Question 540
A readiness review for a typed API generator project requires that test-specific naming conventions run only when touching test files; that an existing file receives a precise localized replacement; and that secrets are not embedded in a shared MCP setup. Which THREE actions directly implement those distinct requirements? Choose THREE.
- place long-lived access tokens directly in .mcp.json
- use Edit for an exact targeted change
- use a test-file glob in the rules frontmatter
- apply the same test naming rule to every source file
- overwrite the whole file with a newly generated copy
- inject credentials through approved environment or secret-management mechanisms
Explanation
Correct Answers
B:For a typed API generator project, surgical edits preserve unrelated lines and provide reviewable diffs, which directly establishes that an existing file receives a precise localized replacement; the separate requirement that secrets are not embedded in a shared MCP setup is handled by a different action.
C:For a typed API generator project, glob matching limits enforcement guidance to the intended file families, which directly establishes that test-specific naming conventions run only when touching test files; the separate requirement that an existing file receives a precise localized replacement is handled by a different action.
F:For a typed API generator project, separating credentials from versioned configuration limits accidental disclosure, which directly establishes that secrets are not embedded in a shared MCP setup; the separate requirement that test-specific naming conventions run only when touching test files is handled by a different action.
Incorrect Answers
A:For a typed API generator project, repository history can expose tokens to everyone with code access, so this option cannot establish that secrets are not embedded in a shared MCP setup; correctly addressing test-specific naming conventions run only when touching test files elsewhere does not repair that deficiency.
D:For a typed API generator project, production files and configuration do not share the test naming context, so this option cannot establish that test-specific naming conventions run only when touching test files; correctly addressing an existing file receives a precise localized replacement elsewhere does not repair that deficiency.
E:For a typed API generator project, full replacement risks losing unrelated code and formatting, so this option cannot establish that an existing file receives a precise localized replacement; correctly addressing secrets are not embedded in a shared MCP setup elsewhere does not repair that deficiency.
Question 541
An audit of a returns-policy assistant identifies two unmet requirements: repeated delivery of one action request cannot create duplicate writes and an ordinary in-policy question is not escalated needlessly. Select TWO actions that remedy those particular deficiencies.
- send every low-risk question to a human as a default
- blindly resubmit the same write after every timeout
- use an idempotency key and confirm the prior commit before retrying
- reserve human handoff for specified triggers and let normal cases proceed
Explanation
Correct Answers
C:For a returns-policy assistant, side-effecting operations need deduplication against timeouts and repeated messages, which directly establishes that repeated delivery of one action request cannot create duplicate writes; the separate requirement that an ordinary in-policy question is not escalated needlessly is handled by a different action.
D:For a returns-policy assistant, well-defined boundaries maintain autonomy without bypassing risky decisions, which directly establishes that an ordinary in-policy question is not escalated needlessly; the separate requirement that repeated delivery of one action request cannot create duplicate writes is handled by a different action.
Incorrect Answers
A:For a returns-policy assistant, blanket escalation defeats the purpose of routine assistance, so this option cannot establish that an ordinary in-policy question is not escalated needlessly; correctly addressing repeated delivery of one action request cannot create duplicate writes elsewhere does not repair that deficiency.
B:For a returns-policy assistant, the first attempt might have committed despite a missing acknowledgment, so this option cannot establish that repeated delivery of one action request cannot create duplicate writes; correctly addressing an ordinary in-policy question is not escalated needlessly elsewhere does not repair that deficiency.
Question 542
Production readiness for a merge-request policy gate depends on ensuring that a CI job invokes Claude without a terminal conversation and that ambiguous requirements are resolved before a destructive migration. Select the most appropriate combined approach.
- run Claude Code in non-interactive print mode with -p; and make assumptions and migrate production files immediately
- run Claude Code in non-interactive print mode with -p; and clarify scope and acceptance criteria while planning
- launch an interactive Claude terminal in an unattended runner; and make assumptions and migrate production files immediately
- launch an interactive Claude terminal in an unattended runner; and clarify scope and acceptance criteria while planning
- implement only run Claude Code in non-interactive print mode with -p; make no corresponding change for the second requirement
Explanation
Correct Answer
B:In a merge-request policy gate, headless invocation permits scripted automation and exits after the requested task; alongside this, a reviewed plan should resolve unknown targets and rollback expectations before writes, satisfying the distinct requirements that a CI job invokes Claude without a terminal conversation and that ambiguous requirements are resolved before a destructive migration.
Incorrect Answers
A:In a merge-request policy gate, headless invocation permits scripted automation and exits after the requested task, but guessed intent can create costly irreversible changes; therefore the separate requirement that ambiguous requirements are resolved before a destructive migration would remain unsatisfied.
C:In a merge-request policy gate, an interactive session can block automation waiting for a person and guessed intent can create costly irreversible changes; the design would fail both conditions: a CI job invokes Claude without a terminal conversation and ambiguous requirements are resolved before a destructive migration.
D:In a merge-request policy gate, a reviewed plan should resolve unknown targets and rollback expectations before writes, but an interactive session can block automation waiting for a person; therefore the separate requirement that a CI job invokes Claude without a terminal conversation would remain unsatisfied.
E:In a merge-request policy gate, headless invocation permits scripted automation and exits after the requested task, but the independent mechanism for the other criterion is absent: a reviewed plan should resolve unknown targets and rollback expectations before writes; as written, the design does not ensure that ambiguous requirements are resolved before a destructive migration.
Question 543
Production readiness for a financial statement data extractor depends on ensuring that tool responses are associated with the exact invocations that produced them and that a missing MCP capability is diagnosed before changing prompts. Select the most appropriate combined approach.
- return tool_result blocks using the original tool_use_id values; and increase the system prompt length to compensate for disconnected tools
- return tool_result blocks using the original tool_use_id values; and verify server connection, transport, and exposed tool availability
- return tool results with newly invented identifiers; and verify server connection, transport, and exposed tool availability
- return tool results with newly invented identifiers; and increase the system prompt length to compensate for disconnected tools
Explanation
Correct Answer
B:In a financial statement data extractor, correlation identifiers bind asynchronous or parallel results to the right requests; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that tool responses are associated with the exact invocations that produced them and that a missing MCP capability is diagnosed before changing prompts.
Incorrect Answers
A:In a financial statement data extractor, correlation identifiers bind asynchronous or parallel results to the right requests, 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 financial statement data extractor, tool discovery depends on a live configured integration, not just the prompt wording, but the model cannot reliably associate a result with an outstanding call; therefore the separate requirement that tool responses are associated with the exact invocations that produced them would remain unsatisfied.
D:In a financial statement data extractor, the model cannot reliably associate a result with an outstanding call and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: tool responses are associated with the exact invocations that produced them and a missing MCP capability is diagnosed before changing prompts.
Question 544
When designing an order-cancellation service, the requirement is not satisfied unless an ordinary in-policy question is not escalated needlessly and a risk prompt handles missing supporting evidence honestly. Which implementation addresses the two independent conditions?
- reserve human handoff for specified triggers and let normal cases proceed; and require a definitive yes-or-no answer for every incomplete record
- reserve human handoff for specified triggers and let normal cases proceed; and instruct the model to return unknown or needs-review when evidence is absent
- send every low-risk question to a human as a default; and require a definitive yes-or-no answer for every incomplete record
- send every low-risk question to a human as a default; and instruct the model to return unknown or needs-review when evidence is absent
Explanation
Correct Answer
B:In an order-cancellation service, well-defined boundaries maintain autonomy without bypassing risky decisions; alongside this, a defined abstention path avoids forced confident judgments without facts, satisfying the distinct requirements that an ordinary in-policy question is not escalated needlessly and that a risk prompt handles missing supporting evidence honestly.
Incorrect Answers
A:In an order-cancellation service, well-defined boundaries maintain autonomy without bypassing risky decisions, but forced binaries hide uncertainty as false certainty; therefore the separate requirement that a risk prompt handles missing supporting evidence honestly would remain unsatisfied.
C:In an order-cancellation service, blanket escalation defeats the purpose of routine assistance and forced binaries hide uncertainty as false certainty; the design would fail both conditions: an ordinary in-policy question is not escalated needlessly and a risk prompt handles missing supporting evidence honestly.
D:In an order-cancellation service, a defined abstention path avoids forced confident judgments without facts, but blanket escalation defeats the purpose of routine assistance; therefore the separate requirement that an ordinary in-policy question is not escalated needlessly would remain unsatisfied.
Question 545
When designing a subscription support service, the requirement is not satisfied unless a payment-changing action obtains explicit user authorization and an extractor always returns the identifiers required by downstream code. Which implementation addresses the two independent conditions?
- treat a request for information as permission to mutate the account; and treat every identifier as an optional free-form note
- confirm the intended action and scope before invoking the write; and treat every identifier as an optional free-form note
- confirm the intended action and scope before invoking the write; and declare mandatory schema fields in the required list
- treat a request for information as permission to mutate the account; and declare mandatory schema fields in the required list
Explanation
Correct Answer
C:In a subscription support service, consent is specific to the side effect and cannot be inferred from a general inquiry; alongside this, required properties prevent accidental omission of key attributes, satisfying the distinct requirements that a payment-changing action obtains explicit user authorization and that an extractor always returns the identifiers required by downstream code.
Incorrect Answers
A:In a subscription support service, asking a question does not approve a financial change and the consumer cannot reliably rely on a field that may be omitted; the design would fail both conditions: a payment-changing action obtains explicit user authorization and an extractor always returns the identifiers required by downstream code.
B:In a subscription support service, consent is specific to the side effect and cannot be inferred from a general inquiry, but the consumer cannot reliably rely on a field that may be omitted; therefore the separate requirement that an extractor always returns the identifiers required by downstream code would remain unsatisfied.
D:In a subscription support service, required properties prevent accidental omission of key attributes, but asking a question does not approve a financial change; therefore the separate requirement that a payment-changing action obtains explicit user authorization would remain unsatisfied.
Question 546
During review of a billing-dispute support agent, an unmet criterion states that an order adjustment uses the current order record. Which measure resolves this specific gap?
- issue the update using details inferred only from conversation
- require the order lookup result before calculating or applying a change
- send a structured state packet with completed checks and unresolved decisions
- enforce a prerequisite gate in application logic before the write tool
Explanation
Correct Answer
B:For a billing-dispute support agent, the dependent operation needs authoritative state and must not guess from the customer's description; this directly establishes that an order adjustment uses the current order record instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a billing-dispute support agent, unverified user text can reference the wrong order or outdated state; as a result, the stated requirement that an order adjustment uses the current order record would still not be met.
C:Although a typed transition preserves obligations and facts between workflow stages, that only supports the distinct goal that a specialist handoff retains its prerequisites and evidence, not the requirement that an order adjustment uses the current order record in a billing-dispute support agent.
D:Although deterministic preconditions protect an irreversible operation even if the model proposes it early, that only supports the distinct goal that refund execution is blocked until customer identity is verified, not the requirement that an order adjustment uses the current order record in a billing-dispute support agent.
Question 547
A team operating a multi-source policy brief service wants to establish two separate behaviors: dependent analysis begins only when source retrieval is complete; in addition, a forced tool call still honors business authorization. Which plan implements both?
- run retrieval before analysis and pass its validated artifacts; and treat a forced tool choice as equivalent to user approval
- run retrieval before analysis and pass its validated artifacts; and combine tool_choice with server-side policy checks
- start the analysis and retrieval agents together without shared results; and combine tool_choice with server-side policy checks
- start the analysis and retrieval agents together without shared results; and treat a forced tool choice as equivalent to user approval
Explanation
Correct Answer
B:In a multi-source policy brief service, a downstream agent needs actual upstream findings rather than an assumed future result; alongside this, selection controls when a tool is proposed but does not grant permission to execute, satisfying the distinct requirements that dependent analysis begins only when source retrieval is complete and that a forced tool call still honors business authorization.
Incorrect Answers
A:In a multi-source policy brief service, a downstream agent needs actual upstream findings rather than an assumed future result, but tool selection and authorization are different controls; therefore the separate requirement that a forced tool call still honors business authorization would remain unsatisfied.
C:In a multi-source policy brief service, selection controls when a tool is proposed but does not grant permission to execute, but the analysis branch cannot evaluate evidence it has not received; therefore the separate requirement that dependent analysis begins only when source retrieval is complete would remain unsatisfied.
D:In a multi-source policy brief service, the analysis branch cannot evaluate evidence it has not received and tool selection and authorization are different controls; the design would fail both conditions: dependent analysis begins only when source retrieval is complete and a forced tool call still honors business authorization.
Question 548
In an insurance document extraction agent, the immediate design requirement is that confidence scores reflect available evidence and uncertainty. Which change most directly establishes that behavior?
- put uncertain cases in an explicit review queue with priority and context
- set confidence to high whenever the explanation is detailed
- route high-impact or low-evidence results to an authorized reviewer
- calibrate confidence against known outcomes and source support
Explanation
Correct Answer
D:For an insurance document extraction agent, observed error rates and evidence quality are better than a fluent self-rating; this directly establishes that confidence scores reflect available evidence and uncertainty instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although triage preserves unattended processing for low-risk cases while catching exceptions, that only supports the distinct goal that an ambiguous item is separated from routine automation, not the requirement that confidence scores reflect available evidence and uncertainty in an insurance document extraction agent.
B:In an insurance document extraction agent, verbal detail is not a validated reliability estimate; as a result, the stated requirement that confidence scores reflect available evidence and uncertainty would still not be met.
C:Although human approval supplies accountability where a mistaken model result has material cost, that only supports the distinct goal that a consequential claim receives independent human sign-off, not the requirement that confidence scores reflect available evidence and uncertainty in an insurance document extraction agent.
Question 549
An audit of a merge-request policy gate asks how to make sure that a coding assistant's output passes explicit acceptance checks. Which implementation should be selected?
- run the specified tests and compare results against acceptance criteria
- accept an implementation because the agent describes it as complete
- turn the feedback into a concrete test or change request
- iterate with focused diffs rather than wholesale regeneration
Explanation
Correct Answer
A:For a merge-request policy gate, objective checks support a pass decision better than self-reported confidence; this directly establishes that a coding assistant's output passes explicit acceptance checks instead of relying on an unrelated workflow control.
Incorrect Answers
B:In a merge-request policy gate, model assertions cannot replace build and behavior evidence; as a result, the stated requirement that a coding assistant's output passes explicit acceptance checks would still not be met.
C:Although actionable feedback narrows the next edit and makes improvement measurable, that only supports the distinct goal that reviewer feedback points to a specific missed requirement, not the requirement that a coding assistant's output passes explicit acceptance checks in a merge-request policy gate.
D:Although narrow changes are easier to test and evaluate against explicit requirements, that only supports the distinct goal that the review produces a small, auditable patch, not the requirement that a coding assistant's output passes explicit acceptance checks in a merge-request policy gate.
Question 550
An incident postmortem for an expense receipt capture system requires controls so that tool output is normalized before it enters the agent context and that a broad tool catalog does not overwhelm a small task. Which paired remedy covers both failure modes?
- preprocess only the original user message; and load all available MCP tools into every specialist turn
- use a PostToolUse processing hook to standardize the returned data; and supply only context-relevant tools for the current agent
- use a PostToolUse processing hook to standardize the returned data; and load all available MCP tools into every specialist turn
- preprocess only the original user message; and supply only context-relevant tools for the current agent
Explanation
Correct Answer
B:In an expense receipt capture system, post-execution interception can clean result fields and attach useful status without changing the model's tool selection; alongside this, reducing irrelevant tool definitions improves selection and saves context, satisfying the distinct requirements that tool output is normalized before it enters the agent context and that a broad tool catalog does not overwhelm a small task.
Incorrect Answers
A:In an expense receipt capture system, input normalization does not correct inconsistent tool outputs and tool bloat makes the available actions harder to discriminate; the design would fail both conditions: tool output is normalized before it enters the agent context and a broad tool catalog does not overwhelm a small task.
C:In an expense receipt capture system, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, 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.
D:In an expense receipt capture system, reducing irrelevant tool definitions improves selection and saves context, 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.