Claude Certified Architect Foundations CCA-F Exam Questions

Question # 4

A team implements an agent with the Agent SDK. They want to add observability: logging each toolcall with timing, inputs, outputs, and model decisions. The Agent SDK uses setting_sources forconfiguration. Where should they implement the logging?

A. In the system prompt: 'Log every tool call you make with its parameters and timing' 
B. Enable debug mode in the Agent SDK to get automatic logging 
C. Wrap each tool handler with a logging decorator that captures inputs, outputs, execution time, and errors before returning results to the Agent SDK
D. Add a 'log' tool that Claude calls after every operation 

The correct answer is A. Why A is correct: Claude is natively multilingual — this is a core capability, not something that needs to be engineered around. Here's why A works:

• Claude can read and understand English system prompts and tool results
• Claude can detect the language of the user's message automatically
• Claude can generate a response in the customer's language (Japanese, Spanish, etc.) even though its internal context is in English
• No translation infrastructure needed — Claude handles this naturally

This is the simplest, most cost-effective, and most reliable architecture. Why the others are wrong: B. Translate system prompt per language

• Unnecessary complexity — Claude doesn't need the system prompt in the customer's language to respond in that language
• Translation of system prompts introduces risk of meaning drift or errors
• Multiplies maintenance burden (every system prompt change must be updated in N languages)

C. Use a translation MCP tool for everything

• Massive overhead and latency — translating every input/output through a separate tool
• Introduces another failure point in the pipeline
• Completely unnecessary given Claude's native multilingual ability

D. Separate agent configurations per language

• Huge operational overhead — maintaining multiple agents for what Claude handles natively
• Scaling problem: what happens when you add a 4th or 5th language?
• Overkill solution to a non-problem

The key principle:

Don't engineer solutions for problems Claude already solves natively

Claude's multilingual capability means you get language handling for free. A good architect recognizes when to leverage the model's built-in strengths rather than adding unnecessary complexity.

Why D is Correct? This is the most elegant and practical solution within the constraints of JSON. By designing a schema where each configuration option has both a value and a comment field, you:

• Stay within valid JSON — no syntax violations
• Keep everything in one response — comments are co-located with their respective config values
• Remain machine-readable — the JSON can still be parsed programmatically
• Allow downstream processing — a script can strip out comment fields to produce a clean config, while humans can read the annotated version

Example output would look like:

{
  "port": {
    "value": 8080,
    "comment": "Server listening port"
  },
  "debug": {
    "value": false,
    "comment": "Enable verbose logging for development"
  }
}

Key Takeaway: When a format has limitations (like JSON lacking comment support), the best approach is to design your schema to work around the limitation — not fight the format or add unnecessary complexity.

Why B is Correct? This metric is purpose-built for exactly the behavior being measured. Here's why it's the right fit:

• It directly measures the target behavior — whether the agent recognizes ambiguity and responds appropriately by asking for clarification
• It uses a ground truth set of known ambiguous inputs, making it objective and repeatable
• It produces a quantifiable percentage, making it trackable over time and across model versions
• It captures both failure modes:
  • Agent asks for clarification when it shouldn't ? false positives
  • Agent makes assumptions when it should ask ? false negatives

How it works in practice:

Clarification Rate = (Ambiguous inputs where agent asked for clarification)
                     ?????????????????????????????????????????????????????
                        (Total ambiguous inputs in ground truth set)
                        
                        Target: as close to 100% as possible

Key Takeaway: When evaluating agent behavior, your metric must directly observe that behavior — not infer it from indirect signals like speed or token count. Clarification Rate does exactly that by comparing agent actions against a curated ground truth of ambiguous cases.

Shift+Tab is the default keyboard shortcut for toggling plan mode in Claude Code. It cycles through modes — including Plan — mid-session, with no restart required. Lowcode More specifically, Shift+Tab cycles through the three modes in order: Edit ? Auto-Accept ? Plan. Medium Here's why the other options are incorrect:

• B. Tab — plain Tab is not a mode-cycling shortcut; it's Shift+Tab.
• C. Ctrl+P — this is not a Claude Code shortcut for plan mode. You can type /plan as a slash command, but Ctrl+P is not the keyboard shortcut.
• D. Escape — pressing Escape (or Esc twice) is used to cancel or rewind a conversation, not to enter plan mode.

Bonus tip: On Windows with Claude Code 2.1.3+, there is a known bug where Shift+Tab only cycles between Edit and Auto-Accept, skipping Plan mode entirely. The workaround is to use the /plan slash command or the mode selector in the UI instead.