Question 450
In a subscription support service, the acceptance criteria require that a destructive tool receives human authorization at execution time and that a truncated response is not mistaken for successful completion. Which paired implementation meets both?
- implement only interrupt or deny the tool until an authorization callback approves it; make no corresponding change for the second requirement
- collect a general approval at the start of the conversation; and interpret every non-tool stop reason as a successful final answer
- collect a general approval at the start of the conversation; and handle max_tokens as truncation rather than end_turn
- interrupt or deny the tool until an authorization callback approves it; and interpret every non-tool stop reason as a successful final answer
- interrupt or deny the tool until an authorization callback approves it; and handle max_tokens as truncation rather than end_turn
Explanation
Correct Answer
E:In a subscription support service, execution gates make the approval binding on the selected action and inputs; alongside this, reaching an output limit is a stop condition but does not establish task completion, satisfying the distinct requirements that a destructive tool receives human authorization at execution time and that a truncated response is not mistaken for successful completion.
Incorrect Answers
A:In a subscription support service, execution gates make the approval binding on the selected action and inputs, but the independent mechanism for the other criterion is absent: reaching an output limit is a stop condition but does not establish task completion; as written, the design does not ensure that a truncated response is not mistaken for successful completion.
B:In a subscription support service, blanket consent does not verify the later high-risk operation and a length-limited result may be incomplete or unusable; the design would fail both conditions: a destructive tool receives human authorization at execution time and a truncated response is not mistaken for successful completion.
C:In a subscription support service, reaching an output limit is a stop condition but does not establish task completion, but blanket consent does not verify the later high-risk operation; therefore the separate requirement that a destructive tool receives human authorization at execution time would remain unsatisfied.
D:In a subscription support service, execution gates make the approval binding on the selected action and inputs, but a length-limited result may be incomplete or unusable; therefore the separate requirement that a truncated response is not mistaken for successful completion would remain unsatisfied.
Question 451
Before expanding a repository change-review job, the owner must demonstrate that repeated delivery of one action request cannot create duplicate writes, while also demonstrating that two teams' analyses are reconciled before publication. Which design provides both controls?
- blindly resubmit the same write after every timeout; and add a synthesis stage with explicit conflict-resolution criteria
- blindly resubmit the same write after every timeout; and publish whichever branch finishes last
- use an idempotency key and confirm the prior commit before retrying; and publish whichever branch finishes last
- use an idempotency key and confirm the prior commit before retrying; and add a synthesis stage with explicit conflict-resolution criteria
Explanation
Correct Answer
D:In a repository change-review job, side-effecting operations need deduplication against timeouts and repeated messages; alongside this, merging divergent work requires an authoritative step rather than choosing by arrival time, satisfying the distinct requirements that repeated delivery of one action request cannot create duplicate writes and that two teams' analyses are reconciled before publication.
Incorrect Answers
A:In a repository change-review job, merging divergent work requires an authoritative step rather than choosing by arrival time, but the first attempt might have committed despite a missing acknowledgment; therefore the separate requirement that repeated delivery of one action request cannot create duplicate writes would remain unsatisfied.
B:In a repository change-review job, the first attempt might have committed despite a missing acknowledgment and run order is not an evidence or quality standard; the design would fail both conditions: repeated delivery of one action request cannot create duplicate writes and two teams' analyses are reconciled before publication.
C:In a repository change-review job, side-effecting operations need deduplication against timeouts and repeated messages, but run order is not an evidence or quality standard; therefore the separate requirement that two teams' analyses are reconciled before publication would remain unsatisfied.
Question 452
In a technical review of an engineering knowledge assistant, the architect must address the following constraints together: a long codebase exploration maintains navigation across stages; test-specific naming conventions run only when touching test files. Which change set is most defensible?
- store complete file contents repeatedly in every handoff; and apply the same test naming rule to every source file
- store complete file contents repeatedly in every handoff; and use a test-file glob in the rules frontmatter
- keep a concise map of relevant files, symbols, and open questions; and apply the same test naming rule to every source file
- keep a concise map of relevant files, symbols, and open questions; and use a test-file glob in the rules frontmatter
Explanation
Correct Answer
D:In an engineering knowledge assistant, a durable index lets later analysis re-open precise evidence as needed; alongside this, glob matching limits enforcement guidance to the intended file families, satisfying the distinct requirements that a long codebase exploration maintains navigation across stages and that test-specific naming conventions run only when touching test files.
Incorrect Answers
A:In an engineering knowledge assistant, duplicated source text overwhelms the window and becomes stale and production files and configuration do not share the test naming context; the design would fail both conditions: a long codebase exploration maintains navigation across stages and test-specific naming conventions run only when touching test files.
B:In an engineering knowledge assistant, glob matching limits enforcement guidance to the intended file families, but duplicated source text overwhelms the window and becomes stale; therefore the separate requirement that a long codebase exploration maintains navigation across stages would remain unsatisfied.
C:In an engineering knowledge assistant, a durable index lets later analysis re-open precise evidence as needed, 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.
Question 453
An architecture review of a code policy conformance job finds two missing guarantees: the repository can review and version its custom workflows; a small approved typo fix is completed without excessive planning. What two-part change closes both gaps?
- distribute the canonical skill only through private direct messages; and use direct execution for the limited reviewed edit
- distribute the canonical skill only through private direct messages; and launch a multi-stage planning effort for a single known line
- store project skills in the repository's .claude/skills structure; and launch a multi-stage planning effort for a single known line
- store project skills in the repository's .claude/skills structure; and use direct execution for the limited reviewed edit
Explanation
Correct Answer
D:In a code policy conformance job, version-controlled skills evolve alongside tests and conventions with code review; alongside this, a bounded low-risk change does not require a long exploratory workflow, satisfying the distinct requirements that the repository can review and version its custom workflows and that a small approved typo fix is completed without excessive planning.
Incorrect Answers
A:In a code policy conformance job, a bounded low-risk change does not require a long exploratory workflow, but unversioned copies lose the team's approved definition; therefore the separate requirement that the repository can review and version its custom workflows would remain unsatisfied.
B:In a code policy conformance job, unversioned copies lose the team's approved definition and extra ceremony adds latency without materially lowering risk; the design would fail both conditions: the repository can review and version its custom workflows and a small approved typo fix is completed without excessive planning.
C:In a code policy conformance job, version-controlled skills evolve alongside tests and conventions with code review, but extra ceremony adds latency without materially lowering risk; therefore the separate requirement that a small approved typo fix is completed without excessive planning would remain unsatisfied.
Question 454
In a payment microservice repository, the acceptance criteria require that the repository can review and version its custom workflows and that test-specific naming conventions run only when touching test files. Which paired implementation meets both?
- store project skills in the repository's .claude/skills structure; and use a test-file glob in the rules frontmatter
- distribute the canonical skill only through private direct messages; and use a test-file glob in the rules frontmatter
- distribute the canonical skill only through private direct messages; and apply the same test naming rule to every source file
- store project skills in the repository's .claude/skills structure; and apply the same test naming rule to every source file
Explanation
Correct Answer
A:In a payment microservice repository, version-controlled skills evolve alongside tests and conventions with code review; alongside this, glob matching limits enforcement guidance to the intended file families, satisfying the distinct requirements that the repository can review and version its custom workflows and that test-specific naming conventions run only when touching test files.
Incorrect Answers
B:In a payment microservice repository, glob matching limits enforcement guidance to the intended file families, but unversioned copies lose the team's approved definition; therefore the separate requirement that the repository can review and version its custom workflows would remain unsatisfied.
C:In a payment microservice repository, unversioned copies lose the team's approved definition and production files and configuration do not share the test naming context; the design would fail both conditions: the repository can review and version its custom workflows and test-specific naming conventions run only when touching test files.
D:In a payment microservice repository, version-controlled skills evolve alongside tests and conventions with code review, 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.
Question 455
A team operating a pull-request review pipeline wants to establish two separate behaviors: a specialist handoff retains its prerequisites and evidence; in addition, workload growth does not cause uncontrolled parallel fan-out. Which plan implements both?
- send a structured state packet with completed checks and unresolved decisions; and limit concurrency and schedule independent jobs against execution budgets
- handoff only a conversational sentence saying the stage is finished; and limit concurrency and schedule independent jobs against execution budgets
- handoff only a conversational sentence saying the stage is finished; and launch all possible child tasks at once without resource controls
- send a structured state packet with completed checks and unresolved decisions; and launch all possible child tasks at once without resource controls
Explanation
Correct Answer
A:In a pull-request review pipeline, a typed transition preserves obligations and facts between workflow stages; alongside this, bounded orchestration balances throughput with tool quotas and downstream service capacity, satisfying the distinct requirements that a specialist handoff retains its prerequisites and evidence and that workload growth does not cause uncontrolled parallel fan-out.
Incorrect Answers
B:In a pull-request review pipeline, bounded orchestration balances throughput with tool quotas and downstream service capacity, but the receiving stage cannot audit what actually passed; therefore the separate requirement that a specialist handoff retains its prerequisites and evidence would remain unsatisfied.
C:In a pull-request review pipeline, the receiving stage cannot audit what actually passed and unbounded fan-out can overwhelm tools and blow through cost budgets; the design would fail both conditions: a specialist handoff retains its prerequisites and evidence and workload growth does not cause uncontrolled parallel fan-out.
D:In a pull-request review pipeline, a typed transition preserves obligations and facts between workflow stages, but unbounded fan-out can overwhelm tools and blow through cost budgets; therefore the separate requirement that workload growth does not cause uncontrolled parallel fan-out would remain unsatisfied.
Question 456
In a merchant support assistant, the acceptance criteria require that contradictory evidence is reviewed before action and that the system distinguishes acceptable and unacceptable edge cases. Which paired implementation meets both?
- mark the inconsistency and request resolution or human verification; and provide only a broad topic label as the classification rule
- select the most recent-looking sentence without checking its source; and provide only a broad topic label as the classification rule
- mark the inconsistency and request resolution or human verification; and specify inclusion criteria and explicit exclusion conditions
- select the most recent-looking sentence without checking its source; and specify inclusion criteria and explicit exclusion conditions
Explanation
Correct Answer
C:In a merchant support assistant, conflicting source claims are a knowledge gap, not authorization to guess; alongside this, negative boundaries teach the model when a near-match must not trigger, satisfying the distinct requirements that contradictory evidence is reviewed before action and that the system distinguishes acceptable and unacceptable edge cases.
Incorrect Answers
A:In a merchant support assistant, conflicting source claims are a knowledge gap, not authorization to guess, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
B:In a merchant support assistant, recency alone cannot establish which contradictory record is correct and generic labels leave ambiguous boundary cases undefined; the design would fail both conditions: contradictory evidence is reviewed before action and the system distinguishes acceptable and unacceptable edge cases.
D:In a merchant support assistant, negative boundaries teach the model when a near-match must not trigger, but recency alone cannot establish which contradictory record is correct; therefore the separate requirement that contradictory evidence is reviewed before action would remain unsatisfied.
Question 457
While preparing a shipping-exception helpdesk for deployment, engineers must ensure that temporary service faults can be retried selectively; they must also ensure that tool output is normalized before it enters the agent context. Which combination best satisfies those requirements?
- include a retryable classification and bounded retry advice; and preprocess only the original user message
- retry every error with the same request indefinitely; and preprocess only the original user message
- retry every error with the same request indefinitely; and use a PostToolUse processing hook to standardize the returned data
- include a retryable classification and bounded retry advice; and use a PostToolUse processing hook to standardize the returned data
Explanation
Correct Answer
D:In a shipping-exception helpdesk, typed transient failures allow backoff without treating permanent errors the same way; alongside this, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, satisfying the distinct requirements that temporary service faults can be retried selectively and that tool output is normalized before it enters the agent context.
Incorrect Answers
A:In a shipping-exception helpdesk, typed transient failures allow backoff without treating permanent errors the same way, but input normalization does not correct inconsistent tool outputs; therefore the separate requirement that tool output is normalized before it enters the agent context would remain unsatisfied.
B:In a shipping-exception helpdesk, permission and validation failures will not heal through repetition and input normalization does not correct inconsistent tool outputs; the design would fail both conditions: temporary service faults can be retried selectively and tool output is normalized before it enters the agent context.
C:In a shipping-exception helpdesk, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, but permission and validation failures will not heal through repetition; therefore the separate requirement that temporary service faults can be retried selectively would remain unsatisfied.
Question 458
In an after-sales issue resolver, the acceptance criteria require that out-of-policy exceptions receive an authorized decision and that a broad tool catalog does not overwhelm a small task. Which paired implementation meets both?
- let the agent approve an exception whenever its wording sounds confident; and load all available MCP tools into every specialist turn
- let the agent approve an exception whenever its wording sounds confident; and supply only context-relevant tools for the current agent
- route the exception to a human approval step before execution; and load all available MCP tools into every specialist turn
- route the exception to a human approval step before execution; and supply only context-relevant tools for the current agent
Explanation
Correct Answer
D:In an after-sales issue resolver, approval is a workflow boundary separate from language-model confidence; alongside this, reducing irrelevant tool definitions improves selection and saves context, satisfying the distinct requirements that out-of-policy exceptions receive an authorized decision and that a broad tool catalog does not overwhelm a small task.
Incorrect Answers
A:In an after-sales issue resolver, model confidence is not delegated business authority and tool bloat makes the available actions harder to discriminate; the design would fail both conditions: out-of-policy exceptions receive an authorized decision and a broad tool catalog does not overwhelm a small task.
B:In an after-sales issue resolver, reducing irrelevant tool definitions improves selection and saves context, but model confidence is not delegated business authority; therefore the separate requirement that out-of-policy exceptions receive an authorized decision would remain unsatisfied.
C:In an after-sales issue resolver, approval is a workflow boundary separate from language-model confidence, but tool bloat makes the available actions harder to discriminate; therefore the separate requirement that a broad tool catalog does not overwhelm a small task would remain unsatisfied.
Question 459
In a technical review of a pull-request review pipeline, the architect must address the following constraints together: an existing file receives a precise localized replacement; project guidance fits within a limited context budget. Which change set is most defensible?
- use Edit for an exact targeted change; and paste complete design manuals into the top-level CLAUDE.md
- use Edit for an exact targeted change; and keep the top-level instruction set concise and move specialized details to scoped files
- overwrite the whole file with a newly generated copy; and keep the top-level instruction set concise and move specialized details to scoped files
- overwrite the whole file with a newly generated copy; and paste complete design manuals into the top-level CLAUDE.md
Explanation
Correct Answer
B:In a pull-request review pipeline, surgical edits preserve unrelated lines and provide reviewable diffs; alongside this, focused guidance preserves useful context and reduces instruction competition, satisfying the distinct requirements that an existing file receives a precise localized replacement and that project guidance fits within a limited context budget.
Incorrect Answers
A:In a pull-request review pipeline, surgical edits preserve unrelated lines and provide reviewable diffs, but indiscriminate loading spends tokens on facts unrelated to the active task; therefore the separate requirement that project guidance fits within a limited context budget would remain unsatisfied.
C:In a pull-request review pipeline, focused guidance preserves useful context and reduces instruction competition, but full replacement risks losing unrelated code and formatting; therefore the separate requirement that an existing file receives a precise localized replacement would remain unsatisfied.
D:In a pull-request review pipeline, full replacement risks losing unrelated code and formatting and indiscriminate loading spends tokens on facts unrelated to the active task; the design would fail both conditions: an existing file receives a precise localized replacement and project guidance fits within a limited context budget.
Question 460
A CI review service shares an MCP server definition across contributors without committing credentials, and engineers also need a reusable project procedure they can invoke explicitly. Which paired setup meets these requirements?
- inject credentials through approved environment or secret-management mechanisms; and write undocumented one-off ad hoc prompts for each engineer
- place long-lived access tokens directly in .mcp.json; and write undocumented one-off ad hoc prompts for each engineer
- inject credentials through approved environment or secret-management mechanisms; and make the skill available under a recognizable slash invocation
- place long-lived access tokens directly in .mcp.json; and make the skill available under a recognizable slash invocation
Explanation
Correct Answer
C:In an automated CI review service, separating credentials from versioned configuration limits accidental disclosure; alongside this, a discoverable workflow gives the team a consistent entry point for repetitive work, satisfying the distinct requirements that secrets are not embedded in a shared MCP setup and that developers can explicitly invoke an established project procedure.
Incorrect Answers
A:In an automated CI review service, separating credentials from versioned configuration limits accidental disclosure, but unshared prompts make results hard to reproduce and review; therefore the separate requirement that developers can explicitly invoke an established project procedure would remain unsatisfied.
B:In an automated CI review service, repository history can expose tokens to everyone with code access and unshared prompts make results hard to reproduce and review; the design would fail both conditions: secrets are not embedded in a shared MCP setup and developers can explicitly invoke an established project procedure.
D:In an automated CI review service, a discoverable workflow gives the team a consistent entry point for repetitive work, but repository history can expose tokens to everyone with code access; therefore the separate requirement that secrets are not embedded in a shared MCP setup would remain unsatisfied.