Question 740
For a warranty claims assistant, a reviewer identifies two independent obligations: the system distinguishes acceptable and unacceptable edge cases and tool responses are associated with the exact invocations that produced them. Which proposal should be approved?
- specify inclusion criteria and explicit exclusion conditions; and return tool_result blocks using the original tool_use_id values
- provide only a broad topic label as the classification rule; and return tool_result blocks using the original tool_use_id values
- provide only a broad topic label as the classification rule; and return tool results with newly invented identifiers
- specify inclusion criteria and explicit exclusion conditions; and return tool results with newly invented identifiers
Explanation
Correct Answer
A:In a warranty claims assistant, negative boundaries teach the model when a near-match must not trigger; alongside this, correlation identifiers bind asynchronous or parallel results to the right requests, satisfying the distinct requirements that the system distinguishes acceptable and unacceptable edge cases and that tool responses are associated with the exact invocations that produced them.
Incorrect Answers
B:In a warranty claims assistant, correlation identifiers bind asynchronous or parallel results to the right requests, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
C:In a warranty claims assistant, generic labels leave ambiguous boundary cases undefined and the model cannot reliably associate a result with an outstanding call; the design would fail both conditions: the system distinguishes acceptable and unacceptable edge cases and tool responses are associated with the exact invocations that produced them.
D:In a warranty claims assistant, negative boundaries teach the model when a near-match must not trigger, 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.
Question 741
An architecture review of a legacy service decomposition finds two missing guarantees: context reduction does not erase unresolved obligations; a source change is validated against the right dependency chain. What two-part change closes both gaps?
- assume the agent will recall every open action from memory; and review only the edited line with no caller context
- track pending approvals and required next steps in durable task state; and trace imports and call sites from the touched module outward
- assume the agent will recall every open action from memory; and trace imports and call sites from the touched module outward
- track pending approvals and required next steps in durable task state; and review only the edited line with no caller context
Explanation
Correct Answer
B:In a legacy service decomposition, persisted obligations survive when natural-language history is shortened; alongside this, dependency-focused exploration spots affected behavior without indiscriminate reading, satisfying the distinct requirements that context reduction does not erase unresolved obligations and that a source change is validated against the right dependency chain.
Incorrect Answers
A:In a legacy service decomposition, window truncation can drop an outstanding approval or escalation and local correctness may miss consumers that rely on the old behavior; the design would fail both conditions: context reduction does not erase unresolved obligations and a source change is validated against the right dependency chain.
C:In a legacy service decomposition, dependency-focused exploration spots affected behavior without indiscriminate reading, but window truncation can drop an outstanding approval or escalation; therefore the separate requirement that context reduction does not erase unresolved obligations would remain unsatisfied.
D:In a legacy service decomposition, persisted obligations survive when natural-language history is shortened, but local correctness may miss consumers that rely on the old behavior; therefore the separate requirement that a source change is validated against the right dependency chain would remain unsatisfied.
Question 742
A deployment-readiness bot is allowed to inspect only its target worktree, and every finding must use one of the team’s approved classification labels. Which design combines least-privilege CI execution with controlled categorization?
- implement only define precise output labels and mapping rules; make no corresponding change for the first requirement
- give the bot administrator credentials to avoid permission failures; and allow a free-form category for each case
- scope runner credentials, worktree access, and allowed tools to its task; and allow a free-form category for each case
- give the bot administrator credentials to avoid permission failures; and define precise output labels and mapping rules
- scope runner credentials, worktree access, and allowed tools to its task; and define precise output labels and mapping rules
Explanation
Correct Answer
E:In a deployment-readiness verification process, CI identity and tool permissions control real write capabilities independent of model instructions; alongside this, controlled categories reduce schema drift and make downstream analytics comparable, satisfying the distinct requirements that a pull-request bot runs with minimum necessary authority and that a classification uses a limited approved category set.
Incorrect Answers
A:In a deployment-readiness verification process, controlled categories reduce schema drift and make downstream analytics comparable, but the independent mechanism for the other criterion is absent: CI identity and tool permissions control real write capabilities independent of model instructions; as written, the design does not ensure that a pull-request bot runs with minimum necessary authority.
B:In a deployment-readiness verification process, broad credentials increase the blast radius of a compromised or mistaken job and unbounded labels fragment the intended taxonomy; the design would fail both conditions: a pull-request bot runs with minimum necessary authority and a classification uses a limited approved category set.
C:In a deployment-readiness verification process, CI identity and tool permissions control real write capabilities independent of model instructions, 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 deployment-readiness verification process, controlled categories reduce schema drift and make downstream analytics comparable, but broad credentials increase the blast radius of a compromised or mistaken job; therefore the separate requirement that a pull-request bot runs with minimum necessary authority would remain unsatisfied.
Question 743
While preparing a returns-and-billing assistant for deployment, engineers must ensure that partial data is not presented as a complete successful result; they must also ensure that important workflow state survives context compression or process restarts. Which combination best satisfies those requirements?
- silently omit records that failed to load; and depend on the model remembering a prior value forever
- return an explicit partial status with missing-item identifiers; and depend on the model remembering a prior value forever
- return an explicit partial status with missing-item identifiers; and persist authoritative task facts and artifact IDs outside ephemeral conversation text
- silently omit records that failed to load; and persist authoritative task facts and artifact IDs outside ephemeral conversation text
Explanation
Correct Answer
C:In a returns-and-billing assistant, failure metadata preserves the difference between a sparse valid response and incomplete execution; alongside this, external durable state can be reloaded and checked when the session window changes, satisfying the distinct requirements that partial data is not presented as a complete successful result and that important workflow state survives context compression or process restarts.
Incorrect Answers
A:In a returns-and-billing assistant, the coordinator could publish an inaccurate completeness claim and context limits and summarization can lose exact identifiers; the design would fail both conditions: partial data is not presented as a complete successful result and important workflow state survives context compression or process restarts.
B:In a returns-and-billing assistant, failure metadata preserves the difference between a sparse valid response and incomplete execution, but context limits and summarization can lose exact identifiers; therefore the separate requirement that important workflow state survives context compression or process restarts would remain unsatisfied.
D:In a returns-and-billing assistant, external durable state can be reloaded and checked when the session window changes, but the coordinator could publish an inaccurate completeness claim; therefore the separate requirement that partial data is not presented as a complete successful result would remain unsatisfied.
Question 744
Tests for a source code audit helper will pass only if the model can distinguish two similar business tools and if a delegated reviewer has no production write capability. Which proposed design directly satisfies both checks?
- give both tools vague names with identical generic descriptions; and give the reviewer every administrative tool and ask for restraint
- give each tool a specific purpose and exclusion examples in its description; and provide only the read-oriented tools required by that reviewer
- give both tools vague names with identical generic descriptions; and provide only the read-oriented tools required by that reviewer
- implement only give each tool a specific purpose and exclusion examples in its description; make no corresponding change for the second requirement
- give each tool a specific purpose and exclusion examples in its description; and give the reviewer every administrative tool and ask for restraint
Explanation
Correct Answer
B:In a source code audit helper, discriminative descriptions reduce wrong routing when operations sound alike; alongside this, agent-scoped tool exposure prevents a write path in a read-only role, satisfying the distinct requirements that the model can distinguish two similar business tools and that a delegated reviewer has no production write capability.
Incorrect Answers
A:In a source code audit helper, a model cannot reliably select on boundaries that the interface never explains and prompt restraint is weaker than withholding execution capability; the design would fail both conditions: the model can distinguish two similar business tools and a delegated reviewer has no production write capability.
C:In a source code audit helper, agent-scoped tool exposure prevents a write path in a read-only role, 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.
D:In a source code audit helper, discriminative descriptions reduce wrong routing when operations sound alike, but the independent mechanism for the other criterion is absent: agent-scoped tool exposure prevents a write path in a read-only role; as written, the design does not ensure that a delegated reviewer has no production write capability.
E:In a source code audit helper, discriminative descriptions reduce wrong routing when operations sound alike, but prompt restraint is weaker than withholding execution capability; therefore the separate requirement that a delegated reviewer has no production write capability would remain unsatisfied.
Question 745
During review of a supplier invoice extractor, an unmet criterion states that the team can diagnose which fields repeatedly fail extraction. Which measure resolves this specific gap?
- record validation failure codes and field paths per attempt
- retain the original source, response version, and retry feedback
- log only the final success-or-failure boolean
- feed field-level validation errors back in a bounded retry
Explanation
Correct Answer
A:For a supplier invoice extractor, granular observability reveals schema weaknesses and document patterns; this directly establishes that the team can diagnose which fields repeatedly fail extraction instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although traceable attempts allow auditors to distinguish correction from silent overwrite, that only supports the distinct goal that a corrected attempt preserves a record of prior validation findings, not the requirement that the team can diagnose which fields repeatedly fail extraction in a supplier invoice extractor.
C:In a supplier invoice extractor, an aggregate flag hides the source of extraction errors; as a result, the stated requirement that the team can diagnose which fields repeatedly fail extraction would still not be met.
D:Although targeted feedback identifies what the next attempt must correct, that only supports the distinct goal that a failed extraction is retried with specific corrective information, not the requirement that the team can diagnose which fields repeatedly fail extraction in a supplier invoice extractor.
Question 746
Production readiness for a contract clause extraction workflow depends on ensuring that a machine consumer receives a schema-compliant JSON object and that a failed extraction is retried with specific corrective information. Select the most appropriate combined approach.
- use supported structured JSON output with a declared schema; and feed field-level validation errors back in a bounded retry
- rely only on a sentence requesting JSON with no validation; and feed field-level validation errors back in a bounded retry
- rely only on a sentence requesting JSON with no validation; and repeat the same vague prompt after each failure
- use supported structured JSON output with a declared schema; and repeat the same vague prompt after each failure
Explanation
Correct Answer
A:In a contract clause extraction workflow, constrained output enforces parseable structure and required field types at generation; alongside this, targeted feedback identifies what the next attempt must correct, satisfying the distinct requirements that a machine consumer receives a schema-compliant JSON object and that a failed extraction is retried with specific corrective information.
Incorrect Answers
B:In a contract clause extraction workflow, targeted feedback identifies what the next attempt must correct, 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 contract clause extraction workflow, prompt-only formatting can still produce malformed or incomplete results and unchanged requests do not reveal which constraint was violated; the design would fail both conditions: a machine consumer receives a schema-compliant JSON object and a failed extraction is retried with specific corrective information.
D:In a contract clause extraction workflow, constrained output enforces parseable structure and required field types at generation, but unchanged requests do not reveal which constraint was violated; therefore the separate requirement that a failed extraction is retried with specific corrective information would remain unsatisfied.
Question 747
Tests for a pre-merge code inspection workflow will pass only if a developer has private preferences that should not change team guidance and if a small approved typo fix is completed without excessive planning. Which proposed design directly satisfies both checks?
- add private preferences to the shared repository CLAUDE.md; and use direct execution for the limited reviewed edit
- add private preferences to the shared repository CLAUDE.md; and launch a multi-stage planning effort for a single known line
- place personal instructions in the user-level CLAUDE.md; and use direct execution for the limited reviewed edit
- place personal instructions in the user-level CLAUDE.md; and launch a multi-stage planning effort for a single known line
Explanation
Correct Answer
C:In a pre-merge code inspection workflow, global personal guidance is available to that user's sessions without committing preferences to the project; alongside this, a bounded low-risk change does not require a long exploratory workflow, satisfying the distinct requirements that a developer has private preferences that should not change team guidance and that a small approved typo fix is completed without excessive planning.
Incorrect Answers
A:In a pre-merge code inspection workflow, a bounded low-risk change does not require a long exploratory workflow, but project instructions would impose one person's settings on the whole team; therefore the separate requirement that a developer has private preferences that should not change team guidance would remain unsatisfied.
B:In a pre-merge code inspection workflow, project instructions would impose one person's settings on the whole team and extra ceremony adds latency without materially lowering risk; the design would fail both conditions: a developer has private preferences that should not change team guidance and a small approved typo fix is completed without excessive planning.
D:In a pre-merge code inspection workflow, global personal guidance is available to that user's sessions without committing preferences to the project, but extra ceremony adds latency without materially lowering risk; therefore the separate requirement that a small approved typo fix is completed without excessive planning would remain unsatisfied.
Question 748
Tests for a structured report conversion service will pass only if each tool interface has a single clear operation boundary and if the assistant can use external service capabilities via MCP. Which proposed design directly satisfies both checks?
- use a single universal tool that infers read versus write from prose; and describe the external API in a prompt without connecting any tool
- separate read-only lookup from side-effecting update interfaces; and configure a compatible MCP server and expose its declared tools to the client
- separate read-only lookup from side-effecting update interfaces; and describe the external API in a prompt without connecting any tool
- use a single universal tool that infers read versus write from prose; and configure a compatible MCP server and expose its declared tools to the client
Explanation
Correct Answer
B:In a structured report conversion service, clear operation boundaries support least privilege and understandable approvals; alongside this, MCP bridges a client to provider-defined capabilities rather than inventing a Claude built-in, satisfying the distinct requirements that each tool interface has a single clear operation boundary and that the assistant can use external service capabilities via MCP.
Incorrect Answers
A:In a structured report conversion service, overloading hides effects and makes execution review harder and instructions cannot create an executable integration endpoint; the design would fail both conditions: each tool interface has a single clear operation boundary and the assistant can use external service capabilities via MCP.
C:In a structured report conversion service, clear operation boundaries support least privilege and understandable approvals, but instructions cannot create an executable integration endpoint; therefore the separate requirement that the assistant can use external service capabilities via MCP would remain unsatisfied.
D:In a structured report conversion service, MCP bridges a client to provider-defined capabilities rather than inventing a Claude built-in, but overloading hides effects and makes execution review harder; therefore the separate requirement that each tool interface has a single clear operation boundary would remain unsatisfied.
Question 749
An architecture review of an analyst research coordinator finds two missing guarantees: one specialist's crash does not discard other verified outputs; one agent's draft is reviewed independently for errors. What two-part change closes both gaps?
- isolate branch failures and preserve completed artifacts for coordination; and use a separate review pass with explicit criteria
- isolate branch failures and preserve completed artifacts for coordination; and ask the draft generator to declare its own work perfect
- restart every agent and erase prior results after a single crash; and use a separate review pass with explicit criteria
- restart every agent and erase prior results after a single crash; and ask the draft generator to declare its own work perfect
Explanation
Correct Answer
A:In an analyst research coordinator, fault containment avoids losing good work while a failed branch is repaired; alongside this, independent criticism exposes omissions that unstructured self-praise can miss, satisfying the distinct requirements that one specialist's crash does not discard other verified outputs and that one agent's draft is reviewed independently for errors.
Incorrect Answers
B:In an analyst research coordinator, fault containment avoids losing good work while a failed branch is repaired, but self-assessment without a second criterion-based pass is weak evidence; therefore the separate requirement that one agent's draft is reviewed independently for errors would remain unsatisfied.
C:In an analyst research coordinator, independent criticism exposes omissions that unstructured self-praise can miss, but unaffected branches would be redone and provenance could be lost; therefore the separate requirement that one specialist's crash does not discard other verified outputs would remain unsatisfied.
D:In an analyst research coordinator, unaffected branches would be redone and provenance could be lost and self-assessment without a second criterion-based pass is weak evidence; the design would fail both conditions: one specialist's crash does not discard other verified outputs and one agent's draft is reviewed independently for errors.
Question 750
In a technical review of a mobile client bug-fix task, the architect must address the following constraints together: every high-impact tool invocation produces an audit event; a missing MCP capability is diagnosed before changing prompts. Which change set is most defensible?
- record the tool name, permitted inputs, outcome, and task identifier in a hook; and increase the system prompt length to compensate for disconnected tools
- infer tool activity from the final natural-language answer; and verify server connection, transport, and exposed tool availability
- record the tool name, permitted inputs, outcome, and task identifier in a hook; and verify server connection, transport, and exposed tool availability
- infer tool activity from the final natural-language answer; and increase the system prompt length to compensate for disconnected tools
Explanation
Correct Answer
C:In a mobile client bug-fix task, runtime instrumentation observes actual proposed or completed tool activity; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that every high-impact tool invocation produces an audit event and that a missing MCP capability is diagnosed before changing prompts.
Incorrect Answers
A:In a mobile client bug-fix task, runtime instrumentation observes actual proposed or completed tool activity, 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.
B:In a mobile client bug-fix task, tool discovery depends on a live configured integration, not just the prompt wording, but a summary can omit failed calls or delegated actions; therefore the separate requirement that every high-impact tool invocation produces an audit event would remain unsatisfied.
D:In a mobile client bug-fix task, a summary can omit failed calls or delegated actions and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: every high-impact tool invocation produces an audit event and a missing MCP capability is diagnosed before changing prompts.