Question 990
While preparing a repository search copilot for deployment, engineers must ensure that a large research job combines specialized findings into one answer; they must also ensure that a team shares a repository-specific MCP server configuration. Which combination best satisfies those requirements?
- have all subagents independently publish the final answer; and commit a reviewed project .mcp.json without credentials
- have all subagents independently publish the final answer; and configure each contributor's personal MCP registry manually
- implement only use a coordinator that delegates focused tasks and owns final synthesis; make no corresponding change for the second requirement
- use a coordinator that delegates focused tasks and owns final synthesis; and configure each contributor's personal MCP registry manually
- use a coordinator that delegates focused tasks and owns final synthesis; and commit a reviewed project .mcp.json without credentials
Explanation
Correct Answer
E:In a repository search copilot, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter; alongside this, project-scoped configuration can be distributed with the repository while keeping secrets external, satisfying the distinct requirements that a large research job combines specialized findings into one answer and that a team shares a repository-specific MCP server configuration.
Incorrect Answers
A:In a repository search copilot, project-scoped configuration can be distributed with the repository while keeping secrets external, but independent final outputs offer no single point to reconcile contradictions; therefore the separate requirement that a large research job combines specialized findings into one answer would remain unsatisfied.
B:In a repository search copilot, independent final outputs offer no single point to reconcile contradictions and local personal settings do not create a reproducible team project setup; the design would fail both conditions: a large research job combines specialized findings into one answer and a team shares a repository-specific MCP server configuration.
C:In a repository search copilot, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, but the independent mechanism for the other criterion is absent: project-scoped configuration can be distributed with the repository while keeping secrets external; as written, the design does not ensure that a team shares a repository-specific MCP server configuration.
D:In a repository search copilot, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, 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.
Question 991
A readiness review for a research PDF metadata pipeline requires that a tool receives a typed and bounded request; that a truncated response is not mistaken for successful completion; and that a partially failed batch is repaired efficiently. Which THREE actions directly implement those distinct requirements? Choose THREE.
- rerun the entire completed batch whenever one record fails
- interpret every non-tool stop reason as a successful final answer
- handle max_tokens as truncation rather than end_turn
- identify failed records and resubmit only safe retry candidates
- define required properties and types in the input schema and validate arguments at the execution boundary
- accept one unstructured free-text argument for every operation
Explanation
Correct Answers
C:For a research PDF metadata pipeline, reaching an output limit is a stop condition but does not establish task completion, which directly establishes that a truncated response is not mistaken for successful completion; the separate requirement that a partially failed batch is repaired efficiently is handled by a different action.
D:For a research PDF metadata pipeline, selective retry avoids paying again for already successful items, which directly establishes that a partially failed batch is repaired efficiently; the separate requirement that a tool receives a typed and bounded request is handled by a different action.
E:For a research PDF metadata pipeline, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, which directly establishes that a tool receives a typed and bounded request; the separate requirement that a truncated response is not mistaken for successful completion is handled by a different action.
Incorrect Answers
A:For a research PDF metadata pipeline, successful work would be duplicated unnecessarily, so this option cannot establish that a partially failed batch is repaired efficiently; correctly addressing a tool receives a typed and bounded request elsewhere does not repair that deficiency.
B:For a research PDF metadata pipeline, a length-limited result may be incomplete or unusable, so this option cannot establish that a truncated response is not mistaken for successful completion; correctly addressing a partially failed batch is repaired efficiently elsewhere does not repair that deficiency.
F:For a research PDF metadata pipeline, unconstrained prose leaves parsing and validation errors to ad hoc handler inference, so this option cannot establish that a tool receives a typed and bounded request; correctly addressing a truncated response is not mistaken for successful completion elsewhere does not repair that deficiency.
Question 992
For a large-codebase architecture explorer, a reviewer identifies two independent obligations: file writes are blocked outside an approved workspace and a conversational task does not invoke tools needlessly. Which proposal should be approved?
- check resolved target paths in the pre-tool policy gate; and force a tool on every message regardless of intent
- check resolved target paths in the pre-tool policy gate; and use automatic tool choice when a call is optional
- tell the model not to leave the workspace; and use automatic tool choice when a call is optional
- tell the model not to leave the workspace; and force a tool on every message regardless of intent
Explanation
Correct Answer
B:In a large-codebase architecture explorer, a boundary check on the actual tool argument enforces the permitted filesystem scope; alongside this, auto allows the model to answer directly when no external side effect or fresh data is needed, satisfying the distinct requirements that file writes are blocked outside an approved workspace and that a conversational task does not invoke tools needlessly.
Incorrect Answers
A:In a large-codebase architecture explorer, a boundary check on the actual tool argument enforces the permitted filesystem scope, but mandatory calls add latency and can invoke irrelevant operations; therefore the separate requirement that a conversational task does not invoke tools needlessly would remain unsatisfied.
C:In a large-codebase architecture explorer, auto allows the model to answer directly when no external side effect or fresh data is needed, but language instructions do not intercept a disallowed filesystem operation; therefore the separate requirement that file writes are blocked outside an approved workspace would remain unsatisfied.
D:In a large-codebase architecture explorer, language instructions do not intercept a disallowed filesystem operation and mandatory calls add latency and can invoke irrelevant operations; the design would fail both conditions: file writes are blocked outside an approved workspace and a conversational task does not invoke tools needlessly.
Question 993
Tests for a monorepo feature modernization project will pass only if regressions introduced during refinement are detected and fixed and if all contributors receive the repository's stable engineering conventions. Which proposed design directly satisfies both checks?
- keep layering patches without checking the last stable behavior; and put concise shared guidance in the repository root CLAUDE.md
- implement only put concise shared guidance in the repository root CLAUDE.md; make no corresponding change for the first requirement
- keep layering patches without checking the last stable behavior; and put team-wide rules only in one developer's user-level instructions
- restore or revise the problematic change and retest affected paths; and put team-wide rules only in one developer's user-level instructions
- restore or revise the problematic change and retest affected paths; and put concise shared guidance in the repository root CLAUDE.md
Explanation
Correct Answer
E:In a monorepo feature modernization project, iteration includes detecting regressions and returning to a passing state; alongside this, project instructions travel with the codebase and establish common architecture and build constraints, satisfying the distinct requirements that regressions introduced during refinement are detected and fixed and that all contributors receive the repository's stable engineering conventions.
Incorrect Answers
A:In a monorepo feature modernization project, project instructions travel with the codebase and establish common architecture and build constraints, 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 feature modernization project, project instructions travel with the codebase and establish common architecture and build constraints, but the independent mechanism for the other criterion is absent: iteration includes detecting regressions and returning to a passing state; as written, the design does not ensure that regressions introduced during refinement are detected and fixed.
C:In a monorepo feature modernization project, cumulative changes can bury the source of failure and personal files do not distribute the intended conventions to other contributors; the design would fail both conditions: regressions introduced during refinement are detected and fixed and all contributors receive the repository's stable engineering conventions.
D:In a monorepo feature modernization project, iteration includes detecting regressions and returning to a passing state, but personal files do not distribute the intended conventions to other contributors; therefore the separate requirement that all contributors receive the repository's stable engineering conventions would remain unsatisfied.
Question 994
An audit of a source-grounded policy synthesis service asks how to make sure that a report separates documented findings from its own inference. Which implementation should be selected?
- label direct source facts separately from analytical conclusions
- attach source IDs and relevant excerpts to individual claims
- present every deduction as a direct source quotation
- carry citation identifiers and retrieval context through synthesis
Explanation
Correct Answer
A:For a source-grounded policy synthesis service, distinguishing evidence from interpretation prevents inference being misattributed to a document; this directly establishes that a report separates documented findings from its own inference instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although claim-level provenance enables an auditor to verify each assertion, that only supports the distinct goal that a synthesized statement can be traced to its supporting source, not the requirement that a report separates documented findings from its own inference in a source-grounded policy synthesis service.
C:In a source-grounded policy synthesis service, unsupported attribution misrepresents what the source actually says; as a result, the stated requirement that a report separates documented findings from its own inference would still not be met.
D:Although provenance metadata must remain attached when intermediate summaries are merged, that only supports the distinct goal that source identity survives multi-agent research handoffs, not the requirement that a report separates documented findings from its own inference in a source-grounded policy synthesis service.
Question 995
An architecture review of a research PDF metadata pipeline finds two missing guarantees: each batch result is matched to its originating record; a handoff retains only action-relevant context. What two-part change closes both gaps?
- match returned results to input rows only by array position; and send every previous chat turn to each new worker
- assign stable custom IDs and map results by those IDs; and send every previous chat turn to each new worker
- assign stable custom IDs and map results by those IDs; and pass a compact structured record of facts, decisions, pending tasks, and sources
- match returned results to input rows only by array position; and pass a compact structured record of facts, decisions, pending tasks, and sources
Explanation
Correct Answer
C:In a research PDF metadata pipeline, asynchronous completion order need not match submission order; alongside this, focused handoffs reduce context size while protecting continuity-critical details, satisfying the distinct requirements that each batch result is matched to its originating record and that a handoff retains only action-relevant context.
Incorrect Answers
A:In a research PDF metadata pipeline, out-of-order or failed items can corrupt record association and large histories include irrelevant or outdated information; the design would fail both conditions: each batch result is matched to its originating record and a handoff retains only action-relevant context.
B:In a research PDF metadata pipeline, asynchronous completion order need not match submission order, but large histories include irrelevant or outdated information; therefore the separate requirement that a handoff retains only action-relevant context would remain unsatisfied.
D:In a research PDF metadata pipeline, focused handoffs reduce context size while protecting continuity-critical details, but out-of-order or failed items can corrupt record association; therefore the separate requirement that each batch result is matched to its originating record would remain unsatisfied.
Question 996
Tests for an after-sales issue resolver will pass only if the agent can recover exact policy facts after compaction and if an extractor always returns the identifiers required by downstream code. Which proposed design directly satisfies both checks?
- treat the compressed summary as an immutable source of truth; and declare mandatory schema fields in the required list
- treat the compressed summary as an immutable source of truth; and treat every identifier as an optional free-form note
- retrieve authoritative facts from a durable store when needed; and declare mandatory schema fields in the required list
- retrieve authoritative facts from a durable store when needed; and treat every identifier as an optional free-form note
Explanation
Correct Answer
C:In an after-sales issue resolver, re-reading source state restores precision that a condensed history cannot guarantee; alongside this, required properties prevent accidental omission of key attributes, satisfying the distinct requirements that the agent can recover exact policy facts after compaction and that an extractor always returns the identifiers required by downstream code.
Incorrect Answers
A:In an after-sales issue resolver, required properties prevent accidental omission of key attributes, but summaries may simplify caveats or omit an exception; therefore the separate requirement that the agent can recover exact policy facts after compaction would remain unsatisfied.
B:In an after-sales issue resolver, summaries may simplify caveats or omit an exception and the consumer cannot reliably rely on a field that may be omitted; the design would fail both conditions: the agent can recover exact policy facts after compaction and an extractor always returns the identifiers required by downstream code.
D:In an after-sales issue resolver, re-reading source state restores precision that a condensed history cannot guarantee, 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.
Question 997
In a technical review of a shipping-exception helpdesk, the architect must address the following constraints together: context reduction does not erase unresolved obligations; a payment-changing action obtains explicit user authorization. Which change set is most defensible?
- track pending approvals and required next steps in durable task state; and confirm the intended action and scope before invoking the write
- assume the agent will recall every open action from memory; and confirm the intended action and scope before invoking the write
- assume the agent will recall every open action from memory; and treat a request for information as permission to mutate the account
- track pending approvals and required next steps in durable task state; and treat a request for information as permission to mutate the account
Explanation
Correct Answer
A:In a shipping-exception helpdesk, persisted obligations survive when natural-language history is shortened; alongside this, consent is specific to the side effect and cannot be inferred from a general inquiry, satisfying the distinct requirements that context reduction does not erase unresolved obligations and that a payment-changing action obtains explicit user authorization.
Incorrect Answers
B:In a shipping-exception helpdesk, consent is specific to the side effect and cannot be inferred from a general inquiry, 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.
C:In a shipping-exception helpdesk, window truncation can drop an outstanding approval or escalation and asking a question does not approve a financial change; the design would fail both conditions: context reduction does not erase unresolved obligations and a payment-changing action obtains explicit user authorization.
D:In a shipping-exception helpdesk, persisted obligations survive when natural-language history is shortened, 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 998
Production readiness for a change-impact analysis service depends on ensuring that a coding agent inspects a known source file without changing it and that a delegated agent receives the background it needs to act. Select the most appropriate combined approach.
- run arbitrary shell commands to modify the file during inspection; and assume the child agent sees all previous coordinator turns
- use Read on the identified file; and assume the child agent sees all previous coordinator turns
- run arbitrary shell commands to modify the file during inspection; and pass the necessary task context and references explicitly at invocation
- use Read on the identified file; and pass the necessary task context and references explicitly at invocation
Explanation
Correct Answer
D:In a change-impact analysis service, file reading provides exact content for analysis without executing the project; alongside this, subagents do not automatically inherit the coordinator's entire conversational history, satisfying the distinct requirements that a coding agent inspects a known source file without changing it and that a delegated agent receives the background it needs to act.
Incorrect Answers
A:In a change-impact analysis service, mutation is unnecessary for a read-only code review and implicit context inheritance makes delegation fragile and incomplete; the design would fail both conditions: a coding agent inspects a known source file without changing it and a delegated agent receives the background it needs to act.
B:In a change-impact analysis service, file reading provides exact content for analysis without executing the project, but implicit context inheritance makes delegation fragile and incomplete; therefore the separate requirement that a delegated agent receives the background it needs to act would remain unsatisfied.
C:In a change-impact analysis service, subagents do not automatically inherit the coordinator's entire conversational history, but mutation is unnecessary for a read-only code review; therefore the separate requirement that a coding agent inspects a known source file without changing it would remain unsatisfied.
Question 999
Tests for a cross-service developer portal will pass only if one developer keeps an MCP server private to their machine and if a delegated agent receives the background it needs to act. Which proposed design directly satisfies both checks?
- use a user-local MCP configuration rather than committing project configuration; and assume the child agent sees all previous coordinator turns
- use a user-local MCP configuration rather than committing project configuration; and pass the necessary task context and references explicitly at invocation
- commit private workstation commands into the repository's shared MCP file; and pass the necessary task context and references explicitly at invocation
- commit private workstation commands into the repository's shared MCP file; and assume the child agent sees all previous coordinator turns
Explanation
Correct Answer
B:In a cross-service developer portal, user scope is appropriate for personal endpoints and avoids distributing local paths; alongside this, subagents do not automatically inherit the coordinator's entire conversational history, satisfying the distinct requirements that one developer keeps an MCP server private to their machine and that a delegated agent receives the background it needs to act.
Incorrect Answers
A:In a cross-service developer portal, user scope is appropriate for personal endpoints and avoids distributing local paths, but implicit context inheritance makes delegation fragile and incomplete; therefore the separate requirement that a delegated agent receives the background it needs to act would remain unsatisfied.
C:In a cross-service developer portal, subagents do not automatically inherit the coordinator's entire conversational history, but machine-specific commands can break teammates' environments; therefore the separate requirement that one developer keeps an MCP server private to their machine would remain unsatisfied.
D:In a cross-service developer portal, machine-specific commands can break teammates' environments and implicit context inheritance makes delegation fragile and incomplete; the design would fail both conditions: one developer keeps an MCP server private to their machine and a delegated agent receives the background it needs to act.
Question 1000
When designing an order-status triage agent, the requirement is not satisfied unless a transient upstream outage is retried safely and confidence scores reflect available evidence and uncertainty. Which implementation addresses the two independent conditions?
- retry access-denied and invalid-input errors indefinitely; and calibrate confidence against known outcomes and source support
- apply a bounded backoff only to classified retryable errors; and calibrate confidence against known outcomes and source support
- apply a bounded backoff only to classified retryable errors; and set confidence to high whenever the explanation is detailed
- retry access-denied and invalid-input errors indefinitely; and set confidence to high whenever the explanation is detailed
Explanation
Correct Answer
B:In an order-status triage agent, transient failures can heal without re-running permanently invalid requests; alongside this, observed error rates and evidence quality are better than a fluent self-rating, satisfying the distinct requirements that a transient upstream outage is retried safely and that confidence scores reflect available evidence and uncertainty.
Incorrect Answers
A:In an order-status triage agent, observed error rates and evidence quality are better than a fluent self-rating, but permanent failures require a fix or escalation rather than repetition; therefore the separate requirement that a transient upstream outage is retried safely would remain unsatisfied.
C:In an order-status triage agent, transient failures can heal without re-running permanently invalid requests, but verbal detail is not a validated reliability estimate; therefore the separate requirement that confidence scores reflect available evidence and uncertainty would remain unsatisfied.
D:In an order-status triage agent, permanent failures require a fix or escalation rather than repetition and verbal detail is not a validated reliability estimate; the design would fail both conditions: a transient upstream outage is retried safely and confidence scores reflect available evidence and uncertainty.