최신 CCAR-F 무료덤프 - Anthropic Claude Certified Architect – Foundations

A. Request B, the error handling task

B. Request A, the function rename task

C. Neither request benefits significantly

D. Both requests benefit equally

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. 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.

C. 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.

D. Add an error classification step in the agentic loop that intercepts tool errors before Claude sees them, then routes to hardcoded retry or escalation logic.

A. Define a fixed sequence of investigation steps upfront-grep for error patterns, then read error handlers, then check database queries, then examine middleware-executing each step regardless of intermediate findings.

B. Have the agent first create a comprehensive plan mapping all code paths through the endpoint before beginning any file exploration or code reading.

C. Run parallel worker agents that simultaneously investigate all four layers, then synthesize their findings to identify where the error originates.

D. Have the agent dynamically generate investigation subtasks based on what it discovers at each step, adapting its exploration plan as new information about the error path emerges.

A. Consolidate semantically overlapping tools-merge issue_credit and process_refund into a single resolve_compensation tool with an action parameter, and fold check_delivery_status into lookup_order with an optional include_tracking flag.

B. Split the tools across two sub-agents-a "financial resolution" agent with process_refund, issue_credit, and apply_promo_code, and a "delivery operations" agent with the remaining delivery tools-with a coordinator routing between them.

C. Add few-shot examples to the system prompt demonstrating correct selection for each ambiguous tool pair, such as showing when issue_credit applies versus when process_refund is appropriate.

D. Enable the tool search tool with defer_loading on the six new tools, keeping the original four always loaded, so the agent dynamically discovers specialized tools only when needed.

A. Set tool_choice to "auto" and reorder the tool definitions so extract_metadata appears first in the tools array, since Claude prioritizes earlier-listed tools.

B. Set tool_choice to {"type": "tool", "name": "extract_metadata"} and process the enrichment requests in subsequent turns after receiving the extracted metadata.

C. Set tool_choice to "any" so Claude must use a tool, combined with system prompt instructions prioritizing extract_metadata .

D. Set tool_choice to {"type": "tool", "name": "extract_metadata"} for every API call in the pipeline, ensuring Claude always extracts metadata before any enrichment can occur.

A. Enter plan mode to explore library usage across modules, map affected code paths, then create a migration strategy before implementing.

B. Update the dependency version, run the test suite, and use Claude Code to fix each failure as it appears.

C. Paste the migration guide's breaking changes into your prompt and use direct execution to update all usages across the 45 files.

D. Create a custom slash command encapsulating the migration transformations, then execute it against each file without prior codebase exploration.

A. Extract the formatting rules into a dedicated skill that Claude loads automatically when generating code, with more detailed examples of correct formatting.

B. Split the formatting rules into path-scoped .claude/rules/ files that load when Claude works on matching file types.

C. Configure a PostToolUse hook with an Edit|Write matcher that automatically runs Prettier on each file Claude modifies.

D. Add a Stop hook with a prompt-based check that evaluates whether generated code follows formatting standards and prompts Claude to fix violations.