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.
Question 751
The release checklist for a research PDF metadata pipeline explicitly checks that partial completion of a multi-step operation is handled safely; it also checks that a missing MCP capability is diagnosed before changing prompts. What coordinated solution meets the checklist?
- treat the first successful tool call as proof that the entire workflow succeeded; and verify server connection, transport, and exposed tool availability
- track individual stage outcomes and use explicit recovery or compensating actions; and verify server connection, transport, and exposed tool availability
- treat the first successful tool call as proof that the entire workflow succeeded; and increase the system prompt length to compensate for disconnected tools
- track individual stage outcomes and use explicit recovery or compensating actions; and increase the system prompt length to compensate for disconnected tools
Explanation
Correct Answer
B:In a research PDF metadata pipeline, an orchestrated workflow must not report overall success while a required step failed; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that partial completion of a multi-step operation is handled safely and that a missing MCP capability is diagnosed before changing prompts.
Incorrect Answers
A:In a research PDF metadata pipeline, tool discovery depends on a live configured integration, not just the prompt wording, but later actions can fail after an earlier side effect; therefore the separate requirement that partial completion of a multi-step operation is handled safely would remain unsatisfied.
C:In a research PDF metadata pipeline, later actions can fail after an earlier side effect and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: partial completion of a multi-step operation is handled safely and a missing MCP capability is diagnosed before changing prompts.
D:In a research PDF metadata pipeline, an orchestrated workflow must not report overall success while a required step failed, 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.
Question 752
For a document field validation service, a reviewer identifies two independent obligations: offline extraction cost is controlled without missing a service-level deadline and reviewer changes remain auditable. Which proposal should be approved?
- compare batch turnaround with the workload's time requirements; and overwrite an automated answer without preserving the reviewer decision
- select the lowest-cost async path even for strict real-time actions; and overwrite an automated answer without preserving the reviewer decision
- select the lowest-cost async path even for strict real-time actions; and log the reviewer identity, decision, justification, and artifact version
- compare batch turnaround with the workload's time requirements; and log the reviewer identity, decision, justification, and artifact version
Explanation
Correct Answer
D:In a document field validation service, asynchronous savings are appropriate only when delayed completion is acceptable; alongside this, a versioned approval trail supports diagnosis and later governance reviews, satisfying the distinct requirements that offline extraction cost is controlled without missing a service-level deadline and that reviewer changes remain auditable.
Incorrect Answers
A:In a document field validation service, asynchronous savings are appropriate only when delayed completion is acceptable, but the final state loses the reason it changed; therefore the separate requirement that reviewer changes remain auditable would remain unsatisfied.
B:In a document field validation service, meeting a live deadline can matter more than per-request savings and the final state loses the reason it changed; the design would fail both conditions: offline extraction cost is controlled without missing a service-level deadline and reviewer changes remain auditable.
C:In a document field validation service, a versioned approval trail supports diagnosis and later governance reviews, but meeting a live deadline can matter more than per-request savings; therefore the separate requirement that offline extraction cost is controlled without missing a service-level deadline would remain unsatisfied.
Question 753
In a technical review of a financial statement data extractor, the architect must address the following constraints together: a risk prompt handles missing supporting evidence honestly; a machine consumer receives a schema-compliant JSON object. Which change set is most defensible?
- instruct the model to return unknown or needs-review when evidence is absent; and rely only on a sentence requesting JSON with no validation
- require a definitive yes-or-no answer for every incomplete record; and use supported structured JSON output with a declared schema
- implement only instruct the model to return unknown or needs-review when evidence is absent; make no corresponding change for the second requirement
- instruct the model to return unknown or needs-review when evidence is absent; and use supported structured JSON output with a declared schema
- require a definitive yes-or-no answer for every incomplete record; and rely only on a sentence requesting JSON with no validation
Explanation
Correct Answer
D:In a financial statement data extractor, a defined abstention path avoids forced confident judgments without facts; alongside this, constrained output enforces parseable structure and required field types at generation, satisfying the distinct requirements that a risk prompt handles missing supporting evidence honestly and that a machine consumer receives a schema-compliant JSON object.
Incorrect Answers
A:In a financial statement data extractor, a defined abstention path avoids forced confident judgments without facts, 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.
B:In a financial statement data extractor, constrained output enforces parseable structure and required field types at generation, 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 a financial statement data extractor, a defined abstention path avoids forced confident judgments without facts, but the independent mechanism for the other criterion is absent: constrained output enforces parseable structure and required field types at generation; as written, the design does not ensure that a machine consumer receives a schema-compliant JSON object.
E:In a financial statement data extractor, forced binaries hide uncertainty as false certainty and prompt-only formatting can still produce malformed or incomplete results; the design would fail both conditions: a risk prompt handles missing supporting evidence honestly and a machine consumer receives a schema-compliant JSON object.
Question 754
An audit of a financial statement data extractor identifies two unmet requirements: an uncertain high-impact decision is routed for review instead of automatic execution and a failed retrieval agent does not masquerade as having found no matches. Select TWO actions that remedy those particular deficiencies.
- proceed whenever the assistant's prose sounds certain
- convert every retrieval failure into an empty list
- set a clear evidence or confidence boundary and require review below it
- return a typed failure status with its origin to the coordinator
Explanation
Correct Answers
C:For a financial statement data extractor, risk-weighted gates limit autonomous actions when support is inadequate, which directly establishes that an uncertain high-impact decision is routed for review instead of automatic execution; the separate requirement that a failed retrieval agent does not masquerade as having found no matches is handled by a different action.
D:For a financial statement data extractor, an operational error must remain distinguishable from a valid empty result, which directly establishes that a failed retrieval agent does not masquerade as having found no matches; the separate requirement that an uncertain high-impact decision is routed for review instead of automatic execution is handled by a different action.
Incorrect Answers
A:For a financial statement data extractor, fluent language is not a calibrated reliability measure, so this option cannot establish that an uncertain high-impact decision is routed for review instead of automatic execution; correctly addressing a failed retrieval agent does not masquerade as having found no matches elsewhere does not repair that deficiency.
B:For a financial statement data extractor, the final report could incorrectly claim no sources exist, so this option cannot establish that a failed retrieval agent does not masquerade as having found no matches; correctly addressing an uncertain high-impact decision is routed for review instead of automatic execution elsewhere does not repair that deficiency.
Question 755
The architect for a service dependency exploration tool needs to ensure that independent research branches can finish without waiting on one another. What should the team implement?
- dispatch the independent branches concurrently through the coordinator
- use a coordinator that delegates focused tasks and owns final synthesis
- chain every research agent in a fixed serial pipeline
- give subagents a common results contract including claim, evidence, and status
Explanation
Correct Answer
A:For a service dependency exploration tool, parallel delegation reduces latency when individual investigations do not consume each other's outputs; this directly establishes that independent research branches can finish without waiting on one another instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, that only supports the distinct goal that a large research job combines specialized findings into one answer, not the requirement that independent research branches can finish without waiting on one another in a service dependency exploration tool.
C:In a service dependency exploration tool, unnecessary sequential handoffs increase latency for independent subtasks; as a result, the stated requirement that independent research branches can finish without waiting on one another would still not be met.
D:Although a typed handoff lets the coordinator compare like fields and detect missing support, that only supports the distinct goal that specialists return comparable artifacts for aggregation, not the requirement that independent research branches can finish without waiting on one another in a service dependency exploration tool.
Question 756
The release checklist for a branch protection review bot explicitly checks that the team obtains a read-only survey of an unfamiliar module; it also checks that test-specific naming conventions run only when touching test files. What coordinated solution meets the checklist?
- investigate in plan-oriented or read-only mode first; and use a test-file glob in the rules frontmatter
- investigate in plan-oriented or read-only mode first; and apply the same test naming rule to every source file
- run write tools to discover how the module behaves; and apply the same test naming rule to every source file
- run write tools to discover how the module behaves; and use a test-file glob in the rules frontmatter
- implement only investigate in plan-oriented or read-only mode first; make no corresponding change for the second requirement
Explanation
Correct Answer
A:In a branch protection review bot, inspection can establish architecture and change scope without side effects; alongside this, glob matching limits enforcement guidance to the intended file families, satisfying the distinct requirements that the team obtains a read-only survey of an unfamiliar module and that test-specific naming conventions run only when touching test files.
Incorrect Answers
B:In a branch protection review bot, inspection can establish architecture and change scope without side effects, but production files and configuration do not share the test naming context; therefore the separate requirement that test-specific naming conventions run only when touching test files would remain unsatisfied.
C:In a branch protection review bot, mutation is unnecessary for gaining initial understanding and production files and configuration do not share the test naming context; the design would fail both conditions: the team obtains a read-only survey of an unfamiliar module and test-specific naming conventions run only when touching test files.
D:In a branch protection review bot, glob matching limits enforcement guidance to the intended file families, but mutation is unnecessary for gaining initial understanding; therefore the separate requirement that the team obtains a read-only survey of an unfamiliar module would remain unsatisfied.
E:In a branch protection review bot, inspection can establish architecture and change scope without side effects, but the independent mechanism for the other criterion is absent: glob matching limits enforcement guidance to the intended file families; as written, the design does not ensure that test-specific naming conventions run only when touching test files.
Question 757
In a service dependency exploration tool, the acceptance criteria require that the review produces a small, auditable patch and that near-overlapping retrieval tools are selected by actual boundary. Which paired implementation meets both?
- iterate with focused diffs rather than wholesale regeneration; and rely exclusively on short tool names for routing
- iterate with focused diffs rather than wholesale regeneration; and document examples and conditions where each tool must not be used
- replace every file in the component to ensure consistency; and document examples and conditions where each tool must not be used
- replace every file in the component to ensure consistency; and rely exclusively on short tool names for routing
Explanation
Correct Answer
B:In a service dependency exploration tool, narrow changes are easier to test and evaluate against explicit requirements; alongside this, contrastive guidance helps tool choice when resource names look similar, satisfying the distinct requirements that the review produces a small, auditable patch and that near-overlapping retrieval tools are selected by actual boundary.
Incorrect Answers
A:In a service dependency exploration tool, narrow changes are easier to test and evaluate against explicit requirements, but names alone may not capture the distinction in scope or authorization; therefore the separate requirement that near-overlapping retrieval tools are selected by actual boundary would remain unsatisfied.
C:In a service dependency exploration tool, contrastive guidance helps tool choice when resource names look similar, but unnecessary regeneration can erase working behavior; therefore the separate requirement that the review produces a small, auditable patch would remain unsatisfied.
D:In a service dependency exploration tool, unnecessary regeneration can erase working behavior and names alone may not capture the distinction in scope or authorization; the design would fail both conditions: the review produces a small, auditable patch and near-overlapping retrieval tools are selected by actual boundary.
Question 758
While preparing a supplier invoice extractor for deployment, engineers must ensure that the system distinguishes acceptable and unacceptable edge cases; they must also ensure that a status field can contain only approved business states. Which combination best satisfies those requirements?
- provide only a broad topic label as the classification rule; and accept any model-generated status description
- specify inclusion criteria and explicit exclusion conditions; and accept any model-generated status description
- specify inclusion criteria and explicit exclusion conditions; and enforce the approved status enum with structured output and validate it in the consumer
- implement only enforce the approved status enum with structured output and validate it in the consumer; make no corresponding change for the first requirement
- provide only a broad topic label as the classification rule; and enforce the approved status enum with structured output and validate it in the consumer
Explanation
Correct Answer
C:In a supplier invoice extractor, negative boundaries teach the model when a near-match must not trigger; alongside this, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, satisfying the distinct requirements that the system distinguishes acceptable and unacceptable edge cases and that a status field can contain only approved business states.
Incorrect Answers
A:In a supplier invoice extractor, generic labels leave ambiguous boundary cases undefined and free-form status phrases can violate a fixed business-state contract; the design would fail both conditions: the system distinguishes acceptable and unacceptable edge cases and a status field can contain only approved business states.
B:In a supplier invoice extractor, negative boundaries teach the model when a near-match must not trigger, but free-form status phrases can violate a fixed business-state contract; therefore the separate requirement that a status field can contain only approved business states would remain unsatisfied.
D:In a supplier invoice extractor, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, but the independent mechanism for the other criterion is absent: negative boundaries teach the model when a near-match must not trigger; as written, the design does not ensure that the system distinguishes acceptable and unacceptable edge cases.
E:In a supplier invoice extractor, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
Question 759
When designing a database migration coding project, the requirement is not satisfied unless delegated investigations stay within bounded scope and a new agent gets only durable context from a completed job. Which implementation addresses the two independent conditions?
- specify the question, allowed sources, expected output, and stopping criterion; and paste a full historical transcript into every new session
- ask every subagent to investigate everything it can find; and paste a full historical transcript into every new session
- specify the question, allowed sources, expected output, and stopping criterion; and initialize a fresh session with a verified structured summary
- ask every subagent to investigate everything it can find; and initialize a fresh session with a verified structured summary
Explanation
Correct Answer
C:In a database migration coding project, a task contract prevents specialist exploration from swallowing the coordinator's larger goal; alongside this, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, satisfying the distinct requirements that delegated investigations stay within bounded scope and that a new agent gets only durable context from a completed job.
Incorrect Answers
A:In a database migration coding project, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but irrelevant turns can consume context and revive outdated assumptions; therefore the separate requirement that a new agent gets only durable context from a completed job would remain unsatisfied.
B:In a database migration coding project, unbounded exploration dilutes signal and inflates context and latency and irrelevant turns can consume context and revive outdated assumptions; the design would fail both conditions: delegated investigations stay within bounded scope and a new agent gets only durable context from a completed job.
D:In a database migration coding project, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, but unbounded exploration dilutes signal and inflates context and latency; therefore the separate requirement that delegated investigations stay within bounded scope would remain unsatisfied.
Question 760
The release checklist for a contract clause extraction workflow explicitly checks that ambiguous write timeouts do not trigger duplicate side effects; it also checks that a broad tool catalog does not overwhelm a small task. What coordinated solution meets the checklist?
- check operation status or use an idempotency key before retry; and load all available MCP tools into every specialist turn
- check operation status or use an idempotency key before retry; and supply only context-relevant tools for the current agent
- repeat the mutation immediately because no success message arrived; and supply only context-relevant tools for the current agent
- repeat the mutation immediately because no success message arrived; and load all available MCP tools into every specialist turn
Explanation
Correct Answer
B:In a contract clause extraction workflow, a timeout can occur after the server commits the action, so retry safety needs state checks; alongside this, reducing irrelevant tool definitions improves selection and saves context, satisfying the distinct requirements that ambiguous write timeouts do not trigger duplicate side effects and that a broad tool catalog does not overwhelm a small task.
Incorrect Answers
A:In a contract clause extraction workflow, a timeout can occur after the server commits the action, so retry safety needs state checks, 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.
C:In a contract clause extraction workflow, reducing irrelevant tool definitions improves selection and saves context, but missing acknowledgment does not prove the first write was rolled back; therefore the separate requirement that ambiguous write timeouts do not trigger duplicate side effects would remain unsatisfied.
D:In a contract clause extraction workflow, missing acknowledgment does not prove the first write was rolled back and tool bloat makes the available actions harder to discriminate; the design would fail both conditions: ambiguous write timeouts do not trigger duplicate side effects and a broad tool catalog does not overwhelm a small task.