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

Question 350

A governance board asks who receives alerts when the assistant's harmful-output rate crosses a threshold. What design decision would best fit these facts?

  1. Negotiate measurable groundedness, coverage, abstention and escalation targets.
  2. Define end-to-end SLIs that include retrieval, tools, queueing and external dependencies.
  3. Publish dependencies, decision gates and contingency dates in the delivery baseline.
  4. Commit to percentile latency and error budgets rather than the mean alone.
  5. Define alert ownership, escalation time and incident response objectives.

Explanation

Correct Answer

E:

Operational service levels need accountable humans, not only machine metric dashboards. State actionable safety incident commitments as an operating commitment with a measurable boundary, dependencies and a named escalation owner.

Incorrect Answers

A:

Although defensible answer-quality commitments can be valuable, it is not the acceptance condition in the question. The missing provision is actionable safety incident commitments, addressed by the control to define alert ownership, escalation time and incident response objectives.

B:

It is aimed at a different outcome, whole-service reliability slas. No evidence is given that it provides actionable safety incident commitments; the needed mechanism is to define alert ownership, escalation time and incident response objectives at the appropriate boundary.

C:

It emphasizes dependency-aware schedule promises without closing the stated gap in actionable safety incident commitments. By contrast, the remedy to define alert ownership, escalation time and incident response objectives acts on the condition that makes this scenario fail.

D:

That is primarily a technique for tail-aware latency objectives. It lacks the explicit measure for actionable safety incident commitments that is necessary here, namely a system that will define alert ownership, escalation time and incident response objectives.

Question 351

A production handoff contains only a prompt file and no diagram of connectors or data flow. What should the solution architect prioritize?

  1. Document SLIs, alert thresholds, owners and operational playbooks.
  2. Record architectural assumptions, verified constraints and exceptions in a decision record.
  3. Document localization decisions and the legal/control basis for each variation.
  4. Create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.

Explanation

Correct Answer

D:

Operations and auditors need the complete system context to reason about failures and exposure. Version the artifacts proving maintainable end-to-end architecture documentation with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

The alternative could reduce risk associated with service reliability handoff completeness, yet the described behavior requires maintainable end-to-end architecture documentation. That outcome depends on the capability to create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.

B:

The proposed measure is aimed at explicit reusable architecture assumptions, not maintainable end-to-end architecture documentation. The architecture must instead create a versioned architecture document showing processing stages, identities, data stores and trust boundaries; a separate change is still needed for maintainable end-to-end architecture documentation.

C:

The relevant trade-off is not primarily governed regional configuration differences. A successful fix needs maintainable end-to-end architecture documentation; otherwise maintainable end-to-end architecture documentation remains unverified even after this change.

Question 352

A team cannot reproduce a deployment because the model, prompt and retrieval versions were not recorded. Which design choice best matches the stated constraint?

  1. Record versioned dependencies and configuration in a deployment manifest.
  2. Document localization decisions and the legal/control basis for each variation.
  3. Create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.
  4. Record architectural assumptions, verified constraints and exceptions in a decision record.

Explanation

Correct Answer

A:

Reproducibility supports regression investigations and safe rollback. Version the artifacts proving complete deployment configuration provenance with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

B:

The proposed action prioritizes governed regional configuration differences. That can coexist with the right solution, but it cannot replace complete deployment configuration provenance: the application must still record versioned dependencies and configuration in a deployment manifest.

C:

The design concern is real but different: maintainable end-to-end architecture documentation. It does not impose the specific requirement for complete deployment configuration provenance; a suitable solution must record versioned dependencies and configuration in a deployment manifest and demonstrate the result.

D:

This addresses explicit reusable architecture assumptions; however, the problem asks for complete deployment configuration provenance. Without the safeguard to record versioned dependencies and configuration in a deployment manifest, the original failure mode is still possible.

Question 353

A security reviewer receives a vague description of 'guardrails' without where they are enforced. Which architecture adjustment is most appropriate?

  1. Document controls by layer, owner, trust boundary and verification evidence.
  2. Document training/adaptation provenance, evaluation scope and known limitations.
  3. Document localization decisions and the legal/control basis for each variation.
  4. Document SLIs, alert thresholds, owners and operational playbooks.

Explanation

Correct Answer

A:

A defensible control design specifies backend gates and tests, not just aspiration. Version the artifacts proving reviewable enforceable control documentation with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

B:

Improving transparent customized-model provenance does not imply reviewable enforceable control documentation. The selected design must document controls by layer, owner, trust boundary and verification evidence, whereas this choice omits that direct protection or verification step.

C:

This recommendation targets governed regional configuration differences at a different point in the workflow. It leaves reviewable enforceable control documentation outside the design contract and does not require the team to document controls by layer, owner, trust boundary and verification evidence.

D:

This is a valid architectural concern when optimizing service reliability handoff completeness. Here it leaves reviewable enforceable control documentation unaddressed, whereas the intended change must document controls by layer, owner, trust boundary and verification evidence before the case can be considered resolved.

Question 354

A data team changes an index schema and downstream app errors appear unexpectedly. Which next step is most defensible?

  1. Keep prompt, policy, test and release notes linked through change control.
  2. Document training/adaptation provenance, evaluation scope and known limitations.
  3. Record architectural assumptions, verified constraints and exceptions in a decision record.
  4. Publish typed integration contracts and change-compatibility requirements.

Explanation

Correct Answer

D:

Explicit interfaces let teams evolve modules without unplanned breakage. Version the artifacts proving versioned cross-team API contracts with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

The control would be justified if alignment of documentation and verification were the limiting factor. In this scenario the decisive target is versioned cross-team api contracts; success requires an architecture that will publish typed integration contracts and change-compatibility requirements.

B:

The option belongs to the broader work on transparent customized-model provenance, but it cannot by itself deliver versioned cross-team api contracts. A decision on this case needs the team to publish typed integration contracts and change-compatibility requirements and verify that outcome.

C:

This shifts attention toward explicit reusable architecture assumptions when the relevant decision is about versioned cross-team api contracts. Unless the architecture can publish typed integration contracts and change-compatibility requirements, the failure described in the stem remains unresolved.

Question 355

A deployment runbook tells operators to 'restart the agent' for all errors but offers no diagnosis. Which approach should be recommended?

  1. Publish typed integration contracts and change-compatibility requirements.
  2. Provide symptom-based triage, trace queries, escalation paths and rollback steps.
  3. Document localization decisions and the legal/control basis for each variation.
  4. Record versioned dependencies and configuration in a deployment manifest.

Explanation

Correct Answer

B:

Useful runbooks connect observations to safe actions and avoid reflexive restarts. Version the artifacts proving actionable incident resolution guidance with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

This addresses versioned cross-team api contracts; however, the problem asks for actionable incident resolution guidance. Without the safeguard to provide symptom-based triage, trace queries, escalation paths and rollback steps, the original failure mode is still possible.

C:

There is a legitimate use case for governed regional configuration differences, but it does not supply the test or enforcement needed for actionable incident resolution guidance. The design needs to provide symptom-based triage, trace queries, escalation paths and rollback steps.

D:

Consider its actual operating scope: complete deployment configuration provenance. The requested assurance is actionable incident resolution guidance, which calls for an implementation that can provide symptom-based triage, trace queries, escalation paths and rollback steps, not merely for a related improvement.

Question 356

A vendor hands over a fine-tuned model without explaining which data or tests support its use. What is the best production design response?

  1. Publish typed integration contracts and change-compatibility requirements.
  2. Document training/adaptation provenance, evaluation scope and known limitations.
  3. Document controls by layer, owner, trust boundary and verification evidence.
  4. Keep prompt, policy, test and release notes linked through change control.

Explanation

Correct Answer

B:

Model artifacts require lineage and scope evidence to support governance after ownership changes. Version the artifacts proving transparent customized-model provenance with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

This is a valid architectural concern when optimizing versioned cross-team api contracts. Here it leaves transparent customized-model provenance unaddressed, whereas the intended change must document training/adaptation provenance, evaluation scope and known limitations before the case can be considered resolved.

C:

By itself, this improves reviewable enforceable control documentation, but the case is not asking the architect to optimize that dimension. The requirement is transparent customized-model provenance, supported by an approach to document training/adaptation provenance, evaluation scope and known limitations.

D:

Its main effect concerns alignment of documentation and verification. The case explicitly hinges on transparent customized-model provenance; to resolve it reliably, the implementation has to document training/adaptation provenance, evaluation scope and known limitations, which this choice does not establish.

Question 357

A compliance auditor asks who approved customer-facing write permissions for a new agent. Which change most directly satisfies this requirement?

  1. Maintain a decision log tying permissions to reviewers and specific workflow justifications.
  2. Create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.
  3. Document localization decisions and the legal/control basis for each variation.
  4. Document controls by layer, owner, trust boundary and verification evidence.
  5. Document SLIs, alert thresholds, owners and operational playbooks.

Explanation

Correct Answer

A:

Authorization decisions should be traceable to accountable approvals, not inferred from source code alone. Version the artifacts proving auditable privilege approval history with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

B:

Although maintainable end-to-end architecture documentation can be valuable, it is not the acceptance condition in the question. The missing provision is auditable privilege approval history, addressed by the control to maintain a decision log tying permissions to reviewers and specific workflow justifications.

C:

It is aimed at a different outcome, governed regional configuration differences. No evidence is given that it provides auditable privilege approval history; the needed mechanism is to maintain a decision log tying permissions to reviewers and specific workflow justifications at the appropriate boundary.

D:

It emphasizes reviewable enforceable control documentation without closing the stated gap in auditable privilege approval history. By contrast, the remedy to maintain a decision log tying permissions to reviewers and specific workflow justifications acts on the condition that makes this scenario fail.

E:

That is primarily a technique for service reliability handoff completeness. It lacks the explicit measure for auditable privilege approval history that is necessary here, namely a system that will maintain a decision log tying permissions to reviewers and specific workflow justifications.

Question 358

An engineering team copies a popular sample architecture but its data residency assumptions are undocumented. What design decision would best fit these facts?

  1. Keep prompt, policy, test and release notes linked through change control.
  2. Record architectural assumptions, verified constraints and exceptions in a decision record.
  3. Publish typed integration contracts and change-compatibility requirements.
  4. Create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.

Explanation

Correct Answer

B:

Unstated assumptions cause reuse failures when organizational context changes. Version the artifacts proving explicit reusable architecture assumptions with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

Consider its actual operating scope: alignment of documentation and verification. The requested assurance is explicit reusable architecture assumptions, which calls for an implementation that can record architectural assumptions, verified constraints and exceptions in a decision record, not merely for a related improvement.

C:

The proposed measure is aimed at versioned cross-team api contracts, not explicit reusable architecture assumptions. The architecture must instead record architectural assumptions, verified constraints and exceptions in a decision record; a separate change is still needed for explicit reusable architecture assumptions.

D:

The relevant trade-off is not primarily maintainable end-to-end architecture documentation. A successful fix needs explicit reusable architecture assumptions; otherwise explicit reusable architecture assumptions remains unverified even after this change.

Question 359

A new on-call team receives no definition of the system's error budget or alert response sequence. Which intervention most directly addresses the failure?

  1. Document controls by layer, owner, trust boundary and verification evidence.
  2. Document SLIs, alert thresholds, owners and operational playbooks.
  3. Document localization decisions and the legal/control basis for each variation.
  4. Create a versioned architecture document showing processing stages, identities, data stores and trust boundaries.

Explanation

Correct Answer

B:

A service is not operationally ready without instructions that let responders assess severity and act. Version the artifacts proving service reliability handoff completeness with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

Its main effect concerns reviewable enforceable control documentation. The case explicitly hinges on service reliability handoff completeness; to resolve it reliably, the implementation has to document SLIs, alert thresholds, owners and operational playbooks, which this choice does not establish.

C:

This addresses governed regional configuration differences; however, the problem asks for service reliability handoff completeness. Without the safeguard to document SLIs, alert thresholds, owners and operational playbooks, the original failure mode is still possible.

D:

The proposed measure is aimed at maintainable end-to-end architecture documentation, not service reliability handoff completeness. The architecture must instead document SLIs, alert thresholds, owners and operational playbooks; a separate change is still needed for service reliability handoff completeness.

Question 360

A regional deployment uses a different approval workflow but no record explains the exception. What should the solution architect prioritize?

  1. Maintain a decision log tying permissions to reviewers and specific workflow justifications.
  2. Document localization decisions and the legal/control basis for each variation.
  3. Document SLIs, alert thresholds, owners and operational playbooks.
  4. Record versioned dependencies and configuration in a deployment manifest.

Explanation

Correct Answer

B:

Operational deviations need context so maintainers do not mistakenly remove necessary safeguards. Version the artifacts proving governed regional configuration differences with associated configuration and verification records so a successor can reproduce the decision.

Incorrect Answers

A:

It emphasizes auditable privilege approval history without closing the stated gap in governed regional configuration differences. By contrast, the remedy to document localization decisions and the legal/control basis for each variation acts on the condition that makes this scenario fail.

C:

Improving service reliability handoff completeness does not imply governed regional configuration differences. The selected design must document localization decisions and the legal/control basis for each variation, whereas this choice omits that direct protection or verification step.

D:

This recommendation targets complete deployment configuration provenance at a different point in the workflow. It leaves governed regional configuration differences outside the design contract and does not require the team to document localization decisions and the legal/control basis for each variation.

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