Local · Offline
Scenario · Guide 1.0
Read the context first. Every question anchored to it assumes you already know what this organisation runs, what it must achieve, and what it is not allowed to do.
22 items anchored to it in today's catalog
Insufficient evidence
No graded answers against this context yet, out of 22 practice items available. Read it, then drill it.
A drill serves only items anchored to this scenario, untimed, and is recorded as General Practice evidence.
Extracted summary — read the official document for the full text
Overview
An Agent SDK support agent handles ambiguous requests - returns, billing disputes, account problems - through custom MCP tools that reach backend systems. It must resolve most cases on first contact while recognising the ones it should hand to a human.
What an architect should notice. Fix the business in one sentence. What the organisation sells bounds every answer, and a design that would suit a different business is the classic plausible-but-wrong option.
Existing environment
An Agent SDK support agent handles ambiguous requests - returns, billing disputes, account problems - through custom MCP tools that reach backend systems. It must resolve most cases on first contact while recognising the ones it should hand to a human.
What an architect should notice. Treat the incumbent stack as a constraint, not background. A proposal that quietly discards what already runs is usually the distractor.
Business requirements
Primary domains stated by the guide: Agentic Architecture & Orchestration; Tool Design & MCP Integration; Context Management & Reliability. Summary written for this repository; read the official exam guide v1.0 for its own wording.
What an architect should notice. Business requirements decide why. When two designs both work, the one that serves a stated business requirement is the one being asked for.
Technical requirements
Primary domains stated by the guide: Agentic Architecture & Orchestration; Tool Design & MCP Integration; Context Management & Reliability. Summary written for this repository; read the official exam guide v1.0 for its own wording.
What an architect should notice. Technical requirements decide what is permitted. At least one of them normally eliminates two options outright — find it before comparing the rest.
Services in play
What an architect should notice. The named services are the vocabulary the questions reuse. Know what each one is for in this context, and what it is not for.
This page shows the extracted summary this project is permitted to hold, never the full published document. Read the official scenario · summary taken from the official source 2026-07-25T08:00:00Z.
Blueprint ground the anchored items actually cover, largest first
| Domain | Task statement | Items | Available to drill |
|---|---|---|---|
| 5 | 5.2 | 4 | 4 |
| 1 | 1.4 | 3 | 3 |
| 2 | 2.1 | 3 | 3 |
| 1 | 1.5 | 2 | 2 |
| 2 | 2.2 | 2 | 2 |
| 5 | 5.1 | 2 | 2 |
| 1 | 1.1 | 1 | 1 |
| 1 | 1.2 | 1 | 1 |
| 1 | 1.3 | 1 | 1 |
| 2 | 2.3 | 1 | 1 |
| 4 | 4.2 | 1 | 1 |
| 4 | 4.4 | 1 | 1 |
Coverage on this page counts your own already-graded answers. It reports what you have practised, never a verdict on this scenario and never an expected outcome: Google publishes no score mapping between practice results and exam outcomes, official results are reported as pass/fail only, and this platform cannot guarantee success on the official exam.