Question 260
For a service dependency exploration tool, acceptance depends on demonstrating that test-specific naming conventions run only when touching test files. Which approach is the strongest fit?
- keep project-wide security guidance in shared instructions rather than a narrow path glob
- add a .claude/rules file with paths matching the API subtree
- create separate path-specific rule files for each package
- use a test-file glob in the rules frontmatter
- apply the same test naming rule to every source file
Explanation
Correct Answer
D:For a service dependency exploration tool, glob matching limits enforcement guidance to the intended file families; this directly establishes that test-specific naming conventions run only when touching test files instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although cross-cutting obligations should not disappear when an agent changes directories, that only supports the distinct goal that a common security rule remains active across the project, not the requirement that test-specific naming conventions run only when touching test files in a service dependency exploration tool.
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 test-specific naming conventions run only when touching test files in a service dependency exploration tool.
C:Although scoped conventions avoid contradictory patterns between codebases sharing a monorepo, that only supports the distinct goal that two nested packages follow distinct framework conventions, not the requirement that test-specific naming conventions run only when touching test files in a service dependency exploration tool.
E:In a service dependency exploration tool, production files and configuration do not share the test naming context; as a result, the stated requirement that test-specific naming conventions run only when touching test files would still not be met.
Question 261
An incident postmortem for a database migration coding project requires controls so that delegated investigations stay within bounded scope and that the developer inspects a suspicious implementation in context. Which paired remedy covers both failure modes?
- ask every subagent to investigate everything it can find; and read targeted code ranges and nearby dependencies
- specify the question, allowed sources, expected output, and stopping criterion; and read targeted code ranges and nearby dependencies
- ask every subagent to investigate everything it can find; and replace source inspection with a guessed architecture overview
- specify the question, allowed sources, expected output, and stopping criterion; and replace source inspection with a guessed architecture overview
Explanation
Correct Answer
B:In a database migration coding project, a task contract prevents specialist exploration from swallowing the coordinator's larger goal; alongside this, focused inspection preserves exact implementation detail without loading the whole codebase, satisfying the distinct requirements that delegated investigations stay within bounded scope and that the developer inspects a suspicious implementation in context.
Incorrect Answers
A:In a database migration coding project, focused inspection preserves exact implementation detail without loading the whole codebase, but unbounded exploration dilutes signal and inflates context and latency; therefore the separate requirement that delegated investigations stay within bounded scope would remain unsatisfied.
C:In a database migration coding project, unbounded exploration dilutes signal and inflates context and latency and a general overview cannot verify the specific logic being debugged; the design would fail both conditions: delegated investigations stay within bounded scope and the developer inspects a suspicious implementation in context.
D:In a database migration coding project, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but a general overview cannot verify the specific logic being debugged; therefore the separate requirement that the developer inspects a suspicious implementation in context would remain unsatisfied.
Question 262
While preparing a shared-library improvement effort for deployment, engineers must ensure that a handoff retains only action-relevant context; they must also ensure that a code investigation finds where a function is referenced. Which combination best satisfies those requirements?
- send every previous chat turn to each new worker; and use Grep to locate occurrences before opening focused files
- pass a compact structured record of facts, decisions, pending tasks, and sources; and use Grep to locate occurrences before opening focused files
- send every previous chat turn to each new worker; and ask for broad prose summaries of every package first
- pass a compact structured record of facts, decisions, pending tasks, and sources; and ask for broad prose summaries of every package first
Explanation
Correct Answer
B:In a shared-library improvement effort, focused handoffs reduce context size while protecting continuity-critical details; alongside this, symbol searching narrows the evidence to files that mention the target, satisfying the distinct requirements that a handoff retains only action-relevant context and that a code investigation finds where a function is referenced.
Incorrect Answers
A:In a shared-library improvement effort, symbol searching narrows the evidence to files that mention the target, but large histories include irrelevant or outdated information; therefore the separate requirement that a handoff retains only action-relevant context would remain unsatisfied.
C:In a shared-library improvement effort, large histories include irrelevant or outdated information and high-level summaries can miss the exact call site; the design would fail both conditions: a handoff retains only action-relevant context and a code investigation finds where a function is referenced.
D:In a shared-library improvement effort, focused handoffs reduce context size while protecting continuity-critical details, but high-level summaries can miss the exact call site; therefore the separate requirement that a code investigation finds where a function is referenced would remain unsatisfied.
Question 263
When designing a developer codebase exploration assistant, the requirement is not satisfied unless a coding agent inspects a known source file without changing it and all contributors receive the repository's stable engineering conventions. Which implementation addresses the two independent conditions?
- use Read on the identified file; and put team-wide rules only in one developer's user-level instructions
- run arbitrary shell commands to modify the file during inspection; and put concise shared guidance in the repository root CLAUDE.md
- run arbitrary shell commands to modify the file during inspection; and put team-wide rules only in one developer's user-level instructions
- use Read on the identified file; and put concise shared guidance in the repository root CLAUDE.md
Explanation
Correct Answer
D:In a developer codebase exploration assistant, file reading provides exact content for analysis without executing the project; alongside this, project instructions travel with the codebase and establish common architecture and build constraints, satisfying the distinct requirements that a coding agent inspects a known source file without changing it and that all contributors receive the repository's stable engineering conventions.
Incorrect Answers
A:In a developer codebase exploration assistant, file reading provides exact content for analysis without executing the project, but personal files do not distribute the intended conventions to other contributors; therefore the separate requirement that all contributors receive the repository's stable engineering conventions would remain unsatisfied.
B:In a developer codebase exploration assistant, project instructions travel with the codebase and establish common architecture and build constraints, 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.
C:In a developer codebase exploration assistant, mutation is unnecessary for a read-only code review and personal files do not distribute the intended conventions to other contributors; the design would fail both conditions: a coding agent inspects a known source file without changing it and all contributors receive the repository's stable engineering conventions.
Question 264
Before expanding a customer account helpdesk agent, the owner must demonstrate that a classifier avoids marking uncertain cases as confirmed violations, while also demonstrating that fast-changing information is checked against its publication date. Which design provides both controls?
- tell the model to flag anything that sounds suspicious; and reuse an old cached claim without its date
- define explicit positive evidence and an abstain or review category; and record source timestamps and refresh time-sensitive evidence
- tell the model to flag anything that sounds suspicious; and record source timestamps and refresh time-sensitive evidence
- define explicit positive evidence and an abstain or review category; and reuse an old cached claim without its date
Explanation
Correct Answer
B:In a customer account helpdesk agent, clear decision thresholds separate direct evidence from weak similarity; alongside this, freshness determines whether an otherwise credible fact applies now, satisfying the distinct requirements that a classifier avoids marking uncertain cases as confirmed violations and that fast-changing information is checked against its publication date.
Incorrect Answers
A:In a customer account helpdesk agent, vague semantic similarity raises false positives and stale evidence may no longer describe the current state; the design would fail both conditions: a classifier avoids marking uncertain cases as confirmed violations and fast-changing information is checked against its publication date.
C:In a customer account helpdesk agent, freshness determines whether an otherwise credible fact applies now, but vague semantic similarity raises false positives; therefore the separate requirement that a classifier avoids marking uncertain cases as confirmed violations would remain unsatisfied.
D:In a customer account helpdesk agent, clear decision thresholds separate direct evidence from weak similarity, but stale evidence may no longer describe the current state; therefore the separate requirement that fast-changing information is checked against its publication date would remain unsatisfied.
Question 265
An architecture review of a security-advisory aggregation workflow finds two missing guarantees: specialists return comparable artifacts for aggregation; multiple subagent outputs can be traced to their individual tasks. What two-part change closes both gaps?
- merge narrative responses by concatenating their text; and strip origin metadata from each response before merging
- give subagents a common results contract including claim, evidence, and status; and attach task IDs and source references to returned artifacts
- give subagents a common results contract including claim, evidence, and status; and strip origin metadata from each response before merging
- merge narrative responses by concatenating their text; and attach task IDs and source references to returned artifacts
Explanation
Correct Answer
B:In a security-advisory aggregation workflow, a typed handoff lets the coordinator compare like fields and detect missing support; alongside this, traceable results let the coordinator identify which delegation produced each claim, satisfying the distinct requirements that specialists return comparable artifacts for aggregation and that multiple subagent outputs can be traced to their individual tasks.
Incorrect Answers
A:In a security-advisory aggregation workflow, unstructured concatenation hides provenance and duplicate or conflicting claims and source-less aggregation impairs diagnosis and fact checking; the design would fail both conditions: specialists return comparable artifacts for aggregation and multiple subagent outputs can be traced to their individual tasks.
C:In a security-advisory aggregation workflow, a typed handoff lets the coordinator compare like fields and detect missing support, but source-less aggregation impairs diagnosis and fact checking; therefore the separate requirement that multiple subagent outputs can be traced to their individual tasks would remain unsatisfied.
D:In a security-advisory aggregation workflow, traceable results let the coordinator identify which delegation produced each claim, but unstructured concatenation hides provenance and duplicate or conflicting claims; therefore the separate requirement that specialists return comparable artifacts for aggregation would remain unsatisfied.
Question 266
The architect for a contract-analysis research network needs to ensure that a delegated reviewer has no production write capability. What should the team implement?
- give the reviewer every administrative tool and ask for restraint
- provide only the read-oriented tools required by that reviewer
- enforce the validator in application control flow, using forced tool_choice only with compatible models
- combine tool_choice with server-side policy checks
Explanation
Correct Answer
B:For a contract-analysis research network, agent-scoped tool exposure prevents a write path in a read-only role; this directly establishes that a delegated reviewer has no production write capability instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a contract-analysis research network, prompt restraint is weaker than withholding execution capability; as a result, the stated requirement that a delegated reviewer has no production write capability 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 delegated reviewer has no production write capability in a contract-analysis research network.
D:Although selection controls when a tool is proposed but does not grant permission to execute, that only supports the distinct goal that a forced tool call still honors business authorization, not the requirement that a delegated reviewer has no production write capability in a contract-analysis research network.
Question 267
In a financial statement data extractor, the engineering team must guarantee that ambiguous write timeouts do not trigger duplicate side effects. What is the most appropriate control?
- check operation status or use an idempotency key before retry
- return an explicit partial status with missing-item identifiers
- repeat the mutation immediately because no success message arrived
- return a non-retryable validation error with the field and expected constraint
Explanation
Correct Answer
A:For a financial statement data extractor, a timeout can occur after the server commits the action, so retry safety needs state checks; this directly establishes that ambiguous write timeouts do not trigger duplicate side effects instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although failure metadata preserves the difference between a sparse valid response and incomplete execution, that only supports the distinct goal that partial data is not presented as a complete successful result, not the requirement that ambiguous write timeouts do not trigger duplicate side effects in a financial statement data extractor.
C:In a financial statement data extractor, missing acknowledgment does not prove the first write was rolled back; as a result, the stated requirement that ambiguous write timeouts do not trigger duplicate side effects would still not be met.
D:Although field-specific feedback lets the caller fix the input before resubmission, that only supports the distinct goal that invalid parameters lead to a clear correction rather than a blind retry, not the requirement that ambiguous write timeouts do not trigger duplicate side effects in a financial statement data extractor.
Question 268
An audit of a payment microservice repository identifies two unmet requirements: a new agent gets only durable context from a completed job and a forced tool call still honors business authorization. Select TWO actions that remedy those particular deficiencies.
- treat a forced tool choice as equivalent to user approval
- initialize a fresh session with a verified structured summary
- combine tool_choice with server-side policy checks
- paste a full historical transcript into every new session
Explanation
Correct Answers
B:For a payment microservice repository, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, which directly establishes that a new agent gets only durable context from a completed job; the separate requirement that a forced tool call still honors business authorization is handled by a different action.
C:For a payment microservice repository, selection controls when a tool is proposed but does not grant permission to execute, which directly establishes that a forced tool call still honors business authorization; the separate requirement that a new agent gets only durable context from a completed job is handled by a different action.
Incorrect Answers
A:For a payment microservice repository, tool selection and authorization are different controls, so this option cannot establish that a forced tool call still honors business authorization; correctly addressing a new agent gets only durable context from a completed job elsewhere does not repair that deficiency.
D:For a payment microservice repository, irrelevant turns can consume context and revive outdated assumptions, so this option cannot establish that a new agent gets only durable context from a completed job; correctly addressing a forced tool call still honors business authorization elsewhere does not repair that deficiency.
Question 269
When designing a service dependency exploration tool, the requirement is not satisfied unless specialized agents work with only relevant permissions and near-overlapping retrieval tools are selected by actual boundary. Which implementation addresses the two independent conditions?
- define each subagent role and expose the minimum matching tools; and rely exclusively on short tool names for routing
- give every subagent the coordinator's complete tool inventory; and rely exclusively on short tool names for routing
- give every subagent the coordinator's complete tool inventory; and document examples and conditions where each tool must not be used
- define each subagent role and expose the minimum matching tools; and document examples and conditions where each tool must not be used
Explanation
Correct Answer
D:In a service dependency exploration tool, tool scoping shrinks both decision confusion and the blast radius of delegated actions; alongside this, contrastive guidance helps tool choice when resource names look similar, satisfying the distinct requirements that specialized agents work with only relevant permissions and that near-overlapping retrieval tools are selected by actual boundary.
Incorrect Answers
A:In a service dependency exploration tool, tool scoping shrinks both decision confusion and the blast radius of delegated actions, but names alone may not capture the distinction in scope or authorization; therefore the separate requirement that near-overlapping retrieval tools are selected by actual boundary would remain unsatisfied.
B:In a service dependency exploration tool, unneeded write or network tools expand risk without improving the specialist task and names alone may not capture the distinction in scope or authorization; the design would fail both conditions: specialized agents work with only relevant permissions and near-overlapping retrieval tools are selected by actual boundary.
C:In a service dependency exploration tool, contrastive guidance helps tool choice when resource names look similar, but unneeded write or network tools expand risk without improving the specialist task; therefore the separate requirement that specialized agents work with only relevant permissions would remain unsatisfied.
Question 270
While preparing a warranty claims assistant for deployment, engineers must ensure that a consequential claim receives independent human sign-off; they must also ensure that a machine consumer receives a schema-compliant JSON object. Which combination best satisfies those requirements?
- route high-impact or low-evidence results to an authorized reviewer; and use supported structured JSON output with a declared schema
- route high-impact or low-evidence results to an authorized reviewer; and rely only on a sentence requesting JSON with no validation
- accept model confidence as a substitute for authorization; and rely only on a sentence requesting JSON with no validation
- accept model confidence as a substitute for authorization; and use supported structured JSON output with a declared schema
Explanation
Correct Answer
A:In a warranty claims assistant, human approval supplies accountability where a mistaken model result has material cost; alongside this, constrained output enforces parseable structure and required field types at generation, satisfying the distinct requirements that a consequential claim receives independent human sign-off and that a machine consumer receives a schema-compliant JSON object.
Incorrect Answers
B:In a warranty claims assistant, human approval supplies accountability where a mistaken model result has material cost, but prompt-only formatting can still produce malformed or incomplete results; therefore the separate requirement that a machine consumer receives a schema-compliant JSON object would remain unsatisfied.
C:In a warranty claims assistant, a model score does not confer business or legal authority and prompt-only formatting can still produce malformed or incomplete results; the design would fail both conditions: a consequential claim receives independent human sign-off and a machine consumer receives a schema-compliant JSON object.
D:In a warranty claims assistant, constrained output enforces parseable structure and required field types at generation, but a model score does not confer business or legal authority; therefore the separate requirement that a consequential claim receives independent human sign-off would remain unsatisfied.