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

Question 110

A contract assistant answers questions that depend on definitions in a master agreement and a revised liability limit in a separately signed addendum. Similarity search retrieves only the master agreement, so the controlling amendment is omitted. Which retrieval design is most suitable?

  1. Rely only on the highest-scoring passage from the master agreement because it has the strongest keyword similarity.
  2. Concatenate every historic agreement in the organization into the prompt and omit document-level provenance.
  3. Ask the model to guess likely liability limits from general commercial practice when the cited agreement is silent.
  4. Index cross-document relationships and effective dates, then retrieve the master clause and its controlling addendum together with citations.

Explanation

Correct Answer

D:

A current amendment can override otherwise relevant older text. Following explicit agreement-to-addendum links and checking signed effective versions prevents an apparently well-grounded answer from omitting a controlling instrument.

Incorrect Answers

A:

A similarity score cannot establish which contractual instrument governs a clause. The signed addendum can have lower lexical similarity while controlling the current liability limit.

B:

Bulk context makes controlling versions harder to identify and can exceed capacity. Contractual precedence and specific source attribution remain necessary even when all text is technically visible.

C:

Commercial conventions are not evidence of the parties’ signed amendment. The assistant should resolve related controlling instruments, not invent terms to fill retrieval gaps.

Question 111

An API workflow repeatedly uses a large unchanged system policy with many small user variations. What is the best production design response?

  1. Keep the prompt simple unless instrumentation shows meaningful cache reuse savings.
  2. Place stable material before volatile request-specific content and observe cache hit rates.
  3. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.
  4. Use an appropriate cacheable stable prefix while managing changing conversation context separately.

Explanation

Correct Answer

C:

Prefix caching reduces repeated processing when the identical reusable content is sent within its cache lifetime.

Incorrect Answers

A:

The alternative could reduce risk associated with cost-effective reuse choice, yet the described behavior requires reusable cached prompt prefix. That outcome depends on the capability to cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

B:

The proposed measure is aimed at stable prefix ordering for cacheability, not reusable cached prompt prefix. The architecture must instead cache the stable prompt prefix using supported cache controls and measure cache-read tokens; a separate change is still needed for reusable cached prompt prefix.

D:

The control would be justified if cache-aware multi-turn assembly were the limiting factor. In this scenario the decisive target is reusable cached prompt prefix; success requires an architecture that will cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Question 112

A team frequently modifies the first lines of its common prompt and loses cache hits. Which change most directly satisfies this requirement?

  1. Place stable material before volatile request-specific content and observe cache hit rates.
  2. Keep tenant-specific confidential material isolated and cache only appropriately scoped content.
  3. Use an appropriate cacheable stable prefix while managing changing conversation context separately.
  4. Move volatile timestamps after the stable region and verify cache creation versus cache reads.
  5. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Explanation

Correct Answer

A:

Prompt-prefix cache reuse depends on consistent leading content; early edits invalidate reuse. Version the reusable artifact and instrument stable prefix ordering for cacheability; reusing content does not automatically grant the right to stable prefix ordering for cacheability.

Incorrect Answers

B:

The proposed action prioritizes tenant-safe prompt reuse. That can coexist with the right solution, but it cannot replace stable prefix ordering for cacheability: the application must still place stable material before volatile request-specific content and observe cache hit rates.

C:

The design concern is real but different: cache-aware multi-turn assembly. It does not impose the specific requirement for stable prefix ordering for cacheability; a suitable solution must place stable material before volatile request-specific content and observe cache hit rates and demonstrate the result.

D:

This addresses measured cache effectiveness; however, the problem asks for stable prefix ordering for cacheability. Without the safeguard to place stable material before volatile request-specific content and observe cache hit rates, the original failure mode is still possible.

E:

That choice would be responsive to reusable cached prompt prefix, but the reported defect is different. It leaves stable prefix ordering for cacheability unproved because there is no commitment to place stable material before volatile request-specific content and observe cache hit rates.

Question 113

An organization distributes different copies of its compliance instructions across ten applications. What design decision would best fit these facts?

  1. Publish a versioned reusable prompt module with release and regression review.
  2. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.
  3. Package the procedure as a reviewed reusable Skill or equivalent team instruction artifact.
  4. Version template contracts and test consuming services before releasing the shared update.

Explanation

Correct Answer

A:

Centralized prompt components reduce drift and make policy changes auditable across applications. Version the reusable artifact and instrument modular policy prompt governance; reusing content does not automatically grant the right to modular policy prompt governance.

Incorrect Answers

B:

Improving reusable cached prompt prefix does not imply modular policy prompt governance. The selected design must publish a versioned reusable prompt module with release and regression review, whereas this choice omits that direct protection or verification step.

C:

This recommendation targets reusable specialized workflow guidance at a different point in the workflow. It leaves modular policy prompt governance outside the design contract and does not require the team to publish a versioned reusable prompt module with release and regression review.

D:

This is a valid architectural concern when optimizing safe changes to shared prompt modules. Here it leaves modular policy prompt governance unaddressed, whereas the intended change must publish a versioned reusable prompt module with release and regression review before the case can be considered resolved.

Question 114

A coding team must repeat a specialized release checklist in every new Claude Code session. Which intervention most directly addresses the failure?

  1. Publish a versioned reusable prompt module with release and regression review.
  2. Treat Skills as guidance and enforce production permissions in identities and tool gateways.
  3. Package the procedure as a reviewed reusable Skill or equivalent team instruction artifact.
  4. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Explanation

Correct Answer

C:

A discoverable task-specific skill turns recurring guidance into a maintained workflow rather than repeated ad hoc text.

Incorrect Answers

A:

The control would be justified if modular policy prompt governance were the limiting factor. In this scenario the decisive target is reusable specialized workflow guidance; success requires an architecture that will package the procedure as a reviewed reusable Skill or equivalent team instruction artifact.

B:

The option belongs to the broader work on separating workflow guidance from enforcement, but it cannot by itself deliver reusable specialized workflow guidance. A decision on this case needs the team to package the procedure as a reviewed reusable Skill or equivalent team instruction artifact and verify that outcome.

D:

For a workflow whose primary weakness was reusable cached prompt prefix, that proposal could be reasonable. Here the unmet obligation is reusable specialized workflow guidance, and that requires the system to package the procedure as a reviewed reusable Skill or equivalent team instruction artifact.

Question 115

A short request uses a tiny prompt and runs once per week; caching setup provides little measurable advantage. What should the solution architect prioritize?

  1. Move volatile timestamps after the stable region and verify cache creation versus cache reads.
  2. Keep the prompt simple unless instrumentation shows meaningful cache reuse savings.
  3. Keep tenant-specific confidential material isolated and cache only appropriately scoped content.
  4. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Explanation

Correct Answer

B:

Caching creates value for sufficiently large repeated prefixes; infrequent tiny prompts often do not justify optimization.

Incorrect Answers

A:

This addresses measured cache effectiveness; however, the problem asks for cost-effective reuse choice. Without the safeguard to keep the prompt simple unless instrumentation shows meaningful cache reuse savings, the original failure mode is still possible.

C:

There is a legitimate use case for tenant-safe prompt reuse, but it does not supply the test or enforcement needed for cost-effective reuse choice. The design needs to keep the prompt simple unless instrumentation shows meaningful cache reuse savings.

D:

Consider its actual operating scope: reusable cached prompt prefix. The requested assurance is cost-effective reuse choice, which calls for an implementation that can keep the prompt simple unless instrumentation shows meaningful cache reuse savings, not merely for a related improvement.

Question 116

A service reuses a long policy prompt, but changing timestamps at the start of each request causes cache misses. A second workload changes tool-choice and reasoning-effort settings between otherwise identical calls and also loses reusable prefixes. Which TWO changes target the causes? Choose TWO.

  1. Keep the prompt simple unless instrumentation shows meaningful cache reuse savings.
  2. Move volatile timestamps after the stable region and verify cache creation versus cache reads.
  3. Warm the cache on every request while leaving changing timestamps at the start of the marked prefix.
  4. Increase cache lifetime without changing the volatile prompt blocks or inconsistent tool and reasoning configurations.
  5. Keep cache-affecting tool-choice and reasoning settings consistent within each comparable request cohort.

Explanation

Correct Answers

B:

Changing a timestamp before the cache breakpoint changes the prefix, producing writes instead of useful reads. Keeping volatile blocks outside the reusable prefix and checking cache creation/read counts distinguishes real reuse from optimistic billing estimates.

E:

Model configuration and tool-selection settings can change the cacheable request prefix even when policy text remains identical. Grouping equivalent calls under stable settings makes cache-read comparisons meaningful and helps distinguish config misses from text misses.

Incorrect Answers

A:

This is a valid architectural concern when optimizing cost-effective reuse choice. Here it leaves measured cache effectiveness and stability of cache-affecting model and tool settings unaddressed, whereas the intended change must move volatile timestamps after the stable region and verify cache creation versus cache reads before the case can be considered resolved.

C:

Cache warming is ineffective when the prefix key changes with each timestamp. The service will keep creating distinct entries instead of reusing a stable prefix, so the request structure must be corrected first.

D:

A longer time-to-live cannot create a hit between requests whose cache identity differs. Prefix stability and comparable request configuration are prerequisites for the read to reuse any stored cache entry.

Question 117

A shared prompt component is upgraded and downstream parsers begin failing silently. Which architecture adjustment is most appropriate?

  1. Version template contracts and test consuming services before releasing the shared update.
  2. Keep tenant-specific confidential material isolated and cache only appropriately scoped content.
  3. Publish a versioned reusable prompt module with release and regression review.
  4. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Explanation

Correct Answer

A:

Reusable prompts are dependencies; governance must control backward compatibility. Version the reusable artifact and instrument safe changes to shared prompt modules; reusing content does not automatically grant the right to safe changes to shared prompt modules.

Incorrect Answers

B:

Although tenant-safe prompt reuse can be valuable, it is not the acceptance condition in the question. The missing provision is safe changes to shared prompt modules, addressed by the control to version template contracts and test consuming services before releasing the shared update.

C:

It is aimed at a different outcome, modular policy prompt governance. No evidence is given that it provides safe changes to shared prompt modules; the needed mechanism is to version template contracts and test consuming services before releasing the shared update at the appropriate boundary.

D:

It emphasizes reusable cached prompt prefix without closing the stated gap in safe changes to shared prompt modules. By contrast, the remedy to version template contracts and test consuming services before releasing the shared update acts on the condition that makes this scenario fail.

Question 118

A long multi-turn support interaction keeps resending earlier instructions unchanged. Which next step is most defensible?

  1. Use an appropriate cacheable stable prefix while managing changing conversation context separately.
  2. Place stable material before volatile request-specific content and observe cache hit rates.
  3. Move volatile timestamps after the stable region and verify cache creation versus cache reads.
  4. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.

Explanation

Correct Answer

A:

Separating reusable instructions from evolving messages supports predictable caching behavior. Version the reusable artifact and instrument cache-aware multi-turn assembly; reusing content does not automatically grant the right to cache-aware multi-turn assembly.

Incorrect Answers

B:

The alternative could reduce risk associated with stable prefix ordering for cacheability, yet the described behavior requires cache-aware multi-turn assembly. That outcome depends on the capability to use an appropriate cacheable stable prefix while managing changing conversation context separately.

C:

The proposed measure is aimed at measured cache effectiveness, not cache-aware multi-turn assembly. The architecture must instead use an appropriate cacheable stable prefix while managing changing conversation context separately; a separate change is still needed for cache-aware multi-turn assembly.

D:

The relevant trade-off is not primarily reusable cached prompt prefix. A successful fix needs cache-aware multi-turn assembly; otherwise cache-aware multi-turn assembly remains unverified even after this change.

Question 119

A team maintains a Skill for incident handling, but the instructions grant no production privileges by themselves. Which approach should be recommended?

  1. Cache the stable prompt prefix using supported cache controls and measure cache-read tokens.
  2. Use an appropriate cacheable stable prefix while managing changing conversation context separately.
  3. Publish a versioned reusable prompt module with release and regression review.
  4. Treat Skills as guidance and enforce production permissions in identities and tool gateways.
  5. Package the procedure as a reviewed reusable Skill or equivalent team instruction artifact.

Explanation

Correct Answer

D:

Reusable procedural knowledge cannot replace authenticated authorization controls. Version the reusable artifact and instrument separating workflow guidance from enforcement; reusing content does not automatically grant the right to separating workflow guidance from enforcement.

Incorrect Answers

A:

Its main effect concerns reusable cached prompt prefix. The case explicitly hinges on separating workflow guidance from enforcement; to resolve it reliably, the implementation has to treat Skills as guidance and enforce production permissions in identities and tool gateways, which this choice does not establish.

B:

The option might improve cache-aware multi-turn assembly; that remains insufficient for separating workflow guidance from enforcement. The case is resolved by separating workflow guidance from enforcement, which depends on a design that will treat Skills as guidance and enforce production permissions in identities and tool gateways.

C:

The proposed action prioritizes modular policy prompt governance. That can coexist with the right solution, but it cannot replace separating workflow guidance from enforcement: the application must still treat Skills as guidance and enforce production permissions in identities and tool gateways.

E:

This addresses reusable specialized workflow guidance; however, the problem asks for separating workflow guidance from enforcement. Without the safeguard to treat Skills as guidance and enforce production permissions in identities and tool gateways, the original failure mode is still possible.

Question 120

A multi-tenant application uses one shared prompt that mixes each customer's secret taxonomy. Which change most directly satisfies this requirement?

  1. Keep tenant-specific confidential material isolated and cache only appropriately scoped content.
  2. Version template contracts and test consuming services before releasing the shared update.
  3. Place stable material before volatile request-specific content and observe cache hit rates.
  4. Keep the prompt simple unless instrumentation shows meaningful cache reuse savings.

Explanation

Correct Answer

A:

Prompt reuse must respect tenant data boundaries; efficiency does not authorize cross-customer disclosure. Version the reusable artifact and instrument tenant-safe prompt reuse; reusing content does not automatically grant the right to tenant-safe prompt reuse.

Incorrect Answers

B:

That is primarily a technique for safe changes to shared prompt modules. It lacks the explicit measure for tenant-safe prompt reuse that is necessary here, namely a system that will keep tenant-specific confidential material isolated and cache only appropriately scoped content.

C:

Improving stable prefix ordering for cacheability does not imply tenant-safe prompt reuse. The selected design must keep tenant-specific confidential material isolated and cache only appropriately scoped content, whereas this choice omits that direct protection or verification step.

D:

This recommendation targets cost-effective reuse choice at a different point in the workflow. It leaves tenant-safe prompt reuse outside the design contract and does not require the team to keep tenant-specific confidential material isolated and cache only appropriately scoped content.

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