Home / Claude Certified Architect – Foundations / Objective 1.1

Domain 1: Agentic Architecture & Orchestration · 27% of the exam · Full exam outline

1.1 Design and implement agentic loops for autonomous task execution

What this objective covers

The agentic loop lifecycle: sending requests to Claude, inspecting stop_reason ("tool_use" vs "end_turn"), executing requested tools, and returning results for the next iteration. How tool results are appended to conversation history so the model can reason about the next action. The distinction between model-driven decision-making (Claude reasons about which tool to call next based on context) and pre-configured decision trees or tool sequences. Implementing agentic loop control flow that continues when stop_reason is "tool_use" and terminates when stop_reason is "end_turn". Adding tool results to conversation context between iterations so the model can incorporate new information into its reasoning. Avoiding anti-patterns such as parsing natural language signals to determine loop termination, setting arbitrary iteration caps as the primary stopping mechanism, or checking for assistant text content as a completion indicator.

Practice questions

Question 1easy

Claude asks for two currency conversions in one response. Your code runs both and returns two tool_result blocks, but Claude's final answer swaps the two figures. What should you check first?

Included in Sample: sample every domain.See plans

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

A good description helps Claude decide when and how to call a tool, so the advice is real. Here Claude already called the right tool twice; the failure is in pairing results with calls.

Order is not the matching mechanism. The IDs let Claude pair results with requests even when results arrive in a different order.

Every tool call gets a unique ID, and each tool_result must echo the ID of the call it answers. That pairing is how Claude knows which output belongs to which request, so a mismatch produces exactly this swap.

Claude can legitimately request several tools in one response, and all their results go back together. Splitting them is unnecessary; matching IDs is what keeps them apart.

Question 2easy

Your application has just executed the tools Claude requested in an agent loop. What should the next Messages API request contain?

Included in Master: master every domain.See plans