Summer Certification Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: force70

Anthropic Claude Certified Architect – Foundations CCAR-F Question # 42 Topic 5 Discussion

Anthropic Claude Certified Architect – Foundations CCAR-F Question # 42 Topic 5 Discussion

CCAR-F Exam Topic 5 Question 42 Discussion:
Question #: 42
Topic #: 5

You are building a customer support resolution agent using the Claude Agent SDK. The agent handles high-ambiguity requests like returns, billing disputes, and account issues. It has access to your backend systems through custom Model Context Protocol (MCP) tools ( get_customer , lookup_order , process_refund , escalate_to_human ). Your target is 80%+ first-contact resolution while knowing when to escalate.

Your process_refund tool returns two types of errors: technical errors (“503 Service Unavailable”, “Connection timeout”) that are transient (~5% of calls), and business errors (“Order exceeds 30-day return window”, “Item already refunded”) that are permanent (~12% of calls). Monitoring shows the agent wastes 3–4 turns retrying business errors that can never succeed. Currently, both error types return only a plain text message to Claude.

What’s the most effective way to reduce wasted retries while improving customer-facing response quality?


A.

Implement automatic retry logic at the tool layer for technical errors only, passing business errors to Claude without retries.


B.

Add few-shot examples showing how to distinguish retriable from non-retriable errors by parsing error message text.


C.

Add a check_refund_eligibility tool that must be called before process_refund to prevent business rule violations.


D.

Return structured error responses with " retriable " : false for business errors and a customer-friendly explanation for Claude to use.


Get Premium CCAR-F Questions

Contribute your Thoughts:


Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.