Objective 4.6 · Domain 4 · 16% of the exam
Monitor system performance using logging and observability tools
Running the system in production, where the interesting problems appear over weeks instead of in a test. Logging, metrics, alerting and drift. What a useful alert looks like for a probabilistic system, where its thresholds come from, and the difference between monitoring the model and monitoring the product outcome it is supposed to move.
6 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.5Optimize token usage, latency, and cost-performance trade-offs(5)
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 →