Question 430
An incident postmortem for a customer refund workflow requires controls so that an unresolved claim is qualified without inventing certainty and that a machine consumer receives a schema-compliant JSON object. Which paired remedy covers both failure modes?
- express the uncertainty and identify what verification is missing; and use supported structured JSON output with a declared schema
- state a firm conclusion because the report needs a complete ending; and rely only on a sentence requesting JSON with no validation
- express the uncertainty and identify what verification is missing; and rely only on a sentence requesting JSON with no validation
- state a firm conclusion because the report needs a complete ending; and use supported structured JSON output with a declared schema
Explanation
Correct Answer
A:In a customer refund workflow, calibrated language communicates a bounded evidence gap honestly; alongside this, constrained output enforces parseable structure and required field types at generation, satisfying the distinct requirements that an unresolved claim is qualified without inventing certainty and that a machine consumer receives a schema-compliant JSON object.
Incorrect Answers
B:In a customer refund workflow, a polished narrative cannot supply missing corroboration and prompt-only formatting can still produce malformed or incomplete results; the design would fail both conditions: an unresolved claim is qualified without inventing certainty and a machine consumer receives a schema-compliant JSON object.
C:In a customer refund workflow, calibrated language communicates a bounded evidence gap honestly, 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.
D:In a customer refund workflow, constrained output enforces parseable structure and required field types at generation, but a polished narrative cannot supply missing corroboration; therefore the separate requirement that an unresolved claim is qualified without inventing certainty would remain unsatisfied.
Question 431
In a technical review of an after-sales issue resolver, the architect must address the following constraints together: a support case missing an essential fact is not silently guessed; a handoff retains only action-relevant context. Which change set is most defensible?
- ask a focused clarifying question for the missing requirement; and send every previous chat turn to each new worker
- invent a plausible value and continue automatically; and pass a compact structured record of facts, decisions, pending tasks, and sources
- ask a focused clarifying question for the missing requirement; and pass a compact structured record of facts, decisions, pending tasks, and sources
- invent a plausible value and continue automatically; and send every previous chat turn to each new worker
Explanation
Correct Answer
C:In an after-sales issue resolver, targeted clarification supplies the decision input before selecting an irreversible action; alongside this, focused handoffs reduce context size while protecting continuity-critical details, satisfying the distinct requirements that a support case missing an essential fact is not silently guessed and that a handoff retains only action-relevant context.
Incorrect Answers
A:In an after-sales issue resolver, targeted clarification supplies the decision input before selecting an irreversible action, but large histories include irrelevant or outdated information; therefore the separate requirement that a handoff retains only action-relevant context would remain unsatisfied.
B:In an after-sales issue resolver, focused handoffs reduce context size while protecting continuity-critical details, but fabricated facts can cause the wrong account or policy to be applied; therefore the separate requirement that a support case missing an essential fact is not silently guessed would remain unsatisfied.
D:In an after-sales issue resolver, fabricated facts can cause the wrong account or policy to be applied and large histories include irrelevant or outdated information; the design would fail both conditions: a support case missing an essential fact is not silently guessed and a handoff retains only action-relevant context.
Question 432
During review of a nightly code quality job, an unmet criterion states that tool output is normalized before it enters the agent context. Which measure resolves this specific gap?
- use an observation-only hook for telemetry when rewriting is unnecessary
- use a PostToolUse processing hook to standardize the returned data
- preprocess only the original user message
- check resolved target paths in the pre-tool policy gate
Explanation
Correct Answer
B:For a nightly code quality job, post-execution interception can clean result fields and attach useful status without changing the model's tool selection; this directly establishes that tool output is normalized before it enters the agent context instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although separating instrumentation from mutation reduces the risk of corrupting evidence, that only supports the distinct goal that tool-call logging does not modify a successful tool result, not the requirement that tool output is normalized before it enters the agent context in a nightly code quality job.
C:In a nightly code quality job, input normalization does not correct inconsistent tool outputs; as a result, the stated requirement that tool output is normalized before it enters the agent context would still not be met.
D:Although a boundary check on the actual tool argument enforces the permitted filesystem scope, that only supports the distinct goal that file writes are blocked outside an approved workspace, not the requirement that tool output is normalized before it enters the agent context in a nightly code quality job.
Question 433
An architecture review of a procurement research assistant finds two missing guarantees: the system distinguishes acceptable and unacceptable edge cases; a formatter handles diverse legitimate examples consistently. What two-part change closes both gaps?
- provide only a broad topic label as the classification rule; and give a small set of representative input-output demonstrations
- specify inclusion criteria and explicit exclusion conditions; and supply only a bare instruction to keep formatting consistent
- specify inclusion criteria and explicit exclusion conditions; and give a small set of representative input-output demonstrations
- provide only a broad topic label as the classification rule; and supply only a bare instruction to keep formatting consistent
Explanation
Correct Answer
C:In a procurement research assistant, negative boundaries teach the model when a near-match must not trigger; alongside this, few-shot examples show the intended mapping more concretely than broad style adjectives, satisfying the distinct requirements that the system distinguishes acceptable and unacceptable edge cases and that a formatter handles diverse legitimate examples consistently.
Incorrect Answers
A:In a procurement research assistant, few-shot examples show the intended mapping more concretely than broad style adjectives, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
B:In a procurement research assistant, negative boundaries teach the model when a near-match must not trigger, but abstract instructions leave many output choices open; therefore the separate requirement that a formatter handles diverse legitimate examples consistently would remain unsatisfied.
D:In a procurement research assistant, generic labels leave ambiguous boundary cases undefined and abstract instructions leave many output choices open; the design would fail both conditions: the system distinguishes acceptable and unacceptable edge cases and a formatter handles diverse legitimate examples consistently.
Question 434
For a multi-repository troubleshooting agent, a reviewer identifies two independent obligations: a tool result includes enough fields to support audit and follow-on actions and a team shares a repository-specific MCP server configuration. Which proposal should be approved?
- return structured identifiers, status, and provenance with the data; and configure each contributor's personal MCP registry manually
- return only a friendly summary with no source identifier; and configure each contributor's personal MCP registry manually
- return only a friendly summary with no source identifier; and commit a reviewed project .mcp.json without credentials
- return structured identifiers, status, and provenance with the data; and commit a reviewed project .mcp.json without credentials
Explanation
Correct Answer
D:In a multi-repository troubleshooting agent, machine-readable outputs let downstream stages validate exactly what was retrieved; alongside this, project-scoped configuration can be distributed with the repository while keeping secrets external, satisfying the distinct requirements that a tool result includes enough fields to support audit and follow-on actions and that a team shares a repository-specific MCP server configuration.
Incorrect Answers
A:In a multi-repository troubleshooting agent, machine-readable outputs let downstream stages validate exactly what was retrieved, 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.
B:In a multi-repository troubleshooting agent, a paraphrase hides the record needed for verification or follow-up and local personal settings do not create a reproducible team project setup; the design would fail both conditions: a tool result includes enough fields to support audit and follow-on actions and a team shares a repository-specific MCP server configuration.
C:In a multi-repository troubleshooting agent, project-scoped configuration can be distributed with the repository while keeping secrets external, but a paraphrase hides the record needed for verification or follow-up; therefore the separate requirement that a tool result includes enough fields to support audit and follow-on actions would remain unsatisfied.
Question 435
The release checklist for a source-grounded policy synthesis service explicitly checks that independent stages of a complex job run efficiently; it also checks that resuming a session does not bypass present-day authorization. What coordinated solution meets the checklist?
- split the job into an arbitrary fixed chain of agents; and treat old approval messages as unlimited authorization for later writes
- divide work along independent outputs and run those stages in parallel; and recheck permissions and current resource state before new side effects
- divide work along independent outputs and run those stages in parallel; and treat old approval messages as unlimited authorization for later writes
- split the job into an arbitrary fixed chain of agents; and recheck permissions and current resource state before new side effects
Explanation
Correct Answer
B:In a source-grounded policy synthesis service, dependency-aware decomposition avoids serial work when branches do not consume one another; alongside this, conversation continuity is not a replacement for live access control or fresh tool state, satisfying the distinct requirements that independent stages of a complex job run efficiently and that resuming a session does not bypass present-day authorization.
Incorrect Answers
A:In a source-grounded policy synthesis service, a rigid sequence creates waits even where no dependency exists and permissions and operational context can change between sessions; the design would fail both conditions: independent stages of a complex job run efficiently and resuming a session does not bypass present-day authorization.
C:In a source-grounded policy synthesis service, dependency-aware decomposition avoids serial work when branches do not consume one another, 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.
D:In a source-grounded policy synthesis service, conversation continuity is not a replacement for live access control or fresh tool state, but a rigid sequence creates waits even where no dependency exists; therefore the separate requirement that independent stages of a complex job run efficiently would remain unsatisfied.
Question 436
An architecture review of a monorepo testing overhaul finds two missing guarantees: a coding assistant's output passes explicit acceptance checks; a risky refactor is evaluated before any files change. What two-part change closes both gaps?
- accept an implementation because the agent describes it as complete; and let the agent immediately edit every matching file
- run the specified tests and compare results against acceptance criteria; and let the agent immediately edit every matching file
- run the specified tests and compare results against acceptance criteria; and use plan mode to inspect dependencies and propose steps before execution
- accept an implementation because the agent describes it as complete; and use plan mode to inspect dependencies and propose steps before execution
Explanation
Correct Answer
C:In a monorepo testing overhaul, objective checks support a pass decision better than self-reported confidence; alongside this, planning separates investigation and approval from code mutation, satisfying the distinct requirements that a coding assistant's output passes explicit acceptance checks and that a risky refactor is evaluated before any files change.
Incorrect Answers
A:In a monorepo testing overhaul, model assertions cannot replace build and behavior evidence and early writes can spread an unapproved assumption through the repository; the design would fail both conditions: a coding assistant's output passes explicit acceptance checks and a risky refactor is evaluated before any files change.
B:In a monorepo testing overhaul, objective checks support a pass decision better than self-reported confidence, 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 monorepo testing overhaul, planning separates investigation and approval from code mutation, but model assertions cannot replace build and behavior evidence; therefore the separate requirement that a coding assistant's output passes explicit acceptance checks would remain unsatisfied.
Question 437
While preparing a contract-analysis research network for deployment, engineers must ensure that tool-call logging does not modify a successful tool result; they must also ensure that a tool receives a typed and bounded request. Which combination best satisfies those requirements?
- use an observation-only hook for telemetry when rewriting is unnecessary; and define required properties and types in the input schema and validate arguments at the execution boundary
- rewrite every tool result as a free-form paraphrase; and define required properties and types in the input schema and validate arguments at the execution boundary
- rewrite every tool result as a free-form paraphrase; and accept one unstructured free-text argument for every operation
- use an observation-only hook for telemetry when rewriting is unnecessary; and accept one unstructured free-text argument for every operation
Explanation
Correct Answer
A:In a contract-analysis research network, separating instrumentation from mutation reduces the risk of corrupting evidence; alongside this, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, satisfying the distinct requirements that tool-call logging does not modify a successful tool result and that a tool receives a typed and bounded request.
Incorrect Answers
B:In a contract-analysis research network, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, 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.
C:In a contract-analysis research network, summaries can discard fields that subsequent steps require and unconstrained prose leaves parsing and validation errors to ad hoc handler inference; the design would fail both conditions: tool-call logging does not modify a successful tool result and a tool receives a typed and bounded request.
D:In a contract-analysis research network, separating instrumentation from mutation reduces the risk of corrupting evidence, 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 438
During review of a repository change-review job, an unmet criterion states that example selection stays relevant to the current workload. Which measure resolves this specific gap?
- use a compact sample covering common cases and one important edge case
- give a small set of representative input-output demonstrations
- include dozens of unrelated demonstrations from other domains
- audit examples against the current decision rubric before use
Explanation
Correct Answer
A:For a repository change-review job, high-signal examples guide the task without overloading context; this directly establishes that example selection stays relevant to the current workload instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although few-shot examples show the intended mapping more concretely than broad style adjectives, that only supports the distinct goal that a formatter handles diverse legitimate examples consistently, not the requirement that example selection stays relevant to the current workload in a repository change-review job.
C:In a repository change-review job, irrelevant examples dilute the pattern and consume tokens; as a result, the stated requirement that example selection stays relevant to the current workload would still not be met.
D:Although consistent labels reinforce the intended criteria rather than training ambiguity into the prompt, that only supports the distinct goal that few-shot material does not contain contradictory answer labels, not the requirement that example selection stays relevant to the current workload in a repository change-review job.
Question 439
An incident postmortem for a monorepo testing overhaul requires controls so that a repeatable code-review procedure is available as a named workflow and that regressions introduced during refinement are detected and fixed. Which paired remedy covers both failure modes?
- create a documented reusable skill in SKILL.md; and keep layering patches without checking the last stable behavior
- retype the entire procedure in every conversation; and restore or revise the problematic change and retest affected paths
- create a documented reusable skill in SKILL.md; and restore or revise the problematic change and retest affected paths
- retype the entire procedure in every conversation; and keep layering patches without checking the last stable behavior
Explanation
Correct Answer
C:In a monorepo testing overhaul, skills package instructions and supporting resources for invocation across similar tasks; alongside this, iteration includes detecting regressions and returning to a passing state, satisfying the distinct requirements that a repeatable code-review procedure is available as a named workflow and that regressions introduced during refinement are detected and fixed.
Incorrect Answers
A:In a monorepo testing overhaul, skills package instructions and supporting resources for invocation across similar tasks, but cumulative changes can bury the source of failure; therefore the separate requirement that regressions introduced during refinement are detected and fixed would remain unsatisfied.
B:In a monorepo testing overhaul, iteration includes detecting regressions and returning to a passing state, but manual repetition produces drift and loses shared revisions; therefore the separate requirement that a repeatable code-review procedure is available as a named workflow would remain unsatisfied.
D:In a monorepo testing overhaul, manual repetition produces drift and loses shared revisions and cumulative changes can bury the source of failure; the design would fail both conditions: a repeatable code-review procedure is available as a named workflow and regressions introduced during refinement are detected and fixed.
Question 440
In a continuous integration repair assistant, the design must ensure that a conclusion supported by model agreement is also tested against source evidence and that tool output is normalized before it enters the agent context. Choose TWO independent changes that directly meet these two requirements.
- use a PostToolUse processing hook to standardize the returned data
- preprocess only the original user message
- promote agreement alone to a guaranteed correctness signal
- require source and business-rule checks regardless of model agreement
Explanation
Correct Answers
A:For a continuous integration repair assistant, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, which directly establishes that tool output is normalized before it enters the agent context; the separate requirement that a conclusion supported by model agreement is also tested against source evidence is handled by a different action.
D:For a continuous integration repair assistant, correlated model errors can survive consensus without external verification, which directly establishes that a conclusion supported by model agreement is also tested against source evidence; the separate requirement that tool output is normalized before it enters the agent context is handled by a different action.
Incorrect Answers
B:For a continuous integration repair assistant, input normalization does not correct inconsistent tool outputs, so this option cannot establish that tool output is normalized before it enters the agent context; correctly addressing a conclusion supported by model agreement is also tested against source evidence elsewhere does not repair that deficiency.
C:For a continuous integration repair assistant, shared biases can produce identical wrong conclusions, so this option cannot establish that a conclusion supported by model agreement is also tested against source evidence; correctly addressing tool output is normalized before it enters the agent context elsewhere does not repair that deficiency.