Bonus 3. Multi-agent orchestration with ADK
Multi-agent orchestration with ADK
Optional, never counted, externally billed. Not required for completion or a certificate, and excluded from every total. Use a dedicated sandbox project, synthetic people and media, budget alerts, least-privilege identities, and the teardown checklist. Never use real disaster-response, health, identity, or location data.
Outcome
Compare a deterministic sequential workflow with specialized upload, extraction, persistence, and summary agents; add budgets and explicit ownership for every handoff.
Evidence artifact
An architecture decision record and an instrumented orchestration trace with one injected partial failure.
Failure clinic
Unbounded delegation, ambiguous state ownership, duplicate side effects, hidden partial failure, and excess latency.
Required comparison
Before using a managed service, implement or inspect a local fixture-backed baseline. Record what the cloud component improves, what it costs, what new permissions it receives, and what failure modes it introduces. The cloud path must not be the only way to understand or demonstrate the concept.
Safety and operations gate
- Confirm the active project and account before creating resources.
- Use synthetic data and document its provenance.
- Record enabled APIs, regions, identities, roles, public endpoints, and retention.
- Bound model calls, uploads, retries, and concurrent work.
- Redact logs and traces before sharing.
- Delete or disable every resource and verify that billing surfaces are empty.