Question 390
An incident postmortem for a multi-source competitor research system requires controls so that the system can continue when one specialist returns an explicit failure and that tool-call logging does not modify a successful tool result. Which paired remedy covers both failure modes?
- record per-branch status and let the coordinator choose retry or partial response; and rewrite every tool result as a free-form paraphrase
- treat every subagent error string as a valid research conclusion; and use an observation-only hook for telemetry when rewriting is unnecessary
- treat every subagent error string as a valid research conclusion; and rewrite every tool result as a free-form paraphrase
- record per-branch status and let the coordinator choose retry or partial response; and use an observation-only hook for telemetry when rewriting is unnecessary
Explanation
Correct Answer
D:In a multi-source competitor research system, the orchestration layer must distinguish missing evidence from a negative factual finding; alongside this, separating instrumentation from mutation reduces the risk of corrupting evidence, satisfying the distinct requirements that the system can continue when one specialist returns an explicit failure and that tool-call logging does not modify a successful tool result.
Incorrect Answers
A:In a multi-source competitor research system, the orchestration layer must distinguish missing evidence from a negative factual finding, 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.
B:In a multi-source competitor research system, separating instrumentation from mutation reduces the risk of corrupting evidence, but error text is operational state rather than evidence about the world; therefore the separate requirement that the system can continue when one specialist returns an explicit failure would remain unsatisfied.
C:In a multi-source competitor research system, error text is operational state rather than evidence about the world and summaries can discard fields that subsequent steps require; the design would fail both conditions: the system can continue when one specialist returns an explicit failure and tool-call logging does not modify a successful tool result.
Question 391
For a customer account helpdesk agent, a reviewer identifies two independent obligations: schema-valid output is also checked against source evidence and context reduction does not erase unresolved obligations. Which proposal should be approved?
- assume a schema-conforming response is factually correct; and track pending approvals and required next steps in durable task state
- validate semantic constraints and provenance in application logic; and assume the agent will recall every open action from memory
- validate semantic constraints and provenance in application logic; and track pending approvals and required next steps in durable task state
- assume a schema-conforming response is factually correct; and assume the agent will recall every open action from memory
Explanation
Correct Answer
C:In a customer account helpdesk agent, JSON shape does not prove that an extracted claim is supported by the document; alongside this, persisted obligations survive when natural-language history is shortened, satisfying the distinct requirements that schema-valid output is also checked against source evidence and that context reduction does not erase unresolved obligations.
Incorrect Answers
A:In a customer account helpdesk agent, persisted obligations survive when natural-language history is shortened, but syntactic conformance cannot guarantee source-level truth; therefore the separate requirement that schema-valid output is also checked against source evidence would remain unsatisfied.
B:In a customer account helpdesk agent, JSON shape does not prove that an extracted claim is supported by the document, 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 customer account helpdesk agent, syntactic conformance cannot guarantee source-level truth and window truncation can drop an outstanding approval or escalation; the design would fail both conditions: schema-valid output is also checked against source evidence and context reduction does not erase unresolved obligations.
Question 392
When designing a shipping-exception helpdesk, the requirement is not satisfied unless a function call accepts only valid argument shapes and context reduction does not erase unresolved obligations. Which implementation addresses the two independent conditions?
- define the tool input schema, enable strict tool use where available, and validate inputs in the handler; and assume the agent will recall every open action from memory
- allow arbitrary keys and silently coerce incorrect types; and assume the agent will recall every open action from memory
- define the tool input schema, enable strict tool use where available, and validate inputs in the handler; and track pending approvals and required next steps in durable task state
- allow arbitrary keys and silently coerce incorrect types; and track pending approvals and required next steps in durable task state
Explanation
Correct Answer
C:In a shipping-exception helpdesk, strict tool inputs constrain generation, and handler validation provides a final enforceable argument boundary; alongside this, persisted obligations survive when natural-language history is shortened, satisfying the distinct requirements that a function call accepts only valid argument shapes and that context reduction does not erase unresolved obligations.
Incorrect Answers
A:In a shipping-exception helpdesk, strict tool inputs constrain generation, and handler validation provides a final enforceable argument boundary, 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.
B:In a shipping-exception helpdesk, unvalidated coercion can change intended operations or silently drop important fields and window truncation can drop an outstanding approval or escalation; the design would fail both conditions: a function call accepts only valid argument shapes and context reduction does not erase unresolved obligations.
D:In a shipping-exception helpdesk, persisted obligations survive when natural-language history is shortened, but unvalidated coercion can change intended operations or silently drop important fields; therefore the separate requirement that a function call accepts only valid argument shapes would remain unsatisfied.
Question 393
The release checklist for a merge-request policy gate explicitly checks that a common security rule remains active across the project; it also checks that an unusual null-value case is handled without inventing data. What coordinated solution meets the checklist?
- scope the security instruction only to one unrelated test directory; and include a demonstration showing how an absent field is represented
- keep project-wide security guidance in shared instructions rather than a narrow path glob; and show only records where every field is present
- keep project-wide security guidance in shared instructions rather than a narrow path glob; and include a demonstration showing how an absent field is represented
- scope the security instruction only to one unrelated test directory; and show only records where every field is present
Explanation
Correct Answer
C:In a merge-request policy gate, cross-cutting obligations should not disappear when an agent changes directories; alongside this, explicit missing-value examples clarify that omissions are not permission to hallucinate, satisfying the distinct requirements that a common security rule remains active across the project and that an unusual null-value case is handled without inventing data.
Incorrect Answers
A:In a merge-request policy gate, explicit missing-value examples clarify that omissions are not permission to hallucinate, but other code paths would lack the universal control; therefore the separate requirement that a common security rule remains active across the project would remain unsatisfied.
B:In a merge-request policy gate, cross-cutting obligations should not disappear when an agent changes directories, but the model lacks a model of the required missing-data behavior; therefore the separate requirement that an unusual null-value case is handled without inventing data would remain unsatisfied.
D:In a merge-request policy gate, other code paths would lack the universal control and the model lacks a model of the required missing-data behavior; the design would fail both conditions: a common security rule remains active across the project and an unusual null-value case is handled without inventing data.
Question 394
While preparing a repository maintenance copilot for deployment, engineers must ensure that the system can continue when one specialist returns an explicit failure; they must also ensure that the model can distinguish two similar business tools. Which combination best satisfies those requirements?
- record per-branch status and let the coordinator choose retry or partial response; and give both tools vague names with identical generic descriptions
- record per-branch status and let the coordinator choose retry or partial response; and give each tool a specific purpose and exclusion examples in its description
- treat every subagent error string as a valid research conclusion; and give both tools vague names with identical generic descriptions
- treat every subagent error string as a valid research conclusion; and give each tool a specific purpose and exclusion examples in its description
Explanation
Correct Answer
B:In a repository maintenance copilot, the orchestration layer must distinguish missing evidence from a negative factual finding; alongside this, discriminative descriptions reduce wrong routing when operations sound alike, satisfying the distinct requirements that the system can continue when one specialist returns an explicit failure and that the model can distinguish two similar business tools.
Incorrect Answers
A:In a repository maintenance copilot, the orchestration layer must distinguish missing evidence from a negative factual finding, 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.
C:In a repository maintenance copilot, error text is operational state rather than evidence about the world and a model cannot reliably select on boundaries that the interface never explains; the design would fail both conditions: the system can continue when one specialist returns an explicit failure and the model can distinguish two similar business tools.
D:In a repository maintenance copilot, discriminative descriptions reduce wrong routing when operations sound alike, but error text is operational state rather than evidence about the world; therefore the separate requirement that the system can continue when one specialist returns an explicit failure would remain unsatisfied.
Question 395
In a document field validation service, the acceptance criteria require that a corrected attempt preserves a record of prior validation findings and that a model learns a boundary between superficially similar cases. Which paired implementation meets both?
- replace all earlier outputs without recording the validation history; and include contrasting positive and negative demonstrations
- retain the original source, response version, and retry feedback; and show only easy positive samples
- retain the original source, response version, and retry feedback; and include contrasting positive and negative demonstrations
- replace all earlier outputs without recording the validation history; and show only easy positive samples
Explanation
Correct Answer
C:In a document field validation service, traceable attempts allow auditors to distinguish correction from silent overwrite; alongside this, near-boundary examples communicate the decisive distinction and reduce false positives, satisfying the distinct requirements that a corrected attempt preserves a record of prior validation findings and that a model learns a boundary between superficially similar cases.
Incorrect Answers
A:In a document field validation service, near-boundary examples communicate the decisive distinction and reduce false positives, but the reason for a changed value becomes untraceable; therefore the separate requirement that a corrected attempt preserves a record of prior validation findings would remain unsatisfied.
B:In a document field validation service, traceable attempts allow auditors to distinguish correction from silent overwrite, but the model may generalize the label to unrelated but similar-looking items; therefore the separate requirement that a model learns a boundary between superficially similar cases would remain unsatisfied.
D:In a document field validation service, the reason for a changed value becomes untraceable and the model may generalize the label to unrelated but similar-looking items; the design would fail both conditions: a corrected attempt preserves a record of prior validation findings and a model learns a boundary between superficially similar cases.
Question 396
The release checklist for a multi-source policy brief service explicitly checks that a failed MCP operation is visible as an error to the client; it also checks that important workflow state survives context compression or process restarts. What coordinated solution meets the checklist?
- return a success-shaped value saying the operation probably worked; and persist authoritative task facts and artifact IDs outside ephemeral conversation text
- mark the tool result as an error and supply structured failure details; and depend on the model remembering a prior value forever
- implement only mark the tool result as an error and supply structured failure details; make no corresponding change for the second requirement
- return a success-shaped value saying the operation probably worked; and depend on the model remembering a prior value forever
- mark the tool result as an error and supply structured failure details; and persist authoritative task facts and artifact IDs outside ephemeral conversation text
Explanation
Correct Answer
E:In a multi-source policy brief service, explicit error status separates failed execution from valid data content; alongside this, external durable state can be reloaded and checked when the session window changes, satisfying the distinct requirements that a failed MCP operation is visible as an error to the client and that important workflow state survives context compression or process restarts.
Incorrect Answers
A:In a multi-source policy brief service, external durable state can be reloaded and checked when the session window changes, but downstream agents can mistake a failure for verified business data; therefore the separate requirement that a failed MCP operation is visible as an error to the client would remain unsatisfied.
B:In a multi-source policy brief service, explicit error status separates failed execution from valid data content, 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.
C:In a multi-source policy brief service, explicit error status separates failed execution from valid data content, but the independent mechanism for the other criterion is absent: external durable state can be reloaded and checked when the session window changes; as written, the design does not ensure that important workflow state survives context compression or process restarts.
D:In a multi-source policy brief service, downstream agents can mistake a failure for verified business data and context limits and summarization can lose exact identifiers; the design would fail both conditions: a failed MCP operation is visible as an error to the client and important workflow state survives context compression or process restarts.
Question 397
Tests for a mobile client bug-fix task will pass only if API conventions apply only to source files under an API directory and if the review produces a small, auditable patch. Which proposed design directly satisfies both checks?
- put API-specific formatting rules in always-on project guidance; and iterate with focused diffs rather than wholesale regeneration
- put API-specific formatting rules in always-on project guidance; and replace every file in the component to ensure consistency
- add a .claude/rules file with paths matching the API subtree; and replace every file in the component to ensure consistency
- add a .claude/rules file with paths matching the API subtree; and iterate with focused diffs rather than wholesale regeneration
Explanation
Correct Answer
D:In a mobile client bug-fix task, path-scoped rules load when the target context matches, keeping unrelated tasks clean; alongside this, narrow changes are easier to test and evaluate against explicit requirements, satisfying the distinct requirements that API conventions apply only to source files under an API directory and that the review produces a small, auditable patch.
Incorrect Answers
A:In a mobile client bug-fix task, narrow changes are easier to test and evaluate against explicit requirements, but frontend and documentation tasks then receive irrelevant instructions; therefore the separate requirement that API conventions apply only to source files under an API directory would remain unsatisfied.
B:In a mobile client bug-fix task, frontend and documentation tasks then receive irrelevant instructions and unnecessary regeneration can erase working behavior; the design would fail both conditions: API conventions apply only to source files under an API directory and the review produces a small, auditable patch.
C:In a mobile client bug-fix task, path-scoped rules load when the target context matches, keeping unrelated tasks clean, but unnecessary regeneration can erase working behavior; therefore the separate requirement that the review produces a small, auditable patch would remain unsatisfied.
Question 398
Production readiness for an internal developer coding workflow depends on ensuring that independent stages of a complex job run efficiently and that context reduction does not erase unresolved obligations. Select the most appropriate combined approach.
- divide work along independent outputs and run those stages in parallel; and assume the agent will recall every open action from memory
- split the job into an arbitrary fixed chain of agents; and assume the agent will recall every open action from memory
- divide work along independent outputs and run those stages in parallel; and track pending approvals and required next steps in durable task state
- split the job into an arbitrary fixed chain of agents; and track pending approvals and required next steps in durable task state
- implement only divide work along independent outputs and run those stages in parallel; make no corresponding change for the second requirement
Explanation
Correct Answer
C:In an internal developer coding workflow, dependency-aware decomposition avoids serial work when branches do not consume one another; alongside this, persisted obligations survive when natural-language history is shortened, satisfying the distinct requirements that independent stages of a complex job run efficiently and that context reduction does not erase unresolved obligations.
Incorrect Answers
A:In an internal developer coding workflow, dependency-aware decomposition avoids serial work when branches do not consume one another, 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.
B:In an internal developer coding workflow, a rigid sequence creates waits even where no dependency exists and window truncation can drop an outstanding approval or escalation; the design would fail both conditions: independent stages of a complex job run efficiently and context reduction does not erase unresolved obligations.
D:In an internal developer coding workflow, persisted obligations survive when natural-language history is shortened, 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.
E:In an internal developer coding workflow, dependency-aware decomposition avoids serial work when branches do not consume one another, but the independent mechanism for the other criterion is absent: persisted obligations survive when natural-language history is shortened; as written, the design does not ensure that context reduction does not erase unresolved obligations.
Question 399
During review of a dependency upgrade initiative, an unmet criterion states that the implementation plan receives stakeholder sign-off. Which measure resolves this specific gap?
- treat the agent's internally generated plan as implicit approval
- present ordered changes, risks, and verification steps before switching to execution
- clarify scope and acceptance criteria while planning
- exit the planning stage and perform scoped implementation with verification
Explanation
Correct Answer
B:For a dependency upgrade initiative, an explicit review point aligns the agent's work with the authorized scope; this directly establishes that the implementation plan receives stakeholder sign-off instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a dependency upgrade initiative, the system cannot infer external authorization from its own reasoning; as a result, the stated requirement that the implementation plan receives stakeholder sign-off would still not be met.
C:Although a reviewed plan should resolve unknown targets and rollback expectations before writes, that only supports the distinct goal that ambiguous requirements are resolved before a destructive migration, not the requirement that the implementation plan receives stakeholder sign-off in a dependency upgrade initiative.
D:Although planning describes intended operations while execution applies and checks them, that only supports the distinct goal that an approved plan is translated into controlled edits and tests, not the requirement that the implementation plan receives stakeholder sign-off in a dependency upgrade initiative.
Question 400
An audit of an automated CI review service asks how to make sure that CI failures provide actionable evidence to maintainers. Which implementation should be selected?
- run Claude Code in non-interactive print mode with -p
- scope runner credentials, worktree access, and allowed tools to its task
- persist structured errors, relevant logs, and a bounded diagnostic summary
- discard the runner logs and keep only the assistant's final sentence
Explanation
Correct Answer
C:For an automated CI review service, stable artifacts help maintainers reproduce the problem without rerunning a chat; this directly establishes that CI failures provide actionable evidence to maintainers instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although headless invocation permits scripted automation and exits after the requested task, that only supports the distinct goal that a CI job invokes Claude without a terminal conversation, not the requirement that CI failures provide actionable evidence to maintainers in an automated CI review service.
B:Although CI identity and tool permissions control real write capabilities independent of model instructions, that only supports the distinct goal that a pull-request bot runs with minimum necessary authority, not the requirement that CI failures provide actionable evidence to maintainers in an automated CI review service.
D:In an automated CI review service, the missing trace impedes diagnosis of command or infrastructure failures; as a result, the stated requirement that CI failures provide actionable evidence to maintainers would still not be met.