Anthropic CCA-F (Claude Certified Architect - Foundations (CCAR-F)) Practice Test 30

Question 290

Production readiness for an analyst research coordinator depends on ensuring that few-shot material does not contain contradictory answer labels and that each batch result is matched to its originating record. Select the most appropriate combined approach.

  1. audit examples against the current decision rubric before use; and assign stable custom IDs and map results by those IDs
  2. keep historical examples even after the labeling policy changes; and match returned results to input rows only by array position
  3. keep historical examples even after the labeling policy changes; and assign stable custom IDs and map results by those IDs
  4. audit examples against the current decision rubric before use; and match returned results to input rows only by array position

Explanation

Correct Answer

A:

In an analyst research coordinator, consistent labels reinforce the intended criteria rather than training ambiguity into the prompt; alongside this, asynchronous completion order need not match submission order, satisfying the distinct requirements that few-shot material does not contain contradictory answer labels and that each batch result is matched to its originating record.

Incorrect Answers

B:

In an analyst research coordinator, stale demonstrations can contradict the updated standard and out-of-order or failed items can corrupt record association; the design would fail both conditions: few-shot material does not contain contradictory answer labels and each batch result is matched to its originating record.

C:

In an analyst research coordinator, asynchronous completion order need not match submission order, but stale demonstrations can contradict the updated standard; therefore the separate requirement that few-shot material does not contain contradictory answer labels would remain unsatisfied.

D:

In an analyst research coordinator, consistent labels reinforce the intended criteria rather than training ambiguity into the prompt, but out-of-order or failed items can corrupt record association; therefore the separate requirement that each batch result is matched to its originating record would remain unsatisfied.

Question 291

In an automated test-generation workflow, the immediate design requirement is that a forced tool call still honors business authorization. Which change most directly establishes that behavior?

  1. supply only context-relevant tools for the current agent
  2. treat a forced tool choice as equivalent to user approval
  3. enforce the validator in application control flow, using forced tool_choice only with compatible models
  4. combine tool_choice with server-side policy checks

Explanation

Correct Answer

D:

For an automated test-generation workflow, selection controls when a tool is proposed but does not grant permission to execute; this directly establishes that a forced tool call still honors business authorization instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although reducing irrelevant tool definitions improves selection and saves context, that only supports the distinct goal that a broad tool catalog does not overwhelm a small task, not the requirement that a forced tool call still honors business authorization in an automated test-generation workflow.

B:

In an automated test-generation workflow, tool selection and authorization are different controls; as a result, the stated requirement that a forced tool call still honors business authorization would still not be met.

C:

Although application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, that only supports the distinct goal that a required validation step runs before the final response even when the model does not support forced tool choice, not the requirement that a forced tool call still honors business authorization in an automated test-generation workflow.

Question 292

In a source code audit helper, the immediate design requirement is that two nested packages follow distinct framework conventions. Which change most directly establishes that behavior?

  1. update the rule's paths glob to include the actual target paths
  2. add a .claude/rules file with paths matching the API subtree
  3. use a test-file glob in the rules frontmatter
  4. write one ambiguous instruction for both packages
  5. create separate path-specific rule files for each package

Explanation

Correct Answer

E:

For a source code audit helper, scoped conventions avoid contradictory patterns between codebases sharing a monorepo; this directly establishes that two nested packages follow distinct framework conventions instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although correct glob coverage determines whether conditional guidance is in context, that only supports the distinct goal that path-scoped rules are loaded for all intended source directories, not the requirement that two nested packages follow distinct framework conventions in a source code audit helper.

B:

Although path-scoped rules load when the target context matches, keeping unrelated tasks clean, that only supports the distinct goal that API conventions apply only to source files under an API directory, not the requirement that two nested packages follow distinct framework conventions in a source code audit helper.

C:

Although glob matching limits enforcement guidance to the intended file families, that only supports the distinct goal that test-specific naming conventions run only when touching test files, not the requirement that two nested packages follow distinct framework conventions in a source code audit helper.

D:

In a source code audit helper, the model must guess which framework convention applies; as a result, the stated requirement that two nested packages follow distinct framework conventions would still not be met.

Question 293

The architect for a security-advisory aggregation workflow needs to ensure that a classification uses a limited approved category set. What should the team implement?

  1. allow a free-form category for each case
  2. state the conjunction of required matching conditions
  3. specify inclusion criteria and explicit exclusion conditions
  4. define precise output labels and mapping rules

Explanation

Correct Answer

D:

For a security-advisory aggregation workflow, controlled categories reduce schema drift and make downstream analytics comparable; this directly establishes that a classification uses a limited approved category set instead of relying on an unrelated workflow control.

Incorrect Answers

A:

In a security-advisory aggregation workflow, unbounded labels fragment the intended taxonomy; as a result, the stated requirement that a classification uses a limited approved category set would still not be met.

B:

Although explicit multi-field criteria prevent a single suggestive field from dominating the outcome, that only supports the distinct goal that extracted records are labeled only when required fields agree, not the requirement that a classification uses a limited approved category set in a security-advisory aggregation workflow.

C:

Although negative boundaries teach the model when a near-match must not trigger, that only supports the distinct goal that the system distinguishes acceptable and unacceptable edge cases, not the requirement that a classification uses a limited approved category set in a security-advisory aggregation workflow.

Question 294

Tests for a merge-request policy gate will pass only if an approved plan is translated into controlled edits and tests and if test-specific naming conventions run only when touching test files. Which proposed design directly satisfies both checks?

  1. exit the planning stage and perform scoped implementation with verification; and apply the same test naming rule to every source file
  2. remain in read-only planning and claim the code was updated; and apply the same test naming rule to every source file
  3. exit the planning stage and perform scoped implementation with verification; and use a test-file glob in the rules frontmatter
  4. remain in read-only planning and claim the code was updated; and use a test-file glob in the rules frontmatter

Explanation

Correct Answer

C:

In a merge-request policy gate, planning describes intended operations while execution applies and checks them; alongside this, glob matching limits enforcement guidance to the intended file families, satisfying the distinct requirements that an approved plan is translated into controlled edits and tests and that test-specific naming conventions run only when touching test files.

Incorrect Answers

A:

In a merge-request policy gate, planning describes intended operations while execution applies and checks them, but production files and configuration do not share the test naming context; therefore the separate requirement that test-specific naming conventions run only when touching test files would remain unsatisfied.

B:

In a merge-request policy gate, a proposal alone does not modify repository state and production files and configuration do not share the test naming context; the design would fail both conditions: an approved plan is translated into controlled edits and tests and test-specific naming conventions run only when touching test files.

D:

In a merge-request policy gate, glob matching limits enforcement guidance to the intended file families, but a proposal alone does not modify repository state; therefore the separate requirement that an approved plan is translated into controlled edits and tests would remain unsatisfied.

Question 295

For a procurement document processing system, a reviewer identifies two independent obligations: a transient upstream outage is retried safely and a long workflow preserves confirmed facts separately from speculation. Which proposal should be approved?

  1. apply a bounded backoff only to classified retryable errors; and mark verified, user-reported, and unknown state explicitly
  2. implement only apply a bounded backoff only to classified retryable errors; make no corresponding change for the second requirement
  3. apply a bounded backoff only to classified retryable errors; and combine guesses and verified attributes in one unqualified summary
  4. retry access-denied and invalid-input errors indefinitely; and mark verified, user-reported, and unknown state explicitly
  5. retry access-denied and invalid-input errors indefinitely; and combine guesses and verified attributes in one unqualified summary

Explanation

Correct Answer

A:

In a procurement document processing system, transient failures can heal without re-running permanently invalid requests; alongside this, epistemic labels stop a tentative suggestion becoming a confirmed action parameter, satisfying the distinct requirements that a transient upstream outage is retried safely and that a long workflow preserves confirmed facts separately from speculation.

Incorrect Answers

B:

In a procurement document processing system, transient failures can heal without re-running permanently invalid requests, but the independent mechanism for the other criterion is absent: epistemic labels stop a tentative suggestion becoming a confirmed action parameter; as written, the design does not ensure that a long workflow preserves confirmed facts separately from speculation.

C:

In a procurement document processing system, transient failures can heal without re-running permanently invalid requests, but downstream operations may rely on an assumption as though it were checked; therefore the separate requirement that a long workflow preserves confirmed facts separately from speculation would remain unsatisfied.

D:

In a procurement document processing system, epistemic labels stop a tentative suggestion becoming a confirmed action parameter, but permanent failures require a fix or escalation rather than repetition; therefore the separate requirement that a transient upstream outage is retried safely would remain unsatisfied.

E:

In a procurement document processing system, permanent failures require a fix or escalation rather than repetition and downstream operations may rely on an assumption as though it were checked; the design would fail both conditions: a transient upstream outage is retried safely and a long workflow preserves confirmed facts separately from speculation.

Question 296

An incident postmortem for a deployment-readiness verification process requires controls so that a pull-request bot runs with minimum necessary authority and that the implementation plan receives stakeholder sign-off. Which paired remedy covers both failure modes?

  1. scope runner credentials, worktree access, and allowed tools to its task; and treat the agent's internally generated plan as implicit approval
  2. give the bot administrator credentials to avoid permission failures; and treat the agent's internally generated plan as implicit approval
  3. scope runner credentials, worktree access, and allowed tools to its task; and present ordered changes, risks, and verification steps before switching to execution
  4. give the bot administrator credentials to avoid permission failures; and present ordered changes, risks, and verification steps before switching to execution

Explanation

Correct Answer

C:

In a deployment-readiness verification process, CI identity and tool permissions control real write capabilities independent of model instructions; alongside this, an explicit review point aligns the agent's work with the authorized scope, satisfying the distinct requirements that a pull-request bot runs with minimum necessary authority and that the implementation plan receives stakeholder sign-off.

Incorrect Answers

A:

In a deployment-readiness verification process, CI identity and tool permissions control real write capabilities independent of model instructions, but the system cannot infer external authorization from its own reasoning; therefore the separate requirement that the implementation plan receives stakeholder sign-off would remain unsatisfied.

B:

In a deployment-readiness verification process, broad credentials increase the blast radius of a compromised or mistaken job and the system cannot infer external authorization from its own reasoning; the design would fail both conditions: a pull-request bot runs with minimum necessary authority and the implementation plan receives stakeholder sign-off.

D:

In a deployment-readiness verification process, an explicit review point aligns the agent's work with the authorized scope, but broad credentials increase the blast radius of a compromised or mistaken job; therefore the separate requirement that a pull-request bot runs with minimum necessary authority would remain unsatisfied.

Question 297

For a multi-source policy brief service, a reviewer identifies two independent obligations: a risk prompt handles missing supporting evidence honestly and confidence scores reflect available evidence and uncertainty. Which proposal should be approved?

  1. instruct the model to return unknown or needs-review when evidence is absent; and set confidence to high whenever the explanation is detailed
  2. require a definitive yes-or-no answer for every incomplete record; and calibrate confidence against known outcomes and source support
  3. require a definitive yes-or-no answer for every incomplete record; and set confidence to high whenever the explanation is detailed
  4. instruct the model to return unknown or needs-review when evidence is absent; and calibrate confidence against known outcomes and source support

Explanation

Correct Answer

D:

In a multi-source policy brief service, a defined abstention path avoids forced confident judgments without facts; alongside this, observed error rates and evidence quality are better than a fluent self-rating, satisfying the distinct requirements that a risk prompt handles missing supporting evidence honestly and that confidence scores reflect available evidence and uncertainty.

Incorrect Answers

A:

In a multi-source policy brief service, a defined abstention path avoids forced confident judgments without facts, but verbal detail is not a validated reliability estimate; therefore the separate requirement that confidence scores reflect available evidence and uncertainty would remain unsatisfied.

B:

In a multi-source policy brief service, observed error rates and evidence quality are better than a fluent self-rating, but forced binaries hide uncertainty as false certainty; therefore the separate requirement that a risk prompt handles missing supporting evidence honestly would remain unsatisfied.

C:

In a multi-source policy brief service, forced binaries hide uncertainty as false certainty and verbal detail is not a validated reliability estimate; the design would fail both conditions: a risk prompt handles missing supporting evidence honestly and confidence scores reflect available evidence and uncertainty.

Question 298

An audit of a purchase-order parsing service identifies two unmet requirements: a machine consumer receives a schema-compliant JSON object and a model learns a boundary between superficially similar cases. Select TWO actions that remedy those particular deficiencies.

  1. use supported structured JSON output with a declared schema
  2. rely only on a sentence requesting JSON with no validation
  3. include contrasting positive and negative demonstrations
  4. show only easy positive samples

Explanation

Correct Answers

A:

For a purchase-order parsing service, constrained output enforces parseable structure and required field types at generation, which directly establishes that a machine consumer receives a schema-compliant JSON object; the separate requirement that a model learns a boundary between superficially similar cases is handled by a different action.

C:

For a purchase-order parsing service, near-boundary examples communicate the decisive distinction and reduce false positives, which directly establishes that a model learns a boundary between superficially similar cases; the separate requirement that a machine consumer receives a schema-compliant JSON object is handled by a different action.

Incorrect Answers

B:

For a purchase-order parsing service, prompt-only formatting can still produce malformed or incomplete results, so this option cannot establish that a machine consumer receives a schema-compliant JSON object; correctly addressing a model learns a boundary between superficially similar cases elsewhere does not repair that deficiency.

D:

For a purchase-order parsing service, the model may generalize the label to unrelated but similar-looking items, so this option cannot establish that a model learns a boundary between superficially similar cases; correctly addressing a machine consumer receives a schema-compliant JSON object elsewhere does not repair that deficiency.

Question 299

In a merchant support assistant, the immediate design requirement is that a corrected attempt preserves a record of prior validation findings. Which change most directly establishes that behavior?

  1. record validation failure codes and field paths per attempt
  2. replace all earlier outputs without recording the validation history
  3. stop after defined retries and route unresolved cases to a reviewer
  4. retain the original source, response version, and retry feedback

Explanation

Correct Answer

D:

For a merchant support assistant, traceable attempts allow auditors to distinguish correction from silent overwrite; this directly establishes that a corrected attempt preserves a record of prior validation findings instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although granular observability reveals schema weaknesses and document patterns, that only supports the distinct goal that the team can diagnose which fields repeatedly fail extraction, not the requirement that a corrected attempt preserves a record of prior validation findings in a merchant support assistant.

B:

In a merchant support assistant, the reason for a changed value becomes untraceable; as a result, the stated requirement that a corrected attempt preserves a record of prior validation findings would still not be met.

C:

Although a bounded escalation path prevents infinite loops and invented resolutions, that only supports the distinct goal that persistent ambiguous data receives human review, not the requirement that a corrected attempt preserves a record of prior validation findings in a merchant support assistant.

Question 300

When designing a policy document normalization service, the requirement is not satisfied unless example selection stays relevant to the current workload and a corrected attempt preserves a record of prior validation findings. Which implementation addresses the two independent conditions?

  1. use a compact sample covering common cases and one important edge case; and retain the original source, response version, and retry feedback
  2. include dozens of unrelated demonstrations from other domains; and retain the original source, response version, and retry feedback
  3. use a compact sample covering common cases and one important edge case; and replace all earlier outputs without recording the validation history
  4. include dozens of unrelated demonstrations from other domains; and replace all earlier outputs without recording the validation history

Explanation

Correct Answer

A:

In a policy document normalization service, high-signal examples guide the task without overloading context; alongside this, traceable attempts allow auditors to distinguish correction from silent overwrite, satisfying the distinct requirements that example selection stays relevant to the current workload and that a corrected attempt preserves a record of prior validation findings.

Incorrect Answers

B:

In a policy document normalization service, traceable attempts allow auditors to distinguish correction from silent overwrite, but irrelevant examples dilute the pattern and consume tokens; therefore the separate requirement that example selection stays relevant to the current workload would remain unsatisfied.

C:

In a policy document normalization service, high-signal examples guide the task without overloading context, but the reason for a changed value becomes untraceable; therefore the separate requirement that a corrected attempt preserves a record of prior validation findings would remain unsatisfied.

D:

In a policy document normalization service, irrelevant examples dilute the pattern and consume tokens and the reason for a changed value becomes untraceable; the design would fail both conditions: example selection stays relevant to the current workload and a corrected attempt preserves a record of prior validation findings.

Claude Certified Architect - Foundations (CCAR-F) (CCA-F) Practice Tests