Question 100
An agent controller must coordinate recoverable workflows across interruptions. A tool result was durably saved with its request ID, but the host crashed before passing it back to Claude. Which response is most reliable?
- Reauthorize actions against the current permission configuration
- Create a clean conversation and explicitly scoped context for the new task
- Persist origin session, fork lineage, task ID, and artifact references
- Load checkpoint status and reuse completed result artifacts
- Replay the persisted, ID-correlated tool_result into the restored conversation
Explanation
Correct Answer
E:When the result is already durably recorded, the host can resume the exact tool-use/result exchange without repeating the side-effecting operation.
Incorrect Answers
A:It would be appropriate when a worker changed permissions in an earlier session, but today's role policy differs; session continuity is not continuing authorization; permissions may change independently of the saved transcript. Here, a tool result was durably saved with its request ID, but the host crashed before passing it back to Claude, so a different mechanism is required.
B:Starting fresh avoids accidentally promoting data from an unrelated case into a new workflow; the alternative problem occurs when a new agent task accidentally inherits old customer contact details. The present scenario instead requires the system to restore a completed tool result without running the tool twice.
C:This choice is relevant when engineers need to trace exactly where a resumed result originated; provenance across resumes and forks is essential for diagnosing which state or branch produced a disputed conclusion. Here, however, a tool result was durably saved with its request ID, but the host crashed before passing it back to Claude.
D:A checkpointed task graph supports partial recovery and avoids paying for identical completed work; it protects against the case where an interrupted research task has several finished specialist outputs, rather than the failure described here: a tool result was durably saved with its request ID, but the host crashed before passing it back to Claude.
Question 101
A research coordinator must synthesize facts from many long reports. Two sources use the same term with incompatible definitions. What should the team do to resolve this particular gap?
- Use effective dates and revision history to resolve precedence
- Record each definition alongside its source and compare before synthesis
- Store the numeric values and page or figure reference for the chart
- Build a short evidence ledger with the relevant claim, number, source, and date
Explanation
Correct Answer
B:Without definition tracking, a long summary can accidentally merge incompatible metrics into one confident statement.
Incorrect Answers
A:Time-sensitive policy questions require temporal reasoning; simple keyword retrieval can privilege an obsolete statement; that applies when an older report says a rule is active, but a later update supersedes it, whereas this case requires a response to two sources use the same term with incompatible definitions.
C:A lossy narrative can change quantitative meaning; structured values and a locator preserve evidence for verification; it protects against the case where a conclusion relies on a small chart extracted from a large PDF, rather than the failure described here: two sources use the same term with incompatible definitions.
D:This measure fits a different trigger: a key statistic is buried between hundreds of unrelated facts. In that setting, A compact ledger brings decisive facts back into active context instead of hoping the writer finds them inside long retrieved text; it does not resolve the present need to retain competing meanings explicitly.
Question 102
An engineering assistant writes migration plans for internal reviewers. A rollout has a strict zero-downtime requirement. Which control is most directly relevant?
- Request checkpoints, reversal conditions, and limitations of restoring state
- Require backward compatibility, staged rollout, and rollback considerations
- Require each risk to be marked observed, inferred, or unknown with supporting evidence
- Require affected service names, dependency edges, and verification steps
Explanation
Correct Answer
B:An explicit availability constraint changes feasible migration designs; it must be visible before the model proposes modifications.
Incorrect Answers
A:Rollback feasibility must be assessed during planning, not assumed after the assistant recommends irreversible changes; that applies when a reviewer cares about data migration reversibility, whereas this case requires a response to a rollout has a strict zero-downtime requirement.
C:Distinguishing established facts from hypotheses prevents speculative risk language from masquerading as a verified defect; this is useful for a risk register mixes confirmed issues with guesses, but it leaves the stated requirement to state operational constraints as acceptance gates unmet.
D:This measure fits a different trigger: a plan says 'update services' without naming dependent components. In that setting, An actionable architecture plan names components and checks rather than relying on unbounded generic tasks; it does not resolve the present need to state operational constraints as acceptance gates.
Question 103
A research pipeline emits structured literature reviews. A citation looks valid but links to a different paper title. How should the workflow be adjusted?
- Require the base population or flag the statistic as incomplete
- Resolve citation metadata and compare it with the claimed title and authors
- Check the identifier format and request a corrected value when supported by the source
- Check claims against retrieved sources and reject unsupported assertions
Explanation
Correct Answer
B:A plausible-looking identifier can be factually wrong; checking external metadata tests referential truth beyond structure.
Incorrect Answers
A:A number without its denominator can be misleading; semantic validation must check whether the claim is interpretable; this is useful for a summarized study reports a percentage without a denominator, but it leaves the stated requirement to verify identifiers against their referenced records unmet.
C:This measure fits a different trigger: a citation record has a malformed DOI string. In that setting, A targeted citation check catches formatting mistakes before publication while keeping evidence matching as a separate step; it does not resolve the present need to verify identifiers against their referenced records.
D:Schema enforcement is not fact checking; a reviewer must compare meaning with evidence rather than regenerate well-formed guesses; that applies when the model keeps producing unsupported claims despite clean JSON, whereas this case requires a response to a citation looks valid but links to a different paper title.
Question 104
An internal compliance system tracks where evidence for decisions originated. Two tools return different customer statuses from separate data stores. Which implementation decision is the best fit?
- Mark quotations, extracted facts, and analyst inferences separately
- Carry source ID, page, and extraction run identifier into the final record
- Record retrieval time and a content digest or archived excerpt where permitted
- Compare source-of-truth ownership and freshness before selecting a status
Explanation
Correct Answer
D:A newer timestamp is not always sufficient if one system is a derived cache; authority and synchronization matter. This matches the workflow goal to identify the authoritative system of record rather than introducing an unrelated action.
Incorrect Answers
A:Separating evidence types prevents a model's synthesis from appearing to be a verbatim statement by an external authority; that applies when a research report mixes direct quotations and model paraphrases without labeling them, whereas this case requires a response to two tools return different customer statuses from separate data stores.
B:A provenance chain connects the published value to the observed document and the specific processing run that produced it; this is useful for an extraction result is copied into a report with no link to its document, but it leaves the stated requirement to identify the authoritative system of record unmet.
C:Web evidence is mutable; a stable reference explains what the system actually saw when reaching its original conclusion; it protects against the case where a cited webpage changes after the original analysis was completed, rather than the failure described here: two tools return different customer statuses from separate data stores.
Question 105
A repository team decides how to package MCP integrations for collaboration. A developer tests an experimental local server that colleagues must not use. What should the architect specify in the design?
- Keep the project-scoped server definition under version control without secrets
- Use a local-only MCP definition rather than committing it to shared project settings
- Inspect the effective MCP configuration and resolve duplicate definitions
- List approved tools and schemas before requesting tool calls
- Review changed schemas and run integration checks before team rollout
Explanation
Correct Answer
B:Local scope prevents unreviewed capabilities from silently appearing in every contributor's workspace. For the stated case, the check is whether the system can restrict a temporary integration to local scope; this approach supplies that control.
Incorrect Answers
A:This measure fits a different trigger: a project-wide tool server has been approved for every contributor to that repository. In that setting, Versioned project configuration gives contributors consistent definitions while leaving credentials outside shared files; it does not resolve the present need to restrict a temporary integration to local scope.
C:MCP discovery depends on active connection configuration; changing model instructions cannot fix an incorrect server command; this is useful for the same server appears in multiple configuration layers with conflicting commands, but it leaves the stated requirement to restrict a temporary integration to local scope unmet.
D:Discovery can inform architecture and permission review while avoiding side effects associated with actual operation execution; it protects against the case where a team wants to discover available server tools without invoking any of them, rather than the failure described here: a developer tests an experimental local server that colleagues must not use.
E:Server version changes can break tool calls even when connection setup succeeds, so schema compatibility requires testing; that applies when a server package is upgraded and its tool arguments change, whereas this case requires a response to a developer tests an experimental local server that colleagues must not use.
Question 106
An engineering assistant investigates a large repository with long context demands. A developer returns to a bug after several unrelated investigations. Which change most directly addresses this condition?
- Audit compacted state against a checklist of nonnegotiable rules
- Provide a compact task-state recap with affected files, assumptions, and unresolved work
- Maintain distinct passed, failed, blocked, and not-run status fields
- Record source revision and file or symbol location alongside the claim
Explanation
Correct Answer
B:Explicit state restoration prevents old side discussions from becoming accidental requirements for the current fix.
Incorrect Answers
A:Compaction should reduce volume, not silently remove guardrails necessary for safe continuation; it protects against the case where a critical security constraint disappears after context compaction, rather than the failure described here: a developer returns to a bug after several unrelated investigations.
C:A clear status ledger prevents a verbose conversation from blurring planned checks with actual execution results; that applies when a long analysis mixes successful tests and unrun suggestions, whereas this case requires a response to a developer returns to a bug after several unrelated investigations.
D:Code facts change over time; a reference to the inspected revision makes the assertion auditable; this is useful for a summary says a function was removed but contains no commit or path evidence, but it leaves the stated requirement to restore the active issue's constraints unmet.
Question 107
An organization uses Claude to summarize an archive of technical incidents. Some incidents must be summarized in chronological dependency order. What is the most defensible next step?
- Use a synchronous, reviewable workflow for that specific incident
- Verify stored document digest and cited spans before accepting the result
- Include stable incident IDs in each request and result mapping
- Process prerequisite records before dispatching dependent summaries
Explanation
Correct Answer
D:Batching does not remove ordering requirements; data-dependent reports need validated inputs from earlier stages. For the stated case, the check is whether the system can separate dependent chains from independent batch items; this approach supplies that control.
Incorrect Answers
A:Interactive escalation has different latency and control requirements from an archival bulk job; it protects against the case where a critical incident needs an urgent follow-up question from a human, rather than the failure described here: some incidents must be summarized in chronological dependency order.
B:Matching output to the right input is a semantic and provenance requirement, not merely a batch-completion check; that applies when one summary appears to describe a different source document, whereas this case requires a response to some incidents must be summarized in chronological dependency order.
C:Without correlation keys, a bulk response can be structurally complete but impossible to assign safely to the correct incident; this is useful for a run returns finished summaries but no mapping to original incident IDs, but it leaves the stated requirement to separate dependent chains from independent batch items unmet.
Question 108
A coordinator divides a codebase-migration assessment among specialist agents. The team wants a single conclusion after three worker assessments. Which approach satisfies the stated constraint?
- Send only relevant file maps and task-specific excerpts to each specialist
- Have the coordinator evaluate worker evidence and generate the consolidated recommendation
- Define distinct tasks and structured outputs for each worker
- Return a structured blocker status with severity and supporting evidence
Explanation
Correct Answer
B:Specialists provide evidence and domain judgments; synthesis ownership prevents conflicting independently published conclusions.
Incorrect Answers
A:Broadcasting the whole repository inflates context and cost and obscures what each worker must evaluate; that applies when the coordinator can pass a 200-page repository dump to every worker, whereas this case requires a response to the team wants a single conclusion after three worker assessments.
C:This measure fits a different trigger: one worker is responsible for dependency scanning and another for test-risk analysis. In that setting, Explicit outputs make the coordinator's merge traceable and prevent the workers from competing over the same incomplete artifact; it does not resolve the present need to maintain one final decision authority.
D:A typed blocker can halt or reroute downstream steps; a buried sentence is easy for a later summarizer to miss; this is useful for a security worker discovers an immediate blocker during parallel migration analysis, but it leaves the stated requirement to maintain one final decision authority unmet.
Question 109
An invoice-extraction team builds reliable prompting for standardized records. The prompt says 'extract the total' without distinguishing gross and net amounts. Which mechanism should be selected?
- State the target ISO date format and how uncertain dates must be handled
- Require page or span references for important extracted fields
- Define a shared field glossary and mapping rules before generation
- Define total, subtotal, tax, and discount semantics with examples
Explanation
Correct Answer
D:Financial field names need precise meanings; otherwise valid-looking numbers can be assigned to the wrong ledger fields.
Incorrect Answers
A:This measure fits a different trigger: extracted dates sometimes use locale-dependent shorthand. In that setting, Formatting criteria prevent ambiguous month/day interpretations and make downstream type checks meaningful; it does not resolve the present need to remove field-definition ambiguity.
B:Evidence-linked extraction allows downstream review to inspect the actual text behind uncertain or disputed values; that applies when a reviewer needs a confidence explanation tied to source text, whereas this case requires a response to the prompt says 'extract the total' without distinguishing gross and net amounts.
C:A stable schema prevents downstream systems from interpreting identical content under inconsistent attribute names; it protects against the case where the same invoice is processed by multiple teams with different field naming, rather than the failure described here: the prompt says 'extract the total' without distinguishing gross and net amounts.
Question 110
A document-processing agent invokes external services while extracting invoice fields. An extraction workflow repeats one expensive tool call after a transient error. What should be implemented at the appropriate boundary?
- Validate tool-call inputs against the declared argument schema
- Track pending work in durable application state until the actual result arrives
- Validate tool output against the expected result contract before reasoning
- Gate the payment tool behind authorization and confirmation before execution
- Apply a retry cap and bounded backoff outside the model
Explanation
Correct Answer
E:An application-owned retry policy prevents infinite loops and makes downstream reliability predictable under outages.
Incorrect Answers
A:Schema checking at the host boundary prevents type errors and unsafe side effects from malformed model-generated arguments; it protects against the case where a tool schema requires a numeric invoice total but Claude supplies a string, rather than the failure described here: an extraction workflow repeats one expensive tool call after a transient error.
B:A long-running call must not be represented as success before completion, especially where later steps depend on its output; that applies when tool execution takes several minutes, but the model has already emitted the request, whereas this case requires a response to an extraction workflow repeats one expensive tool call after a transient error.
C:This measure fits a different trigger: the OCR service sometimes returns an empty string rather than recognized text. In that setting, An empty result may reflect OCR failure, not an intentionally blank invoice field; validation stops it being promoted to fact; it does not resolve the present need to bound repeated recovery attempts.
D:Prompt wording alone is not a reliable transaction guard; the execution layer must verify that the action is approved; this is useful for a payment API can create a real charge, but model responses may be replayed, but it leaves the stated requirement to bound repeated recovery attempts unmet.