Question 850
In an after-sales issue resolver, the acceptance criteria require that file writes are blocked outside an approved workspace and that a truncated response is not mistaken for successful completion. Which paired implementation meets both?
- check resolved target paths in the pre-tool policy gate; and interpret every non-tool stop reason as a successful final answer
- tell the model not to leave the workspace; and interpret every non-tool stop reason as a successful final answer
- check resolved target paths in the pre-tool policy gate; and handle max_tokens as truncation rather than end_turn
- tell the model not to leave the workspace; and handle max_tokens as truncation rather than end_turn
Explanation
Correct Answer
C:In an after-sales issue resolver, a boundary check on the actual tool argument enforces the permitted filesystem scope; alongside this, reaching an output limit is a stop condition but does not establish task completion, satisfying the distinct requirements that file writes are blocked outside an approved workspace and that a truncated response is not mistaken for successful completion.
Incorrect Answers
A:In an after-sales issue resolver, a boundary check on the actual tool argument enforces the permitted filesystem scope, 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.
B:In an after-sales issue resolver, language instructions do not intercept a disallowed filesystem operation and a length-limited result may be incomplete or unusable; the design would fail both conditions: file writes are blocked outside an approved workspace and a truncated response is not mistaken for successful completion.
D:In an after-sales issue resolver, reaching an output limit is a stop condition but does not establish task completion, but language instructions do not intercept a disallowed filesystem operation; therefore the separate requirement that file writes are blocked outside an approved workspace would remain unsatisfied.
Question 851
In a mobile client bug-fix task, the acceptance criteria require that API conventions apply only to source files under an API directory and that only one approved write tool is callable in a sensitive stage. Which paired implementation meets both?
- put API-specific formatting rules in always-on project guidance; and restrict the stage's allowed tool set and verify permissions in the executor
- put API-specific formatting rules in always-on project guidance; and let the model select from a broad global list of tools
- add a .claude/rules file with paths matching the API subtree; and restrict the stage's allowed tool set and verify permissions in the executor
- add a .claude/rules file with paths matching the API subtree; and let the model select from a broad global list of tools
Explanation
Correct Answer
C:In a mobile client bug-fix task, path-scoped rules load when the target context matches, keeping unrelated tasks clean; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that API conventions apply only to source files under an API directory and that only one approved write tool is callable in a sensitive stage.
Incorrect Answers
A:In a mobile client bug-fix task, capability scoping narrows possible side effects before model selection, but frontend and documentation tasks then receive irrelevant instructions; therefore the separate requirement that API conventions apply only to source files under an API directory would remain unsatisfied.
B:In a mobile client bug-fix task, frontend and documentation tasks then receive irrelevant instructions and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: API conventions apply only to source files under an API directory and only one approved write tool is callable in a sensitive stage.
D:In a mobile client bug-fix task, path-scoped rules load when the target context matches, keeping unrelated tasks clean, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.
Question 852
A team operating a multi-source competitor research system wants to establish two separate behaviors: a selector accepts only supported operation names; in addition, a large research job combines specialized findings into one answer. Which plan implements both?
- ask the model to invent a suitable action string; and have all subagents independently publish the final answer
- declare an operation enum in the schema and reject values outside it in the tool handler; and have all subagents independently publish the final answer
- ask the model to invent a suitable action string; and use a coordinator that delegates focused tasks and owns final synthesis
- declare an operation enum in the schema and reject values outside it in the tool handler; and use a coordinator that delegates focused tasks and owns final synthesis
Explanation
Correct Answer
D:In a multi-source competitor research system, schema constraints guide valid selections and runtime validation blocks unsupported operation values; alongside this, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, satisfying the distinct requirements that a selector accepts only supported operation names and that a large research job combines specialized findings into one answer.
Incorrect Answers
A:In a multi-source competitor research system, free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist and independent final outputs offer no single point to reconcile contradictions; the design would fail both conditions: a selector accepts only supported operation names and a large research job combines specialized findings into one answer.
B:In a multi-source competitor research system, schema constraints guide valid selections and runtime validation blocks unsupported operation values, but independent final outputs offer no single point to reconcile contradictions; therefore the separate requirement that a large research job combines specialized findings into one answer would remain unsatisfied.
C:In a multi-source competitor research system, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, but free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist; therefore the separate requirement that a selector accepts only supported operation names would remain unsatisfied.
Question 853
In a purchase-order parsing service, the acceptance criteria require that the reviewer does not simply echo the generator's confidence and that a missing value is represented without fabricating a string. Which paired implementation meets both?
- give the reviewer the source and rubric, not only the draft's self-rating; and allow null in the field schema and define its semantics
- provide the generator's score as the sole review criterion; and allow null in the field schema and define its semantics
- provide the generator's score as the sole review criterion; and force the model to populate every unknown value with a guess
- give the reviewer the source and rubric, not only the draft's self-rating; and force the model to populate every unknown value with a guess
Explanation
Correct Answer
A:In a purchase-order parsing service, independent evidence lets a critic challenge unsupported assertions; alongside this, explicit nullable types distinguish genuine absence from empty or invented data, satisfying the distinct requirements that the reviewer does not simply echo the generator's confidence and that a missing value is represented without fabricating a string.
Incorrect Answers
B:In a purchase-order parsing service, explicit nullable types distinguish genuine absence from empty or invented data, but anchoring on a self-assigned grade hides actual defects; therefore the separate requirement that the reviewer does not simply echo the generator's confidence would remain unsatisfied.
C:In a purchase-order parsing service, anchoring on a self-assigned grade hides actual defects and fabricated values preserve schema appearance but destroy factual accuracy; the design would fail both conditions: the reviewer does not simply echo the generator's confidence and a missing value is represented without fabricating a string.
D:In a purchase-order parsing service, independent evidence lets a critic challenge unsupported assertions, but fabricated values preserve schema appearance but destroy factual accuracy; therefore the separate requirement that a missing value is represented without fabricating a string would remain unsatisfied.
Question 854
In a technical review of a continuous integration repair assistant, the architect must address the following constraints together: documentation-only conventions do not dilute code-editing tasks; developers can explicitly invoke an established project procedure. Which change set is most defensible?
- scope documentation style rules to matching documentation paths; and write undocumented one-off ad hoc prompts for each engineer
- scope documentation style rules to matching documentation paths; and make the skill available under a recognizable slash invocation
- place all documentation writing rules in a global user file; and write undocumented one-off ad hoc prompts for each engineer
- place all documentation writing rules in a global user file; and make the skill available under a recognizable slash invocation
Explanation
Correct Answer
B:In a continuous integration repair assistant, conditional loading keeps instruction context relevant to the file being worked on; alongside this, a discoverable workflow gives the team a consistent entry point for repetitive work, satisfying the distinct requirements that documentation-only conventions do not dilute code-editing tasks and that developers can explicitly invoke an established project procedure.
Incorrect Answers
A:In a continuous integration repair assistant, conditional loading keeps instruction context relevant to the file being worked on, 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.
C:In a continuous integration repair assistant, those conventions will follow unrelated code tasks and unshared prompts make results hard to reproduce and review; the design would fail both conditions: documentation-only conventions do not dilute code-editing tasks and developers can explicitly invoke an established project procedure.
D:In a continuous integration repair assistant, a discoverable workflow gives the team a consistent entry point for repetitive work, but those conventions will follow unrelated code tasks; therefore the separate requirement that documentation-only conventions do not dilute code-editing tasks would remain unsatisfied.
Question 855
An incident postmortem for a developer productivity assistant requires controls so that a straightforward lookup avoids unnecessary agent coordination and that a tool receives a typed and bounded request. Which paired remedy covers both failure modes?
- spawn a coordinator plus multiple specialists for every trivial query; and define required properties and types in the input schema and validate arguments at the execution boundary
- spawn a coordinator plus multiple specialists for every trivial query; and accept one unstructured free-text argument for every operation
- use one focused tool-assisted agent for the bounded task; and accept one unstructured free-text argument for every operation
- use one focused tool-assisted agent for the bounded task; and define required properties and types in the input schema and validate arguments at the execution boundary
Explanation
Correct Answer
D:In a developer productivity assistant, orchestration overhead is not justified when there is no useful specialization or concurrency; alongside this, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, satisfying the distinct requirements that a straightforward lookup avoids unnecessary agent coordination and that a tool receives a typed and bounded request.
Incorrect Answers
A:In a developer productivity assistant, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, but extra agents add latency and handoff risk without new capabilities; therefore the separate requirement that a straightforward lookup avoids unnecessary agent coordination would remain unsatisfied.
B:In a developer productivity assistant, extra agents add latency and handoff risk without new capabilities and unconstrained prose leaves parsing and validation errors to ad hoc handler inference; the design would fail both conditions: a straightforward lookup avoids unnecessary agent coordination and a tool receives a typed and bounded request.
C:In a developer productivity assistant, orchestration overhead is not justified when there is no useful specialization or concurrency, but unconstrained prose leaves parsing and validation errors to ad hoc handler inference; therefore the separate requirement that a tool receives a typed and bounded request would remain unsatisfied.
Question 856
The architect for an automated CI review service needs to ensure that few-shot material does not contain contradictory answer labels. What should the team implement?
- keep historical examples even after the labeling policy changes
- audit examples against the current decision rubric before use
- use a compact sample covering common cases and one important edge case
- include contrasting positive and negative demonstrations
Explanation
Correct Answer
B:For an automated CI review service, consistent labels reinforce the intended criteria rather than training ambiguity into the prompt; this directly establishes that few-shot material does not contain contradictory answer labels instead of relying on an unrelated workflow control.
Incorrect Answers
A:In an automated CI review service, stale demonstrations can contradict the updated standard; as a result, the stated requirement that few-shot material does not contain contradictory answer labels would still not be met.
C:Although high-signal examples guide the task without overloading context, that only supports the distinct goal that example selection stays relevant to the current workload, not the requirement that few-shot material does not contain contradictory answer labels in an automated CI review service.
D:Although near-boundary examples communicate the decisive distinction and reduce false positives, that only supports the distinct goal that a model learns a boundary between superficially similar cases, not the requirement that few-shot material does not contain contradictory answer labels in an automated CI review service.
Question 857
While preparing a frontend component repair effort for deployment, engineers must ensure that a developer has private preferences that should not change team guidance; they must also ensure that a coding agent inspects a known source file without changing it. Which combination best satisfies those requirements?
- add private preferences to the shared repository CLAUDE.md; and use Read on the identified file
- place personal instructions in the user-level CLAUDE.md; and use Read on the identified file
- add private preferences to the shared repository CLAUDE.md; and run arbitrary shell commands to modify the file during inspection
- place personal instructions in the user-level CLAUDE.md; and run arbitrary shell commands to modify the file during inspection
Explanation
Correct Answer
B:In a frontend component repair effort, global personal guidance is available to that user's sessions without committing preferences to the project; alongside this, file reading provides exact content for analysis without executing the project, satisfying the distinct requirements that a developer has private preferences that should not change team guidance and that a coding agent inspects a known source file without changing it.
Incorrect Answers
A:In a frontend component repair effort, file reading provides exact content for analysis without executing the project, but project instructions would impose one person's settings on the whole team; therefore the separate requirement that a developer has private preferences that should not change team guidance would remain unsatisfied.
C:In a frontend component repair effort, project instructions would impose one person's settings on the whole team and mutation is unnecessary for a read-only code review; the design would fail both conditions: a developer has private preferences that should not change team guidance and a coding agent inspects a known source file without changing it.
D:In a frontend component repair effort, global personal guidance is available to that user's sessions without committing preferences to the project, but mutation is unnecessary for a read-only code review; therefore the separate requirement that a coding agent inspects a known source file without changing it would remain unsatisfied.
Question 858
Production readiness for a repository search copilot depends on ensuring that a common security rule remains active across the project and that an existing file receives a precise localized replacement. Select the most appropriate combined approach.
- keep project-wide security guidance in shared instructions rather than a narrow path glob; and overwrite the whole file with a newly generated copy
- scope the security instruction only to one unrelated test directory; and overwrite the whole file with a newly generated copy
- scope the security instruction only to one unrelated test directory; and use Edit for an exact targeted change
- keep project-wide security guidance in shared instructions rather than a narrow path glob; and use Edit for an exact targeted change
Explanation
Correct Answer
D:In a repository search copilot, cross-cutting obligations should not disappear when an agent changes directories; alongside this, surgical edits preserve unrelated lines and provide reviewable diffs, satisfying the distinct requirements that a common security rule remains active across the project and that an existing file receives a precise localized replacement.
Incorrect Answers
A:In a repository search copilot, cross-cutting obligations should not disappear when an agent changes directories, 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.
B:In a repository search copilot, other code paths would lack the universal control and full replacement risks losing unrelated code and formatting; the design would fail both conditions: a common security rule remains active across the project and an existing file receives a precise localized replacement.
C:In a repository search copilot, surgical edits preserve unrelated lines and provide reviewable diffs, but other code paths would lack the universal control; therefore the separate requirement that a common security rule remains active across the project would remain unsatisfied.
Question 859
In a technical review of a pull-request review pipeline, the architect must address the following constraints together: a pull-request bot runs with minimum necessary authority; the agent executes tests and examines their exit status. Which change set is most defensible?
- give the bot administrator credentials to avoid permission failures; and inspect the test configuration only with Read and claim tests passed
- implement only scope runner credentials, worktree access, and allowed tools to its task; make no corresponding change for the second requirement
- give the bot administrator credentials to avoid permission failures; and use Bash with an approved test command
- scope runner credentials, worktree access, and allowed tools to its task; and use Bash with an approved test command
- scope runner credentials, worktree access, and allowed tools to its task; and inspect the test configuration only with Read and claim tests passed
Explanation
Correct Answer
D:In a pull-request review pipeline, CI identity and tool permissions control real write capabilities independent of model instructions; alongside this, the shell can run build tools and return execution feedback that Read cannot supply, satisfying the distinct requirements that a pull-request bot runs with minimum necessary authority and that the agent executes tests and examines their exit status.
Incorrect Answers
A:In a pull-request review pipeline, broad credentials increase the blast radius of a compromised or mistaken job and reading configuration does not execute a test suite; the design would fail both conditions: a pull-request bot runs with minimum necessary authority and the agent executes tests and examines their exit status.
B:In a pull-request review pipeline, CI identity and tool permissions control real write capabilities independent of model instructions, but the independent mechanism for the other criterion is absent: the shell can run build tools and return execution feedback that Read cannot supply; as written, the design does not ensure that the agent executes tests and examines their exit status.
C:In a pull-request review pipeline, the shell can run build tools and return execution feedback that Read cannot supply, 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.
E:In a pull-request review pipeline, CI identity and tool permissions control real write capabilities independent of model instructions, but reading configuration does not execute a test suite; therefore the separate requirement that the agent executes tests and examines their exit status would remain unsatisfied.
Question 860
In a technical review of a service-credit approval assistant, the architect must address the following constraints together: a changed account record supersedes an old conversational value; an extraction error is caught before storage. Which change set is most defensible?
- reuse the value from the first turn without checking for change; and validate parsed data against application rules and source constraints
- refresh the authoritative source before a consequential write; and validate parsed data against application rules and source constraints
- refresh the authoritative source before a consequential write; and write the response to the database without checking required invariants
- implement only refresh the authoritative source before a consequential write; make no corresponding change for the second requirement
- reuse the value from the first turn without checking for change; and write the response to the database without checking required invariants
Explanation
Correct Answer
B:In a service-credit approval assistant, current external state protects against stale facts preserved in context; alongside this, local validation detects missing cross-field relationships even when the JSON is syntactically valid, satisfying the distinct requirements that a changed account record supersedes an old conversational value and that an extraction error is caught before storage.
Incorrect Answers
A:In a service-credit approval assistant, local validation detects missing cross-field relationships even when the JSON is syntactically valid, but conversations do not automatically reflect later database updates; therefore the separate requirement that a changed account record supersedes an old conversational value would remain unsatisfied.
C:In a service-credit approval assistant, current external state protects against stale facts preserved in context, but valid-looking output may still violate business rules; therefore the separate requirement that an extraction error is caught before storage would remain unsatisfied.
D:In a service-credit approval assistant, current external state protects against stale facts preserved in context, but the independent mechanism for the other criterion is absent: local validation detects missing cross-field relationships even when the JSON is syntactically valid; as written, the design does not ensure that an extraction error is caught before storage.
E:In a service-credit approval assistant, conversations do not automatically reflect later database updates and valid-looking output may still violate business rules; the design would fail both conditions: a changed account record supersedes an old conversational value and an extraction error is caught before storage.