Home / Claude Certified Architect – Foundations / Objective 5.2

Domain 5: Context Management & Reliability · 15% of the exam · Full exam outline

5.2 Design effective escalation and ambiguity resolution patterns

What this objective covers

Appropriate escalation triggers: customer requests for a human, policy exceptions/gaps (not just complex cases), and inability to make meaningful progress. The distinction between escalating immediately when a customer explicitly demands it versus offering to resolve when the issue is straightforward. Why sentiment-based escalation and self-reported confidence scores are unreliable proxies for actual case complexity. How multiple customer matches require clarification (requesting additional identifiers) rather than heuristic selection. Adding explicit escalation criteria with few-shot examples to the system prompt demonstrating when to escalate versus resolve autonomously. Honoring explicit customer requests for human agents immediately without first attempting investigation. Acknowledging frustration while offering resolution when the issue is within the agent's capability, escalating only if the customer reiterates their preference. Escalating when policy is ambiguous or silent on the customer's specific request (e.g., competitor price matching when policy only addresses own-site adjustments). Instructing the agent to ask for additional identifiers when tool results return multiple matches, rather than selecting based on heuristics.

Practice questions

Question 1easy

A team is building an agent that refactors a service across many files over several hours. The product owner wants to review direction at a few planned points without approving every individual action. Which design fits the agent pattern?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Checkpoints give the owner a say at the points they care about while the agent keeps operating independently between them, which is exactly what the pattern allows.

This keeps autonomy but drops the planned review points the owner explicitly wants during the run.

Per-call approval is the opposite of what the owner asked for and removes the agent's independent operation.

Iteration caps are a real control, but they end the run at an arbitrary count rather than at the review points the owner chose.

Question 2easy

In Anthropic's description of autonomous agents, at which points can an agent stop and bring the human back in while it works?

Included in Master: master every domain.See plans