CCA-FUpdated 8d ago · Aug 28, 2026

Claude Certified Architect - Foundations

134 questions across 1 topics, with suggested answers, explanations where available, and imported community discussion. The first 13 questions are free to preview.

Browse questions Practice mode

Topics

#	Topic	Questions	Free
1	Agentic Architecture & Orchestration	116	13

Preview

13 of 116 accessible

Question 1 · Agentic Architecture & Orchestration Open

You’re implementing escalation logic for when the agent should invoke `escalate_to_human`. Your team has proposed four different ways to trigger escalation. Which approach will most reliably identify cases that truly need human intervention?

Answer: C Human escalation is most reliable when it is triggered by clear, task-relevant conditions: the customer explicitly asks for a human, the required resolution involves a policy exception, or the agent cannot make meaningful progress. These conditions directly reflect a need for human judgment or assistance, unlike sentiment thresholds, fixed retry counts, or rigid category mappings.

Question 2 · Context Management & Reliability Open

The agent confirms customer identity through a multi-step process before resetting passwords. During testing, after the customer answers the third verification question, the agent asks for their name again, as though the earlier exchange never occurred. What is the most likely reason for this behavior?

Answer: C The Claude Messages API requires the application to supply the relevant prior user and assistant messages with each new request to preserve conversational context. When subsequent requests omit the conversation history, Claude has no access to information established in earlier exchanges and may ask for it again. **Learn more:** [Messages — Claude API Reference](https://platform.claude.com/docs/en/api/messages)

Question 3 · Context Management & Reliability Open

A customer comes back **4 hours** after the original session about the same billing dispute. The prior **32-turn** session includes `lookup_order` results stating: “Status: PENDING, Expected resolution: 24-48 hours.” During testing, you find that, when sessions with stale tool results are resumed, the agent frequently cites the outdated information in its responses (for example, “I see your refund is still being processed”) even after later fresh tool calls return different details. What approach most reliably supports returning customers?

Answer: A Starting a new session with a structured summary preserves durable context such as the issue, completed actions, and prior resolution state without retaining stale tool observations. Performing new tool calls before responding makes the current external state the only operational data available to the agent, avoiding conflicts with older results and unsupported prior assertions.