Anthropic CCAR-P Exam Prep
Claude Certified Architect - Professional (Page 4 )

Updated On: 3-Oct-2026

HOTSPOT (Drag and Drop is not supported)

You are evaluating prompting claims in a peer's design document.
For each claim, select yes if the claim reflects sound practice. Otherwise, select no.
QUESTION IMAGE:

  1. See Explanation section for answer.

Answer(s): A

Explanation:

CORRECT AREA HIGHLIGHTED




You are supporting an engineer whose newly added MCP server does not appear in their Claude Code session.
Which diagnostic step should be tried first?

  1. Disable every MCP server in the configuration to isolate the issue, removing all tool access rather than confirming whether the new server is registered.
  2. Switch the team to a different Claude product family unrelated to the existing workflow, abandoning the current configuration rather than diagnosing the registration issue.
  3. Verify the MCP server is registered using the listing command, then reconnect the session if needed, since configuration changes typically require a restart to take effect.
  4. Reinstall the developer's operating system from scratch, discarding all local configuration and tool state before attempting any targeted diagnostic steps.

Answer(s): C

Explanation:

The first diagnostic action must establish whether Claude Code has loaded the MCP server configuration and whether it can connect to the registered endpoint. The official management command is claude mcp list; within Claude Code, /mcp can also be used to inspect server status. The listing distinguishes registered and connected servers from configurations that require authentication, approval, or connection troubleshooting. Connect Claude Code to Tools via MCP
If the server was added or its configuration changed after the current session began, reconnecting or restarting the relevant Claude Code session is a proportionate next step. This ensures that configuration state and available tool definitions are refreshed before more intrusive troubleshooting begins. If the server is listed but unhealthy, the engineer can then inspect it with claude mcp get <name> and investigate transport, command path, credentials, workspace approval, or endpoint connectivity.
Options A, B, and D are operationally unsound because they discard working capabilities or environments before confirming the basic registration state. Disabling all MCP servers eliminates useful diagnostic comparisons; changing product families abandons the relevant configuration; reinstalling the operating system is grossly disproportionate and risks destroying evidence needed for diagnosis.
Study Guide references/topics: Claude Code environment configuration; MCP registration; server-status inspection; session refresh; targeted operational troubleshooting.



You are enabling a development team to build Claude-integrated features efficiently. The team reports that prompt engineering is consuming 40% of their development time due to manual trial-and-error iterations.
Which combination of developer productivity tools and practices would most effectively improve throughput while maintaining quality?

  1. Establish a prompt versioning system with tracked performance metrics, create a shared prompt library with documented examples and patterns for common tasks, provide a local evaluation harness so developers can test prompt changes against a suite of test cases before committing, and schedule regular knowledge-sharing sessions where developers share what works for different use cases
  2. Require all prompt engineering to be done by a single senior developer to ensure consistency and eliminate duplicated effort
  3. Use an automated prompt generation system that removes the need for manual prompt engineering altogether, accepting that generated prompts may be sub-optimal
  4. Have developers use the same generic prompt for all tasks to minimize customization and testing overhead

Answer(s): A

Explanation:

The correct answer addresses the root cause of inefficiency: lack of reusable knowledge and feedback mechanisms. A prompt versioning system with performance metrics creates institutional memory and prevents repeating failed iterations. A shared library accelerates onboarding and reduces redundant exploration. A local evaluation harness enables rapid, low-friction feedback without repeated API calls, reducing iteration time from minutes (waiting for API) to seconds. Knowledge-sharing sessions distribute best practices across the team, multiplying the impact of individual learnings. Together, these practices typically reduce prompt engineering time by 50-70%.
Why others are incorrect: A single bottleneck developer does not scale and creates a single point of failure. Automated prompt generation cannot reliably replace domain-specific tuning and often produces mediocre outputs. A generic prompt for all tasks ignores that prompts must be tailored to the specific task, input structure, and desired output format, leading to poor quality and requiring rework.



You are identifying signals that a deployment should re-enter design rather than continue iterating in place.
Which signal most directly indicates the need for a new design cycle?

  1. A runbook step requires a clarification edit to improve on-call guidance accuracy, which can be handled as a documentation update without changes to component responsibilities or core contracts.
  2. A dashboard alert threshold needs a small numerical adjustment to reduce false-positive noise, which can be handled as an operational configuration change without a new design cycle.
  3. A minor copy edit is requested in a customer-facing string within the existing UI, which can be handled as a localized content change without altering component responsibilities or contracts.
  4. The system's current architecture cannot meet the new requirements without changes to component responsibilities or core contracts.

Answer(s): D

Explanation:

A new design cycle is warranted when the required change crosses an architectural boundary. Option D explicitly states that the existing architecture cannot satisfy the new requirements without redistributing component responsibilities or altering core contracts. Such changes may affect service ownership, orchestration, data flows, integration interfaces, security boundaries, failure handling, evaluation strategy, and operational accountability. They therefore require renewed discovery, impact analysis, design review, stakeholder approval, and regression planning.
Options A, B, and C are localized maintenance activities. Clarifying a runbook improves operational documentation but does not change the deployed system's structure. Adjusting an alert threshold is a controlled operational tuning activity, provided the change remains within established monitoring policy. Editing customer-facing copy is similarly confined to the presentation or content layer. None of these changes inherently invalidates component contracts or architectural assumptions.
An architect should distinguish between iteration within an approved design and evidence that the design itself no longer supports the required outcome. Re-entering design for every minor adjustment creates unnecessary governance overhead; continuing local iteration after architectural assumptions have failed creates unmanaged technical and operational risk. Option D is the only signal that establishes a structural incompatibility.
Study Guide references/topics: Lifecycle feedback loops; design re-entry criteria; architectural significance; component responsibilities; interface contracts; controlled operational iteration.



MULTIPLE CHOICE
A security team is evaluating two proposed controls. Control A adds an outbound tool allow-list with destination restrictions and per-call review. Control B scores responses against a stable adversarial evaluation set after each model-version change.
Which two risk categories are correctly matched to these controls? (Select two.)

  1. Control A --- prompt injection from adversarial content in retrieved data
  2. Control A --- silent quality drift after a model-version upgrade
  3. Control A --- data exfiltration via outbound tool calls
  4. Control B --- data exfiltration via outbound tool calls
  5. Control B --- silent quality drift after a model-version upgrade

Answer(s): C,E

Explanation:

Control A directly constrains the outbound action surface. An allow-list limits which tools and destinations may receive data, while per-call review introduces an approval boundary before information leaves the controlled environment. These measures therefore address data exfiltration through outbound tool calls, making Option C correct. Anthropic's security guidance recommends least privilege, narrowly scoped permissions, sandboxing, and limiting access to sensitive information and actions so that a compromised agent can cause minimal damage. Mitigate Jailbreaks and Prompt Injections
Control B addresses model-version drift. Running a stable adversarial evaluation set after each version change creates a consistent comparison baseline and detects regressions that might otherwise remain invisible during routine testing. This correctly maps Control B to silent quality drift, making Option E correct. Anthropic's migration guidance repeatedly calls for workload reevaluation because instruction following, style, reasoning, and agent behavior can differ between versions. Model Migration Guide
Control A may limit the consequences of successful prompt injection, but it does not prevent or directly detect adversarial instructions in retrieved content. Control B measures behavioral performance but does not impose outbound authorization controls. Each control must therefore be mapped to the risk it most directly mitigates.
Study Guide references/topics: Tool governance; least privilege; exfiltration controls; adversarial evaluations; model-change regression testing; defense in depth.



Viewing page 4 of 30
Viewing questions 16 - 20 out of 125 questions


Post your Comments and Discuss Anthropic CCAR-P exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!