Question 310
In a static analysis automation, the acceptance criteria require that a risky refactor is evaluated before any files change and that all contributors receive the repository's stable engineering conventions. Which paired implementation meets both?
- use plan mode to inspect dependencies and propose steps before execution; and put team-wide rules only in one developer's user-level instructions
- let the agent immediately edit every matching file; and put concise shared guidance in the repository root CLAUDE.md
- use plan mode to inspect dependencies and propose steps before execution; and put concise shared guidance in the repository root CLAUDE.md
- let the agent immediately edit every matching file; and put team-wide rules only in one developer's user-level instructions
- implement only put concise shared guidance in the repository root CLAUDE.md; make no corresponding change for the first requirement
Explanation
Correct Answer
C:In a static analysis automation, planning separates investigation and approval from code mutation; alongside this, project instructions travel with the codebase and establish common architecture and build constraints, satisfying the distinct requirements that a risky refactor is evaluated before any files change and that all contributors receive the repository's stable engineering conventions.
Incorrect Answers
A:In a static analysis automation, planning separates investigation and approval from code mutation, 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 static analysis automation, project instructions travel with the codebase and establish common architecture and build constraints, but early writes can spread an unapproved assumption through the repository; therefore the separate requirement that a risky refactor is evaluated before any files change would remain unsatisfied.
D:In a static analysis automation, early writes can spread an unapproved assumption through the repository and personal files do not distribute the intended conventions to other contributors; the design would fail both conditions: a risky refactor is evaluated before any files change and all contributors receive the repository's stable engineering conventions.
E:In a static analysis automation, project instructions travel with the codebase and establish common architecture and build constraints, but the independent mechanism for the other criterion is absent: planning separates investigation and approval from code mutation; as written, the design does not ensure that a risky refactor is evaluated before any files change.
Question 311
In a returns-policy assistant, the immediate design requirement is that critical account identifiers survive a long support conversation. Which change most directly establishes that behavior?
- refresh the authoritative source before a consequential write
- store verified IDs and decisions in an explicit structured case-facts record
- rely only on a conversational summary of the earliest turns
- pass a compact structured record of facts, decisions, pending tasks, and sources
Explanation
Correct Answer
B:For a returns-policy assistant, durable structured state prevents essential exact values being lost during summarization; this directly establishes that critical account identifiers survive a long support conversation instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although current external state protects against stale facts preserved in context, that only supports the distinct goal that a changed account record supersedes an old conversational value, not the requirement that critical account identifiers survive a long support conversation in a returns-policy assistant.
C:In a returns-policy assistant, compression can omit or alter identifiers that later actions require; as a result, the stated requirement that critical account identifiers survive a long support conversation would still not be met.
D:Although focused handoffs reduce context size while protecting continuity-critical details, that only supports the distinct goal that a handoff retains only action-relevant context, not the requirement that critical account identifiers survive a long support conversation in a returns-policy assistant.
Question 312
The release gate for a monorepo testing overhaul requires that one developer keeps an MCP server private to their machine; it also requires that a new source file is created from supplied content. Which TWO actions meet the specified checks? Choose TWO.
- use Grep to create the source file
- use Write for file creation
- commit private workstation commands into the repository's shared MCP file
- use a user-local MCP configuration rather than committing project configuration
Explanation
Correct Answers
B:For a monorepo testing overhaul, writing a new artifact is appropriate when no existing target needs surgical modification, which directly establishes that a new source file is created from supplied content; the separate requirement that one developer keeps an MCP server private to their machine is handled by a different action.
D:For a monorepo testing overhaul, user scope is appropriate for personal endpoints and avoids distributing local paths, which directly establishes that one developer keeps an MCP server private to their machine; the separate requirement that a new source file is created from supplied content is handled by a different action.
Incorrect Answers
A:For a monorepo testing overhaul, search utilities do not create code artifacts, so this option cannot establish that a new source file is created from supplied content; correctly addressing one developer keeps an MCP server private to their machine elsewhere does not repair that deficiency.
C:For a monorepo testing overhaul, machine-specific commands can break teammates' environments, so this option cannot establish that one developer keeps an MCP server private to their machine; correctly addressing a new source file is created from supplied content elsewhere does not repair that deficiency.
Question 313
A team operating a symbol-search assistant wants to establish two separate behaviors: the agent executes tests and examines their exit status; in addition, a missing MCP capability is diagnosed before changing prompts. Which plan implements both?
- use Bash with an approved test command; and increase the system prompt length to compensate for disconnected tools
- use Bash with an approved test command; and verify server connection, transport, and exposed tool availability
- implement only use Bash with an approved test command; make no corresponding change for the second requirement
- inspect the test configuration only with Read and claim tests passed; and increase the system prompt length to compensate for disconnected tools
- inspect the test configuration only with Read and claim tests passed; and verify server connection, transport, and exposed tool availability
Explanation
Correct Answer
B:In a symbol-search assistant, the shell can run build tools and return execution feedback that Read cannot supply; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that the agent executes tests and examines their exit status and that a missing MCP capability is diagnosed before changing prompts.
Incorrect Answers
A:In a symbol-search assistant, the shell can run build tools and return execution feedback that Read cannot supply, but a model cannot call a capability absent from its available tool registry; therefore the separate requirement that a missing MCP capability is diagnosed before changing prompts would remain unsatisfied.
C:In a symbol-search assistant, the shell can run build tools and return execution feedback that Read cannot supply, but the independent mechanism for the other criterion is absent: tool discovery depends on a live configured integration, not just the prompt wording; as written, the design does not ensure that a missing MCP capability is diagnosed before changing prompts.
D:In a symbol-search assistant, reading configuration does not execute a test suite and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: the agent executes tests and examines their exit status and a missing MCP capability is diagnosed before changing prompts.
E:In a symbol-search assistant, tool discovery depends on a live configured integration, not just the prompt wording, 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 314
The release checklist for a procurement research assistant explicitly checks that the system distinguishes acceptable and unacceptable edge cases; it also checks that a failed retrieval agent does not masquerade as having found no matches. What coordinated solution meets the checklist?
- implement only specify inclusion criteria and explicit exclusion conditions; make no corresponding change for the second requirement
- provide only a broad topic label as the classification rule; and return a typed failure status with its origin to the coordinator
- specify inclusion criteria and explicit exclusion conditions; and return a typed failure status with its origin to the coordinator
- provide only a broad topic label as the classification rule; and convert every retrieval failure into an empty list
- specify inclusion criteria and explicit exclusion conditions; and convert every retrieval failure into an empty list
Explanation
Correct Answer
C:In a procurement research assistant, negative boundaries teach the model when a near-match must not trigger; alongside this, an operational error must remain distinguishable from a valid empty result, satisfying the distinct requirements that the system distinguishes acceptable and unacceptable edge cases and that a failed retrieval agent does not masquerade as having found no matches.
Incorrect Answers
A:In a procurement research assistant, negative boundaries teach the model when a near-match must not trigger, but the independent mechanism for the other criterion is absent: an operational error must remain distinguishable from a valid empty result; as written, the design does not ensure that a failed retrieval agent does not masquerade as having found no matches.
B:In a procurement research assistant, an operational error must remain distinguishable from a valid empty result, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
D:In a procurement research assistant, generic labels leave ambiguous boundary cases undefined and the final report could incorrectly claim no sources exist; the design would fail both conditions: the system distinguishes acceptable and unacceptable edge cases and a failed retrieval agent does not masquerade as having found no matches.
E:In a procurement research assistant, negative boundaries teach the model when a near-match must not trigger, but the final report could incorrectly claim no sources exist; therefore the separate requirement that a failed retrieval agent does not masquerade as having found no matches would remain unsatisfied.
Question 315
For a build verification pipeline, a reviewer identifies two independent obligations: secrets are not embedded in a shared MCP setup and tool-call logging does not modify a successful tool result. Which proposal should be approved?
- place long-lived access tokens directly in .mcp.json; and rewrite every tool result as a free-form paraphrase
- inject credentials through approved environment or secret-management mechanisms; and use an observation-only hook for telemetry when rewriting is unnecessary
- inject credentials through approved environment or secret-management mechanisms; and rewrite every tool result as a free-form paraphrase
- place long-lived access tokens directly in .mcp.json; and use an observation-only hook for telemetry when rewriting is unnecessary
Explanation
Correct Answer
B:In a build verification pipeline, separating credentials from versioned configuration limits accidental disclosure; alongside this, separating instrumentation from mutation reduces the risk of corrupting evidence, satisfying the distinct requirements that secrets are not embedded in a shared MCP setup and that tool-call logging does not modify a successful tool result.
Incorrect Answers
A:In a build verification pipeline, repository history can expose tokens to everyone with code access and summaries can discard fields that subsequent steps require; the design would fail both conditions: secrets are not embedded in a shared MCP setup and tool-call logging does not modify a successful tool result.
C:In a build verification pipeline, separating credentials from versioned configuration limits accidental disclosure, but summaries can discard fields that subsequent steps require; therefore the separate requirement that tool-call logging does not modify a successful tool result would remain unsatisfied.
D:In a build verification pipeline, separating instrumentation from mutation reduces the risk of corrupting evidence, 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.
Question 316
Before expanding a technical due-diligence report generator, the owner must demonstrate that independent research branches can finish without waiting on one another, while also demonstrating that a tool receives a typed and bounded request. Which design provides both controls?
- chain every research agent in a fixed serial pipeline; and define required properties and types in the input schema and validate arguments at the execution boundary
- chain every research agent in a fixed serial pipeline; and accept one unstructured free-text argument for every operation
- dispatch the independent branches concurrently through the coordinator; and accept one unstructured free-text argument for every operation
- dispatch the independent branches concurrently through the coordinator; and define required properties and types in the input schema and validate arguments at the execution boundary
Explanation
Correct Answer
D:In a technical due-diligence report generator, parallel delegation reduces latency when individual investigations do not consume each other's outputs; alongside this, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, satisfying the distinct requirements that independent research branches can finish without waiting on one another and that a tool receives a typed and bounded request.
Incorrect Answers
A:In a technical due-diligence report generator, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, but unnecessary sequential handoffs increase latency for independent subtasks; therefore the separate requirement that independent research branches can finish without waiting on one another would remain unsatisfied.
B:In a technical due-diligence report generator, unnecessary sequential handoffs increase latency for independent subtasks and unconstrained prose leaves parsing and validation errors to ad hoc handler inference; the design would fail both conditions: independent research branches can finish without waiting on one another and a tool receives a typed and bounded request.
C:In a technical due-diligence report generator, parallel delegation reduces latency when individual investigations do not consume each other's outputs, 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 317
Before expanding a branch protection review bot, the owner must demonstrate that the assistant locates files containing a particular symbol or string, while also demonstrating that a team shares a repository-specific MCP server configuration. Which design provides both controls?
- scan only filenames with Glob; and configure each contributor's personal MCP registry manually
- use Grep to search file contents; and commit a reviewed project .mcp.json without credentials
- use Grep to search file contents; and configure each contributor's personal MCP registry manually
- scan only filenames with Glob; and commit a reviewed project .mcp.json without credentials
Explanation
Correct Answer
B:In a branch protection review bot, text search locates occurrences efficiently before focused reading; alongside this, project-scoped configuration can be distributed with the repository while keeping secrets external, satisfying the distinct requirements that the assistant locates files containing a particular symbol or string and that a team shares a repository-specific MCP server configuration.
Incorrect Answers
A:In a branch protection review bot, path matching does not inspect symbol occurrences inside files and local personal settings do not create a reproducible team project setup; the design would fail both conditions: the assistant locates files containing a particular symbol or string and a team shares a repository-specific MCP server configuration.
C:In a branch protection review bot, text search locates occurrences efficiently before focused reading, but local personal settings do not create a reproducible team project setup; therefore the separate requirement that a team shares a repository-specific MCP server configuration would remain unsatisfied.
D:In a branch protection review bot, project-scoped configuration can be distributed with the repository while keeping secrets external, but path matching does not inspect symbol occurrences inside files; therefore the separate requirement that the assistant locates files containing a particular symbol or string would remain unsatisfied.
Question 318
An audit of a CLI application maintenance task asks how to make sure that an exploratory branch can be compared with a baseline later. Which implementation should be selected?
- resume the stored session by its identifier
- preserve both branch identifiers and outcome summaries
- persist authoritative task facts and artifact IDs outside ephemeral conversation text
- overwrite the baseline notes with the trial branch's results
- recheck permissions and current resource state before new side effects
Explanation
Correct Answer
B:For a CLI application maintenance task, tracking lineage makes result comparison possible without confusing which session produced an artifact; this directly establishes that an exploratory branch can be compared with a baseline later instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although session resumption retains the recorded conversation and avoids rebuilding the entire task from scratch, that only supports the distinct goal that a developer returns to an interrupted session with prior reasoning, not the requirement that an exploratory branch can be compared with a baseline later in a CLI application maintenance task.
C:Although external durable state can be reloaded and checked when the session window changes, that only supports the distinct goal that important workflow state survives context compression or process restarts, not the requirement that an exploratory branch can be compared with a baseline later in a CLI application maintenance task.
D:In a CLI application maintenance task, losing provenance prevents trustworthy evaluation; as a result, the stated requirement that an exploratory branch can be compared with a baseline later would still not be met.
E:Although conversation continuity is not a replacement for live access control or fresh tool state, that only supports the distinct goal that resuming a session does not bypass present-day authorization, not the requirement that an exploratory branch can be compared with a baseline later in a CLI application maintenance task.
Question 319
While preparing a multi-source competitor research system for deployment, engineers must ensure that resuming a session does not bypass present-day authorization; they must also ensure that the model can distinguish two similar business tools. Which combination best satisfies those requirements?
- treat old approval messages as unlimited authorization for later writes; and give each tool a specific purpose and exclusion examples in its description
- treat old approval messages as unlimited authorization for later writes; and give both tools vague names with identical generic descriptions
- recheck permissions and current resource state before new side effects; and give each tool a specific purpose and exclusion examples in its description
- recheck permissions and current resource state before new side effects; and give both tools vague names with identical generic descriptions
Explanation
Correct Answer
C:In a multi-source competitor research system, conversation continuity is not a replacement for live access control or fresh tool state; alongside this, discriminative descriptions reduce wrong routing when operations sound alike, satisfying the distinct requirements that resuming a session does not bypass present-day authorization and that the model can distinguish two similar business tools.
Incorrect Answers
A:In a multi-source competitor research system, discriminative descriptions reduce wrong routing when operations sound alike, but permissions and operational context can change between sessions; therefore the separate requirement that resuming a session does not bypass present-day authorization would remain unsatisfied.
B:In a multi-source competitor research system, permissions and operational context can change between sessions and a model cannot reliably select on boundaries that the interface never explains; the design would fail both conditions: resuming a session does not bypass present-day authorization and the model can distinguish two similar business tools.
D:In a multi-source competitor research system, conversation continuity is not a replacement for live access control or fresh tool state, but a model cannot reliably select on boundaries that the interface never explains; therefore the separate requirement that the model can distinguish two similar business tools would remain unsatisfied.
Question 320
An incident postmortem for a shipping-exception helpdesk requires controls so that an out-of-policy request is escalated consistently and that a classification uses a limited approved category set. Which paired remedy covers both failure modes?
- escalate only when the customer's sentiment is strongly negative; and define precise output labels and mapping rules
- use an explicit exception trigger and designated human review queue; and allow a free-form category for each case
- use an explicit exception trigger and designated human review queue; and define precise output labels and mapping rules
- escalate only when the customer's sentiment is strongly negative; and allow a free-form category for each case
- implement only use an explicit exception trigger and designated human review queue; make no corresponding change for the second requirement
Explanation
Correct Answer
C:In a shipping-exception helpdesk, policy-driven routing is predictable across changes in user tone; alongside this, controlled categories reduce schema drift and make downstream analytics comparable, satisfying the distinct requirements that an out-of-policy request is escalated consistently and that a classification uses a limited approved category set.
Incorrect Answers
A:In a shipping-exception helpdesk, controlled categories reduce schema drift and make downstream analytics comparable, but calmly phrased exceptions still exceed the agent's authority; therefore the separate requirement that an out-of-policy request is escalated consistently would remain unsatisfied.
B:In a shipping-exception helpdesk, policy-driven routing is predictable across changes in user tone, but unbounded labels fragment the intended taxonomy; therefore the separate requirement that a classification uses a limited approved category set would remain unsatisfied.
D:In a shipping-exception helpdesk, calmly phrased exceptions still exceed the agent's authority and unbounded labels fragment the intended taxonomy; the design would fail both conditions: an out-of-policy request is escalated consistently and a classification uses a limited approved category set.
E:In a shipping-exception helpdesk, policy-driven routing is predictable across changes in user tone, but the independent mechanism for the other criterion is absent: controlled categories reduce schema drift and make downstream analytics comparable; as written, the design does not ensure that a classification uses a limited approved category set.