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

Question 1150

An independent assessment of a telecommunications support Claude system reports that omnipresent privileged tools create avoidable misuse opportunities. Which change best closes the exposed control gap?

  1. Enforce Progressive schema-on-demand loading
  2. Enforce Scoped tool result summarization
  3. Enforce Deferred capability disclosure
  4. Enforce Context compaction after tool fan-out
  5. Enforce Two-stage source navigation

Explanation

Correct Answer

C:

The remediation acts at the relevant design boundary: the integration can disclose gated tools only after task classification and authorization. That counteracts the observed hazard that omnipresent privileged tools create avoidable misuse opportunities. Rollout should include capability tiers and approval-aware discovery, with regression evidence from forbidden-tool exposure count during ordinary tasks.

Incorrect Answers

A:

Although the alternative reduces the risk that loading every endpoint specification on each turn exhausts context because the integration can retrieve only candidate tool schemas after coarse capability discovery; yet it would not correct the observed weakness: omnipresent privileged tools create avoidable misuse opportunities.

B:

Although the alternative reduces the risk that unrestricted tool payloads consume context and may expose irrelevant data because the integration can trim tool results to task-relevant validated fields before prompting; but this remedy operates on another boundary, not the case where omnipresent privileged tools create avoidable misuse opportunities.

D:

When raw fan-out results can dominate the remaining model context, the integration can aggregate key evidence and preserve original trace references instead of replaying all raw logs; yet it would not correct the observed weakness: omnipresent privileged tools create avoidable misuse opportunities.

E:

This addresses the failure where supplying all document bodies creates noise and hides decisive lines, because the integration can locate relevant documents first and open targeted spans afterward; but this remedy operates on another boundary, not the case where omnipresent privileged tools create avoidable misuse opportunities.

Question 1151

A compliance assurance team is advancing Availability design for downstream dependencies beyond its proof of concept. Engineers expect that the architecture can specify degraded-mode behavior and dependency-aware reliability goals. What evidence of setup readiness should be required first?

  1. Confirm difficulty classifier and escalation accuracy tests
  2. Confirm failure-mode inventory and tested fallback rules
  3. Confirm latency tracing and an agreed user-facing SLO
  4. Confirm priority tiers and admitted-concurrency limits
  5. Confirm tagged cost accounting and a quality acceptance rubric

Explanation

Correct Answer

B:

The required preparation is failure-mode inventory and tested fallback rules. It makes the following architecture claim enforceable: the architecture can specify degraded-mode behavior and dependency-aware reliability goals. If that setup is skipped, a model SLA cannot compensate for an unavailable required retrieval backend, so the release should examine end-to-end availability during indexed-source outages.

Incorrect Answers

A:

The setup is useful to enable the alternative's behavior where the architecture can send low-risk cases to a smaller adequate model and escalate hard cases and trivial classifications and difficult investigations share an expensive model; but the production dependency for Availability design for downstream dependencies is failure-mode inventory and tested fallback rules.

C:

Where average response time looks fine while urgent users face long delays, the architecture can define p95 or p99 targets with workload-specific error budgets; however, the named intervention needs failure-mode inventory and tested fallback rules before its protection can be enforced.

D:

For the separate challenge where traffic spikes exceed sustainable interactive capacity, the architecture can reject or queue nonessential work while preserving critical requests; but the production dependency for Availability design for downstream dependencies is failure-mode inventory and tested fallback rules.

E:

The setup is useful to enable the alternative's behavior where the architecture can compare total model and review cost per accepted result instead of per call and a cheap model yields many outputs that reviewers reject; for this release, the team must first verify failure-mode inventory and tested fallback rules.

Question 1152

An energy operations pilot cannot be accepted because rewriting an entire prompt bundle for every minor change defeats modular management. The owner can change one primary architectural control; what should it be?

  1. Deploy Budget-aware Skill loading
  2. Deploy Modular prompt composition
  3. Deploy Small-delta prompt updates
  4. Deploy Stable-prefix prompt caching

Explanation

Correct Answer

C:

The engineering fix changes the mechanism rather than the presentation: the model configuration can isolate changeable instructions from stable common context. It requires independent rule modules and change tracking; a regression test should examine regression rate and context churn per rule update in cases where rewriting an entire prompt bundle for every minor change defeats modular management.

Incorrect Answers

A:

The alternative reduces the risk that always-on instructions spend context budget on irrelevant procedures because the model configuration can progressively load only the approved capability needed for the task; however, the energy operations defect follows the path in which rewriting an entire prompt bundle for every minor change defeats modular management.

B:

This addresses the failure where shipping all instructions to every request increases interference and token cost, because the model configuration can assemble versioned role-specific modules for the active task; yet it would not correct the observed weakness: rewriting an entire prompt bundle for every minor change defeats modular management.

D:

This addresses the failure where changing the cached prefix can invalidate reuse and trigger new writes, because the model configuration can cache an eligible unchanged prompt prefix to reduce repeat processing cost and latency; whereas the energy operations defect follows the path in which rewriting an entire prompt bundle for every minor change defeats modular management.

Question 1153

During an acceptance review in public-sector casework, Tool dependency error budgets is operational but its benefit has not been measured. Auditors are concerned that overall system uptime can mask a failing required tool. Which evidence most directly settles the question?

  1. Audit cost anomaly precision normalized by useful completions
  2. Audit trace-complete sessions and root-cause isolation time
  3. Audit dependency-caused task failure rate against budget
  4. Audit labeled quality degradation detection delay

Explanation

Correct Answer

C:

Tracking dependency-caused task failure rate against budget provides direct evidence that the system delivers its intended effect: the evaluation process can track dependency-specific error budgets and user-facing completion. The measure is more informative than prompt counts because the failure being measured is that overall system uptime can mask a failing required tool.

Incorrect Answers

A:

Where token spend surges while resolution volume remains flat, a relevant check would establish whether the evaluation process can alert on cost per accepted outcome and decompose input, output and retries; but the acceptance gate must instead inspect dependency-caused task failure rate against budget to detect the targeted failure.

B:

Where complaints cite slowness but each component dashboard looks normal, a relevant check would establish whether the evaluation process can instrument model, retrieval, orchestration and external tool spans together; by contrast, the public-sector casework release needs evidence from dependency-caused task failure rate against budget.

D:

When production intent mix, correctness change after onboarding a new customer and the evaluation process can monitor quality proxies and periodically score sampled expert-labeled outputs; but the acceptance gate must instead inspect dependency-caused task failure rate against budget to detect the targeted failure.

Question 1154

A compliance assurance release candidate fails review after assessors observe that fixing symptoms without new regression cases causes recurrence. What intervention should take priority?

  1. Deploy Safe rollback and kill switch
  2. Deploy Production feedback-to-backlog loop
  3. Deploy Vendor and version change watch
  4. Deploy Continuous cost-governance review

Explanation

Correct Answer

B:

This is the causal correction: the delivery team can turn classified incidents into prioritized, testable improvement work. With issue ownership and linked evaluation cases in place, the team can test defects with reproduced tests and closed remediation actions and show that the problematic case in which fixing symptoms without new regression cases causes recurrence has been addressed.

Incorrect Answers

A:

Where an update creates unsafe automated actions and must be disabled immediately, the delivery team can provide reversible releases and a tested stop mechanism for side effects; but this remedy operates on another boundary, not the case where fixing symptoms without new regression cases causes recurrence.

C:

This addresses the failure where assuming a static vendor environment permits silent integration drift, because the delivery team can maintain a compatibility review for API, model and governance revisions; yet it would not correct the observed weakness: fixing symptoms without new regression cases causes recurrence.

D:

This addresses the failure where a one-time forecast becomes misleading as workload characteristics evolve, because the delivery team can reassess spend versus accepted outcomes on a recurring schedule; but this remedy operates on another boundary, not the case where fixing symptoms without new regression cases causes recurrence.

Question 1155

A healthcare operations incident exposes a specific weakness: a hidden disclaimer elsewhere does not prevent false assumptions in workflow. Which architectural correction addresses the cause rather than masking the symptom?

  1. Introduce Bias-aware dataset curation
  2. Introduce Subgroup error disparity evaluation
  3. Introduce Explainable evidence trail
  4. Introduce Transparency on assistant limitations

Explanation

Correct Answer

D:

The remediation acts at the relevant design boundary: the control layer can label automation role, evidence basis and uncertainty at the decision point. That counteracts the observed hazard that a hidden disclaimer elsewhere does not prevent false assumptions in workflow. Rollout should include approved communication language and user research, with regression evidence from user understanding and inappropriate reliance rate.

Incorrect Answers

A:

This addresses the failure where more data from the same biased process can reinforce misleading targets, because the control layer can audit label quality and group representation before using examples for evaluation; whereas the healthcare operations defect follows the path in which a hidden disclaimer elsewhere does not prevent false assumptions in workflow.

B:

Although the alternative reduces the risk that pooled averages can conceal unequal outcomes because the control layer can test quality and harm rates separately for relevant populations; yet it would not correct the observed weakness: a hidden disclaimer elsewhere does not prevent false assumptions in workflow.

C:

Although the alternative reduces the risk that verbose chain-of-thought-style text is not a substitute for verifiable reasons because the control layer can record relevant policy criteria and source evidence with a clear decision summary; but this remedy operates on another boundary, not the case where a hidden disclaimer elsewhere does not prevent false assumptions in workflow.

Question 1156

The manufacturing quality architect proposes omitting Deferred capability disclosure from the production design. What is the most direct failure mode that decision would expose?

  1. The risk that supplying all document bodies creates noise and hides decisive lines
  2. The risk that full-depth retrieval on every question increases latency without equal value
  3. The risk that unrestricted tool payloads consume context and may expose irrelevant data
  4. The risk that raw fan-out results can dominate the remaining model context
  5. The risk that omnipresent privileged tools create avoidable misuse opportunities
  6. The risk that loading every endpoint specification on each turn exhausts context

Explanation

Correct Answer

E:

This is the direct residual hazard: omnipresent privileged tools create avoidable misuse opportunities. The omitted intervention matters because the integration can disclose gated tools only after task classification and authorization. A reviewer should demand capability tiers and approval-aware discovery and measure forbidden-tool exposure count during ordinary tasks before treating the risk as controlled.

Incorrect Answers

A:

The competing hazard is that supplying all document bodies creates noise and hides decisive lines in a workload where a repository has many documents but only a few sections matter per request; whereas removing Deferred capability disclosure primarily exposes the risk that omnipresent privileged tools create avoidable misuse opportunities.

B:

The competing hazard is that full-depth retrieval on every question increases latency without equal value in a workload where simple lookups need one source but investigations need deeper evidence; but this is not the immediate loss associated with omitting Deferred capability disclosure: omnipresent privileged tools create avoidable misuse opportunities.

C:

When a service returns giant JSON objects when only three fields are needed, unrestricted tool payloads consume context and may expose irrelevant data; however, the named safeguard addresses the distinct hazard that omnipresent privileged tools create avoidable misuse opportunities.

D:

When parallel tool results contain extensive redundant logs, raw fan-out results can dominate the remaining model context; whereas removing Deferred capability disclosure primarily exposes the risk that omnipresent privileged tools create avoidable misuse opportunities.

F:

When dozens of APIs have large OpenAPI specifications, loading every endpoint specification on each turn exhausts context; however, the named safeguard addresses the distinct hazard that omnipresent privileged tools create avoidable misuse opportunities.

Question 1157

After installing Availability design for downstream dependencies in an energy operations workflow, the team must validate whether it has reduced the exposure that a model SLA cannot compensate for an unavailable required retrieval backend. Which measurement is most relevant?

  1. Evaluate critical-request success rate during overload drills
  2. Evaluate percentile latency against target by request class
  3. Evaluate quality-adjusted cost across routed task categories
  4. Evaluate fully loaded cost divided by accepted completions
  5. Evaluate forecast error for tokens per second and concurrency peaks
  6. Evaluate end-to-end availability during indexed-source outages

Explanation

Correct Answer

F:

The acceptance measure focuses on end-to-end availability during indexed-source outages at the task or workflow boundary. Model fluency would not establish whether the architecture can specify degraded-mode behavior and dependency-aware reliability goals, and it could conceal cases where a model SLA cannot compensate for an unavailable required retrieval backend.

Incorrect Answers

A:

The proposed measure would suit a setting where traffic spikes exceed sustainable interactive capacity, since the architecture can reject or queue nonessential work while preserving critical requests; by contrast, the energy operations release needs evidence from end-to-end availability during indexed-source outages.

B:

Where average response time looks fine while urgent users face long delays, a relevant check would establish whether the architecture can define p95 or p99 targets with workload-specific error budgets; however, that proxy would not demonstrate end-to-end availability during indexed-source outages for the selected intervention.

C:

When trivial classifications, difficult investigations share an expensive model and the architecture can send low-risk cases to a smaller adequate model and escalate hard cases; but the acceptance gate must instead inspect end-to-end availability during indexed-source outages to detect the targeted failure.

D:

The proposed measure would suit a setting where a cheap model yields many outputs that reviewers reject, since the architecture can compare total model and review cost per accepted result instead of per call; by contrast, the energy operations release needs evidence from end-to-end availability during indexed-source outages.

E:

The proposed measure would suit a setting where requests differ sharply in input length and tool loops, since the architecture can forecast using token volume, concurrency and retry behavior rather than call count alone; however, that proxy would not demonstrate end-to-end availability during indexed-source outages for the selected intervention.

Question 1158

A contract administration architecture gate expects the following behavior: the model configuration can isolate changeable instructions from stable common context. Which TWO actions together supply the design intervention and its operating dependency? Choose TWO.

  1. Establish clear module precedence and a registry
  2. Establish independent rule modules and change tracking
  3. Implement Small-delta prompt updates
  4. Implement Reusable governed Skill packages
  5. Track cache hit and creation trends before and after configuration change

Explanation

Correct Answers

B:

The prerequisite is independent rule modules and change tracking. It provides the operating preparation for a system in which the model configuration can isolate changeable instructions from stable common context; without this setup, the planned safeguard has not been demonstrated as deployable.

C:

Implementing the intervention changes the operational mechanism so that the model configuration can isolate changeable instructions from stable common context. The failure to prevent is that rewriting an entire prompt bundle for every minor change defeats modular management; configuration and validation remain separate release obligations.

Incorrect Answers

A:

The alternative setup enables a different mechanism: the model configuration can assemble versioned role-specific modules for the active task; whereas this intervention requires independent rule modules and change tracking as its operating precondition.

D:

This design choice is aimed at cases where teams repeat complex procedures with files and scripts across projects; it is effective because the model configuration can package approved specialized instructions and resources for on-demand use. The rollout described is instead governed by the case where; however, the intended intervention requires that the model configuration can isolate changeable instructions from stable common context.

E:

This test would validate a different benefit: the model configuration can test hit behavior because request structure changes may alter caching effectiveness; but that indicator does not verify regression rate and context churn per rule update for the selected architecture.

Question 1159

A software platform pilot cannot be accepted because overall system uptime can mask a failing required tool. The owner can change one primary architectural control; what should it be?

  1. Introduce Semantic failure event logging
  2. Introduce End-to-end request tracing
  3. Introduce Tool dependency error budgets
  4. Introduce Cost anomaly alert per outcome

Explanation

Correct Answer

C:

This is the causal correction: the evaluation process can track dependency-specific error budgets and user-facing completion. With tagged tool-call spans and ownership escalation in place, the team can test dependency-caused task failure rate against budget and show that the problematic case in which overall system uptime can mask a failing required tool has been addressed.

Incorrect Answers

A:

Although the alternative reduces the risk that a status 200 can still represent a failed business outcome because the evaluation process can emit categorized validation failures, not only HTTP error codes; yet it would not correct the observed weakness: overall system uptime can mask a failing required tool.

B:

Where complaints cite slowness but each component dashboard looks normal, the evaluation process can instrument model, retrieval, orchestration and external tool spans together; but this remedy operates on another boundary, not the case where overall system uptime can mask a failing required tool.

D:

This addresses the failure where raw spend alone may rise legitimately with increased workload, because the evaluation process can alert on cost per accepted outcome and decompose input, output and retries; yet it would not correct the observed weakness: overall system uptime can mask a failing required tool.

Question 1160

A procurement services audit challenges the need for Production feedback-to-backlog loop. Which risk would remain unmanaged if its function were not provided elsewhere?

  1. The possibility that skipping evidence gates pushes unresolved assumptions into production
  2. The possibility that fixing symptoms without new regression cases causes recurrence
  3. The possibility that source code transfer alone does not make the service supportable
  4. The possibility that a one-time forecast becomes misleading as workload characteristics evolve
  5. The possibility that passing at release time cannot establish long-term reliability

Explanation

Correct Answer

B:

If the protection disappears, fixing symptoms without new regression cases causes recurrence. The missing architectural distinction is that the delivery team can turn classified incidents into prioritized, testable improvement work. The approval board should require an alternative with issue ownership and linked evaluation cases and validate it against defects with reproduced tests and closed remediation actions.

Incorrect Answers

A:

The other exposure arises when a team attempts global launch before measuring pilot outcomes: skipping evidence gates pushes unresolved assumptions into production; but this is not the immediate loss associated with omitting Production feedback-to-backlog loop: fixing symptoms without new regression cases causes recurrence.

C:

The other exposure arises when a prototype team leaves without trained on-call operators: source code transfer alone does not make the service supportable; whereas removing Production feedback-to-backlog loop primarily exposes the risk that fixing symptoms without new regression cases causes recurrence.

D:

If adoption growth changes the mix of tokens, tools and support effort, a one-time forecast becomes misleading as workload characteristics evolve; but this is not the immediate loss associated with omitting Production feedback-to-backlog loop: fixing symptoms without new regression cases causes recurrence.

E:

When accuracy drifts gradually as policy sources and user behavior change, passing at release time cannot establish long-term reliability; however, the named safeguard addresses the distinct hazard that fixing symptoms without new regression cases causes recurrence.

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