Objective 3.4 · Domain 3 · 19% of the exam
Analyze observability challenges and select monitoring strategies at scale
Observability at scale asks what to log, what to trace, and how to make a non-deterministic system debuggable after the fact. Traces have to span the whole chain, from retrieval through tool calls to model turns, because the failure is usually in the step nobody instrumented. Sampling strategy comes up, so does the cost of logging full prompts and completions, and so does redaction.
5 questions · answers and explanations shown as you go · free, no sign-up
The rest of domain 3: Integration
This domain is 19% of a scored form, about 12 of the 63 questions, spread across 8 objectives. Drill the whole domain or pick another objective below.
- 3.1Evaluate tool/agent configuration for capability bloat(5)
- 3.2Analyze authentication and authorization requirements to identify security gaps(5)
- 3.3Evaluate accuracy-latency trade-offs and justify configuration decisions(5)
- 3.5Design a RAG pipeline with appropriate chunking and indexing strategies(5)
- 3.6Apply retrieval strategies matched to data shape and query pattern(5)
- 3.7Evaluate connection protocols and select the appropriate integration mechanism (MCP, API/CLI, agent-to-agent)(4)
- 3.8Evaluate progressive discovery vs. monolithic context strategy(4)
One objective is a narrow slice. A full-length timed mock is what tells you whether the whole thing holds together.
Sit a timed mock →