Anthropic CCAR-P (Claude Certified Architect - Professional) Practice Test 7

Question 60

A large engineering project delegates code search, test investigation, and documentation to assistants with separate permission sets. Which acceptance outcome would show that delegated work completes without unnecessary privileged tools?

  1. Consistency of generated changes with repository build and test conventions across fresh sessions
  2. Denial of prohibited commands after attempts to override local and project configuration
  3. Secret-scanning results and blocked exfiltration on seeded repository credentials
  4. Subagent task completion with zero out-of-scope tool access

Explanation

Correct Answer

D:

Role-isolation tests prove that decomposition also restricts authority; measure subagent task completion with zero out-of-scope tool access at the release gate; give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts.

Incorrect Answers

A:

Reproducible onboarding shows whether team guidance is discoverable and current; put reviewed repository-specific guidance in a shared CLAUDE.md file with appropriate scope and code review; this tests consistency of generated changes with repository build and test conventions across fresh sessions; the actual release condition is subagent task completion with zero out-of-scope tool access.

B:

Policy precedence tests validate that enterprise controls remain effective; use organization-managed policy and supported permission configuration so enforced restrictions cannot be casually overridden by per-user convenience settings; this tests denial of prohibited commands after attempts to override local and project configuration; the actual release condition is subagent task completion with zero out-of-scope tool access.

C:

Source and runtime scans target the actual paths by which developer secrets can leak; use approved secret storage, scoped environment access, and redaction while avoiding credentials in repositories, prompts, or logs; this tests secret-scanning results and blocked exfiltration on seeded repository credentials; the actual release condition is subagent task completion with zero out-of-scope tool access.

Question 61

A credit-review agent can request sensitive write privileges only after a confirmed transaction step. During exploratory conversations, testers attempt to trigger the final action prematurely. Which evidence validates the staged permission design?

  1. Changes rejected when requested tool scopes exceed the approved task manifest
  2. Single correct connector selection and consistent ticket states across repeated requests
  3. Correct tool-selection rate for ambiguous intents and invalid-argument rejection
  4. Absence of privileged tool calls before the confirmed transaction stage
  5. Zero mutation permissions for report-only identities across tool contract checks

Explanation

Correct Answer

D:

Stage-bound tests prove that tool exposure follows authorization and intent; measure absence of privileged tool calls before the confirmed transaction stage at the release gate; reveal high-impact tools only within a confirmed, authorized transaction stage; maintain server-side gating independently of model choice.

Incorrect Answers

A:

Policy-based manifest validation detects excessive authority before runtime exposure; maintain owner-approved manifests with risk classification, contract checks, permission reviews, and change-control gates; this tests changes rejected when requested tool scopes exceed the approved task manifest; the actual release condition is absence of privileged tool calls before the confirmed transaction stage.

B:

Removing ambiguity should reduce routing variance without reducing supported tasks; consolidate overlapping operations behind a maintained interface and retire obsolete tool definitions after migration testing; this tests single correct connector selection and consistent ticket states across repeated requests; the actual release condition is absence of privileged tool calls before the confirmed transaction stage.

C:

Confusion tests exercise the ambiguity that caused misrouting; define task-specific descriptions, typed arguments, required fields, and clear side-effect semantics so tool selection is meaningful; this tests correct tool-selection rate for ambiguous intents and invalid-argument rejection; the actual release condition is absence of privileged tool calls before the confirmed transaction stage.

E:

Permission tests reveal whether supposedly analytical agents can cause side effects; expose narrowly scoped read-only capabilities and gate changes through separate authenticated write paths with explicit approvals; this tests zero mutation permissions for report-only identities across tool contract checks; the actual release condition is absence of privileged tool calls before the confirmed transaction stage.

Question 62

A regulated enterprise is debating launch despite unresolved safety issues with no assigned mitigations. Its executive committee also sees a polished demo and mistakenly assumes the system handles unknown inputs and outages automatically. Which TWO stakeholder practices make these risks actionable and visible? Choose TWO.

  1. Keep a versioned decision and change history
  2. Demonstrate known limitations alongside successful workflows
  3. Maintain a risk register with controls and accountable owners
  4. Compare options on a shared multi-dimensional scorecard
  5. Record alternatives and rationale in an architecture decision record

Explanation

Correct Answers

B:

Use representative happy-path and failure-path demonstrations with explicit fallback, uncertainty, and human ownership; understanding checks reveal whether decision-makers grasp operational limits; its corresponding workstream should be validated by stakeholder identification of boundaries and fallback responsibilities after the demo.

C:

Record probability and impact where appropriate, control owners, evidence, residual risk, and required approvals; a control register makes risk decisions reviewable rather than rhetorical; its corresponding workstream should be validated by completion and ownership of high-severity mitigations before the release gate.

Incorrect Answers

A:

Maintain a version-controlled decision log linked to implementation and review milestones, including superseded guidance; chat history and scattered slides rarely provide an authoritative current decision state; its natural acceptance measure is correct retrieval of active decisions and their supersession chain during review, which does not satisfy the separate workstreams being assessed.

D:

Present the same quality, latency, cost, risk, and maintainability measures for each candidate under agreed weighting; isolated benchmark rankings cannot settle a decision with several business constraints; its natural acceptance measure is stakeholder-approved selection using common scored evidence and disclosed trade-offs, which does not satisfy the separate workstreams being assessed.

E:

Use an ADR recording context, considered options, decision, trade-offs, implications, and conditions for revisiting it; a final diagram alone often omits rejected alternatives and the reasoning behind the choice; its natural acceptance measure is reconstructability of key design decisions after a simulated staff handoff, which does not satisfy the separate workstreams being assessed.

Question 63

A travel advisory workflow retrieves weather notices, visa rules, and company policy with no cross-call dependencies. What action best fits the business and technical boundary?

  1. Move slow operations into asynchronous jobs with progress states
  2. Parallelize independent read-only tool calls
  3. Rerank a short candidate set for ambiguous retrieval queries
  4. Use a safe limited answer when the deadline would otherwise be missed

Explanation

Correct Answer

B:

Execute independent lookups concurrently with bounded timeouts and aggregate the results after all necessary dependencies complete; concurrency wins only if the final synthesis retains complete inputs; evaluate the design with end-to-end p95 improvement with all required sources still present.

Incorrect Answers

A:

Acknowledge an asynchronous job, persist its state, and let the client poll or receive authorized completion notifications; a longer synchronous timeout would still tie up request resources and expose users to unreliable waits; this alternative would measure job completion reliability and duplicate-submission rate during slow-system simulations; it does not establish end-to-end p95 improvement with all required sources still present for the described use case.

C:

Retrieve a bounded candidate set and rerank against the actual question to concentrate useful evidence without feeding all candidates to the model; taking every retrieved hit into context may raise token cost and distraction without raising answer quality; this alternative would measure grounded-answer accuracy and retrieval-stage p95 latency at several rerank depths; it does not establish end-to-end p95 improvement with all required sources still present for the described use case.

D:

Keep the critical verified signal independent and return a clearly limited result when optional enrichment exceeds its budget; silently presenting an unverified enriched conclusion would violate accuracy requirements despite meeting a timer; this alternative would measure deadline compliance and correct indication of omitted enrichment; it does not establish end-to-end p95 improvement with all required sources still present for the described use case.

Question 64

A team adds an executable enforcement hook to prevent selected unsafe operations in an AI-assisted coding workflow. Which simulated bypass test would demonstrate that the check cannot be skipped by prompt wording?

  1. Consistency of generated changes with repository build and test conventions across fresh sessions
  2. Hook execution and blocked noncompliant operations under simulated bypass attempts
  3. Subagent task completion with zero out-of-scope tool access
  4. Access denial for cross-project MCP resources under user identity tests

Explanation

Correct Answer

B:

Gate testing verifies that a real program, not a conversational promise, enforces the rule; measure hook execution and blocked noncompliant operations under simulated bypass attempts at the release gate; configure supported hooks for deterministic checks at appropriate lifecycle points, with clear failure behavior and maintenance ownership.

Incorrect Answers

A:

Reproducible onboarding shows whether team guidance is discoverable and current; put reviewed repository-specific guidance in a shared CLAUDE.md file with appropriate scope and code review; this tests consistency of generated changes with repository build and test conventions across fresh sessions; the actual release condition is hook execution and blocked noncompliant operations under simulated bypass attempts.

C:

Role-isolation tests prove that decomposition also restricts authority; give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts; this tests subagent task completion with zero out-of-scope tool access; the actual release condition is hook execution and blocked noncompliant operations under simulated bypass attempts.

D:

Scope checks confirm that connector convenience has not expanded data visibility; choose appropriate configuration scope and per-user or service authorization for MCP servers, avoiding shared cross-project secrets; this tests access denial for cross-project MCP resources under user identity tests; the actual release condition is hook execution and blocked noncompliant operations under simulated bypass attempts.

Question 65

Developers have built a useful prototype on customer exports that compliance cannot authorize for production. Which action best removes the underlying failure mode?

  1. Define which decisions remain with people
  2. Map available data and its permitted uses before solution selection
  3. Prioritize a repetitive step with bounded exceptions
  4. Measure the current manual task before choosing automation

Explanation

Correct Answer

B:

Data-readiness and usage-rights mapping identifies legitimate inputs, owners, quality gaps, and prohibited transfers before committing to an implementation; measured coverage of eligible sources exposes blockers that a high demo score conceals; verify the repair using percentage of required fields with validated owners, quality checks, and approved processing purposes.

Incorrect Answers

A:

Decision ownership is an authorization and accountability control; it does not fix missing input records or prompt-token waste; explicit decision-rights boundaries distinguish advisory generation from actions requiring a credentialed human or deterministic policy engine; that control is assessed by share of binding decisions showing the required named approver and rationale; the incident instead requires percentage of required fields with validated owners, quality checks, and approved processing purposes.

C:

Prioritization improves initial return and feasibility; it does not directly supply output-validation code or tenant isolation; select a high-frequency, well-described task with measurable work reduction and explicit escalation for ambiguous records; that control is assessed by accepted cases per reviewer-hour with exception share tracked separately; the incident instead requires percentage of required fields with validated owners, quality checks, and approved processing purposes.

D:

Process measurement establishes value, not the identity, data-permission, or runtime architecture of a Claude application; a baseline separates real business improvement from attractive demos; use completed cases, reviewer effort, errors, and exception handling as measurable comparators; that control is assessed by change in verified minutes and rework per adjudicated claim versus the documented baseline; the incident instead requires percentage of required fields with validated owners, quality checks, and approved processing purposes.

Question 66

A replacement model improves a general reasoning score but quietly changes JSON field behavior, breaking two consumers. What release control would detect this incompatibility before rollout?

  1. Select a model path compatible with required modalities
  2. Gate model-version updates on regression tests
  3. Benchmark a smaller model for routine classification
  4. Use stronger reasoning capacity for genuinely complex decisions
  5. Use confidence-aware routing with a bounded fallback

Explanation

Correct Answer

B:

Treat model replacements as versioned releases with task-specific eval gates, contract tests, canaries, and rollback capability; version-aware tests make improvement claims meaningful for the deployed application; verify the repair using no contract regressions and acceptable quality/latency deltas on the proposed release.

Incorrect Answers

A:

Model selection based solely on text benchmark accuracy does not prove image interpretation reliability; confirm that the chosen Claude interface supports the required input modality and test image quality, extraction, and reasoning together; that control is assessed by correct equipment identification and recommendation accuracy on labeled photographs; the incident instead requires no contract regressions and acceptable quality/latency deltas on the proposed release.

C:

A lightweight route should not be assumed suitable for complex multi-step decisions without a representative evaluation; compare an efficient Claude model against labeled classification cases and select the lowest-cost model that meets the defined accuracy floor; that control is assessed by macro-F1, critical-class recall, and cost per correctly triaged message on held-out traffic; the incident instead requires no contract regressions and acceptable quality/latency deltas on the proposed release.

D:

High reasoning capacity is wasteful if the task only extracts a known field or matches a stable label; escalate tasks with demonstrated reasoning difficulty to a capable model after measuring gains on cases involving cross-document dependencies; that control is assessed by correct resolution of cross-exhibit conflicts at the required latency and review cost; the incident instead requires no contract regressions and acceptable quality/latency deltas on the proposed release.

E:

Blindly using one model tier on all cases neither controls the hardest error modes nor optimizes cost; combine an evaluated uncertainty trigger with escalation to a stronger model or reviewer, using explicit limits and post-route quality measurement; that control is assessed by high-risk escalation recall and total cost under the required error ceiling; the incident instead requires no contract regressions and acceptable quality/latency deltas on the proposed release.

Question 67

The planner's prompt is dominated by connector descriptions and begins choosing tools before clarifying the task. What design correction resolves the reported failure?

  1. Keep orchestrator intent and policy separate from tool inventories
  2. Use searchable tool discovery for large catalogs
  3. Preserve stable prefixes while dynamically discovering tools
  4. Load capability groups after intent classification

Explanation

Correct Answer

A:

Separate goal interpretation and policy decisions from a downstream staged capability-discovery step; phase separation verifies that the assistant understands the task before acting; verify the repair using intent-classification accuracy before any tool disclosure or call.

Incorrect Answers

B:

Up-front registration of every schema does not improve a request that needs only one domain-specific operation; expose a lean search or discovery interface and load relevant detailed tools only after intent is established; that control is assessed by tool-choice accuracy and context-token savings on varied employee requests; the incident instead requires intent-classification accuracy before any tool disclosure or call.

C:

Progressive discovery can lose its token advantage if dynamic tool definitions repeatedly destroy cache reuse; isolate stable instructions from changing discovery payloads and measure cache behavior when tool inventories vary; that control is assessed by cache-read tokens and total context cost while changing selected tool subsets; the incident instead requires intent-classification accuracy before any tool disclosure or call.

D:

Capability-group routing cannot replace policy enforcement once a sensitive tool is selected; select a bounded task-specific capability group after intent routing with conservative fallback for ambiguous requests; that control is assessed by irrelevant tool exposure per intent with no loss of required task completion; the incident instead requires intent-classification accuracy before any tool disclosure or call.

Question 68

A coding assistant proposes a change to multi-tenant authorization logic. The review suite deliberately includes a bypass of the resource ownership check. Which result would prove the safeguards detect it before release?

  1. Review time and defect localization per incremental change set
  2. Detection of seeded authorization regressions during peer review and CI
  3. Documented endpoint examples executing successfully against the reviewed build
  4. Passing unit and property tests including specified rounding boundaries

Explanation

Correct Answer

B:

Diff-focused review finds changes that ordinary output fluency cannot reveal; measure detection of seeded authorization regressions during peer review and CI at the release gate; require focused code review of the actual diff, threat-relevant tests, and approval before merging sensitive changes.

Incorrect Answers

A:

Small-batch evidence shows whether modernization remains controlled and reversible; use small scoped changes, compatibility checkpoints, and separate pull requests tied to specific tests; this tests review time and defect localization per incremental change set; the actual release condition is detection of seeded authorization regressions during peer review and CI.

C:

Executable examples reveal fabricated or obsolete instructions; ground documentation generation in current code, schemas, and tests, then validate examples and have owners review changes; this tests documented endpoint examples executing successfully against the reviewed build; the actual release condition is detection of seeded authorization regressions during peer review and CI.

D:

Test-first evidence anchors generated code in independently defined behavior; define executable tests and expected behavior before relying on AI-generated implementation, then review failures and iterate; this tests passing unit and property tests including specified rounding boundaries; the actual release condition is detection of seeded authorization regressions during peer review and CI.

Question 69

Identical user requests randomly reach different connectors and produce inconsistent ticket state. What design correction resolves the reported failure?

  1. Write unambiguous tool descriptions and input schemas
  2. Remove duplicate and deprecated tools from the catalog
  3. Stage privileged capabilities only after explicit intent confirmation
  4. Separate read-only retrieval from mutating tools

Explanation

Correct Answer

B:

Consolidate overlapping operations behind a maintained interface and retire obsolete tool definitions after migration testing; removing ambiguity should reduce routing variance without reducing supported tasks; verify the repair using single correct connector selection and consistent ticket states across repeated requests.

Incorrect Answers

A:

A richer schema improves selection but does not override a backend that ignores caller authorization; define task-specific descriptions, typed arguments, required fields, and clear side-effect semantics so tool selection is meaningful; that control is assessed by correct tool-selection rate for ambiguous intents and invalid-argument rejection; the incident instead requires single correct connector selection and consistent ticket states across repeated requests.

C:

Hiding a tool in ordinary prompts is a defense-in-depth measure, not sufficient if APIs permit unauthorized direct calls; reveal high-impact tools only within a confirmed, authorized transaction stage; maintain server-side gating independently of model choice; that control is assessed by absence of privileged tool calls before the confirmed transaction stage; the incident instead requires single correct connector selection and consistent ticket states across repeated requests.

D:

A generic read-write interface offers more authority than the reporting workflow requires; expose narrowly scoped read-only capabilities and gate changes through separate authenticated write paths with explicit approvals; that control is assessed by zero mutation permissions for report-only identities across tool contract checks; the incident instead requires single correct connector selection and consistent ticket states across repeated requests.

Question 70

A benefits assistant supports several languages, but an audit suspects one language has disproportionate guidance errors. Which measurement would reveal whether quality and escalation are equitable across supported groups?

  1. Time to resolve substantiated challenges and proportion of cases with documented review
  2. Quality and escalation parity across predeclared language segments
  3. Task completion by users of tested assistive technologies on representative flows
  4. Accuracy of user understanding of supported versus unsupported tasks
  5. Successful intervention before seeded high-impact incorrect actions are committed

Explanation

Correct Answer

B:

Group-specific evaluation reveals concentrated harm masked by pooled scores; measure quality and escalation parity across predeclared language segments at the release gate; evaluate suitable subgroup error rates and access outcomes, with privacy-aware sampling and appropriate fairness review.

Incorrect Answers

A:

Remedy effectiveness measures whether affected people can obtain meaningful reconsideration; provide a contest and correction process with accountable human ownership for significant impacts; this tests time to resolve substantiated challenges and proportion of cases with documented review; the actual release condition is quality and escalation parity across predeclared language segments.

C:

Direct accessibility testing measures practical use rather than formal content correctness only; include accessibility requirements, assistive-technology testing, and inclusive content rubrics in evaluation and design; this tests task completion by users of tested assistive technologies on representative flows; the actual release condition is quality and escalation parity across predeclared language segments.

D:

Scenario tests reveal whether disclosures prevent inappropriate reliance; maintain clear documentation of intended use, unsupported scenarios, measured performance, and escalation requirements; this tests accuracy of user understanding of supported versus unsupported tasks; the actual release condition is quality and escalation parity across predeclared language segments.

E:

Pre-commit override drills test real controllability rather than retrospective documentation; preserve an authorized override and recovery route scaled to decision consequences, with feedback recorded for evaluation; this tests successful intervention before seeded high-impact incorrect actions are committed; the actual release condition is quality and escalation parity across predeclared language segments.

Claude Certified Architect - Professional (CCAR-P) Practice Tests