Anthropic CCAR-F 問題集 : Claude Certified Architect - Foundations

Your agent uses three tools: get_property_details(property_id) returns data including street address, get_price_history(property_id) returns historical pricing, and get_neighborhood_info(address) returns area statistics. You observe that get_neighborhood_info always requires get_property_details first just to extract the address, even when users specify the property by ID. This creates unnecessary latency and failure coupling - if the first call fails, the neighborhood request also fails. What tool design change best addresses this?

• A. Consolidate into a single get_property_with_neighborhood(property_id) tool returning both datasets.
• B. Create a lookup_address(property_id) helper tool for retrieving addresses.
• C. Change get_neighborhood_info to accept property_id, resolving the address internally.
• D. Add retry logic and timeout handling to get_property_details.

Which statement BEST describes Retrieval-Augmented Generation?

• A. It changes token pricing.
• B. It supplies relevant external knowledge during inference.
• C. It compresses model weights.
• D. It permanently retrains Claude.

You are using Claude Code to accelerate software development. Your team uses it for code generation, refactoring, debugging, and documentation. You need to integrate it into your development workflow with custom slash commands, CLAUDE.md configurations, and understand when to use plan mode vs direct execution.
A critical bug is affecting production users. Error logs show exceptions in the OrderProcessing module with a clear stack trace pointing to a specific function. You haven't worked with this module before. What's the most effective approach?

• A. Enter plan mode to explore the module's architecture and dependencies before attempting any fixes.
• B. Use direct execution to examine the stack trace, read the relevant code, and implement a fix once you identify the root cause.
• C. Start with direct execution to gather initial information, then switch to plan mode to design a comprehensive solution before implementing any changes.
• D. Use plan mode to analyze the error in context of the module's design, enumerate potential root causes, and prioritize fixes systematically.

Anthropic's tool use documentation states: "Write instructive error messages. Instead of generic errors like 'failed', include what went wrong and what Claude should try next." A billing dispute agent uses lookup_order, which catches all exceptions and returns a tool_result with is_error:
true and the message "Tool execution failed". Monitoring shows two failure modes: the agent retries the identical call until hitting the turn limit, or it immediately calls escalate_to_human without trying alternative tools. Which change follows the documented recommendation and gives Claude the information it needs to select the correct recovery action for each error type?

• A. Remove is_error: true and return the error details as normal tool content, so Claude reasons about the response as data rather than treating it as a flagged failure condition that biases retry behavior.
• B. Add an error classification step in the agentic loop that intercepts tool errors before Claude sees them, tags each as "retry," "try_alternative," or "escalate," and appends that recommendation to the tool result.
• C. Implement retry logic with exponential backoff inside each tool implementation so transient errors are resolved transparently within the tool before any failure result is surfaced to Claude in the agentic loop.
• D. Return error-type-specific messages with is_error: true, e.g., "Order not found-try get_customer to search by phone" for data errors and "Database timeout (transient)-retry should succeed" for infrastructure errors.

Your post_content tool requires user confirmation before publishing. The current workflow displays "Ready to post to social media. Confirm?" and analytics show users approve 98% of requests within 2 seconds. Post-mortems reveal incidents where posts went to wrong accounts, were scheduled for wrong times, or contained errors - all confirmed by users without catching the mistakes. How should you redesign the confirmation workflow?

• A. Require users to type a confirmation phrase instead of clicking a button
• B. Auto-approve routine posts and only require explicit confirmation for unusual patterns like posting to new accounts or large audiences
• C. Include the complete post text, target account, scheduled time, and platform in the confirmation request
• D. Add a mandatory waiting period before the confirm option becomes available