Anthropic CCA-F Exam : Claude Certified Architect Foundations (CCA-F)

An enterprise wants Claude responses to remain professional across every interaction. Where should tone instructions primarily reside?

• A. System prompt
• B. User prompt only
• C. API key description
• D. Retrieved documents

Your MCP server implements a check_availability tool that queries an external calendar API.
During testing, you encounter three error conditions: (1) the tool is called with a malformed request missing the required user_email parameter, (2) the calendar API returns a 404 because the specified user doesn't exist in the calendar system, and (3) the calendar API returns a 503 because the service is temporarily unavailable. How should each error be reported according to MCP's error handling design?

• A. Report all three as JSON-RPC protocol errors.
• B. Report error 1 as a JSON-RPC protocol error; report errors 2 and 3 as tool results with isError:
  true.
• C. Report errors 1 and 2 as JSON-RPC protocol errors; report error 3 as a tool result with isError:
  true.
• D. Report all three as tool results with isError: true.

A financial services company plans to integrate Claude into an internal document analysis platform. The architects want to minimize exposure of confidential client information while maintaining high-quality responses. Which approach BEST aligns with Anthropic's recommended architecture?

• A. Replace Claude with a smaller local model regardless of task complexity.
• B. Store every prompt permanently for auditing.
• C. Send every document without preprocessing to maximize context.
• D. Remove unnecessary sensitive information before sending prompts whenever possible.

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.
Your team has three requirements for Claude Code's behavior in your project
1. Claude must never modify files in the db/migrations/ directory
2. Claude should prefer your custom logging module over console.log
3. All TypeScript files must be auto-formatted with Prettier after
every edit
All three are currently written as instructions in your project's CLAUDE.md. During a complex refactoring session, a developer discovers that Claude edited a migration file, violating requirement #1. How should you restructure these requirements across Claude Code's configuration mechanisms?

• A. Rewrite all three requirements in CLAUDE.md using stronger directive language and add few- shot examples that demonstrate Claude refusing to edit migration files and running Prettier after edits.
• B. Configure hooks for all three: a PreToolUse hook script that blocks Edit calls targeting db/migrations/,a PreToolUse hook script that adds logging convention context before edits, and a PostToolUse hook that runs Prettier after TypeScript edits.
• C. Move all three requirements into .claude/rules/ as path-scoped rules: one targeting db/migrations/** that forbids editing those files, and others targeting **/*.ts for the logging convention and formatting instruction.
• D. Add Edit(./db/migrations/**) to permissions.deny in the project settings, keep the logging preference in CLAUDE.md, and add a PostToolUse hook on the Edit tool that runs Prettier on changed TypeScript files.

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