Scenario 4: Developer Productivity with Claude
Claude Certified Architect - Foundations (CCAR-F)
Scenario 4: Developer Productivity with Claude
You are building developer productivity tools using the Claude Agent SDK. The agent helps engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate code, and automate repetitive tasks. It uses the built-in tools (Read, Write, Bash, Grep, Glob) and integrates with Model Context Protocol (MCP) servers.
Passage quoted verbatim from the official CCAR-F exam guide v1.0, section 5.
This scenario on the exam
- 4 of 6 — four are dealt at random
- 3
- 30
Primary domains
- Tool Design & MCP Integration
- Claude Code Configuration & Workflows
- Agentic Architecture & Orchestration
What the exam asks inside this context
-
Which built-in for which job. Grep searches contents, Glob matches paths, Edit needs a unique anchor and Read plus Write is the fallback when there is not one.
-
Learning a codebase without reading it all. Grep to entry points, Read to follow imports and trace flows. Reading everything up front fills the context with files the task never touches.
-
Scoped tool sets. An agent holding explore, edit and deploy together will eventually edit during an investigation. The fix is the tool list, not an instruction.
-
MCP servers alongside the built-ins. Project versus user scope, environment variable expansion for tokens, and a description good enough that the agent does not fall back to Grep.