Objective 4.5 · Domain 4 · 16% of the exam
Optimize token usage, latency, and cost-performance trade-offs
Optimising cost and latency once the system works. Caching, model right-sizing per step, trimming context, batching, and streaming to improve perceived latency without changing total time. The framing that scores well is measuring first: the exam dislikes answers that optimise a component nobody has shown to be the bottleneck.
5 questions · answers and explanations shown as you go · free, no sign-up
The rest of domain 4: Evaluation, Testing & Optimization
This domain is 16% of a scored form, about 10 of the 63 questions, spread across 6 objectives. Drill the whole domain or pick another objective below.
- 4.1Define evaluation metrics (accuracy, latency, cost, safety, security)(6)
- 4.2Design evaluation datasets and test frameworks using mixed methodologies(5)
- 4.3Conduct A/B testing and iterative improvements(5)
- 4.4Diagnose system issues (prompt failure, hallucinations, model mismatch)(5)
- 4.6Monitor system performance using logging and observability tools(6)
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 →