Question 290
A research agent must explore conflicting hypotheses with limited resources. An answer requires independently checking both supportive and contradictory evidence. Which approach satisfies the stated constraint?
- Stop additional investigation once evidence suffices and obligations are satisfied
- Track completed task intents and reuse valid existing findings
- Allow a bounded agent loop to generate follow-ups from validated findings
- Enumerate documents and allocate bounded extraction tasks to each
- Assign explicit confirmation and challenge tasks before the final synthesis
Explanation
Correct Answer
E:Separate search objectives reduce confirmation bias and give the coordinator grounds to compare conflicting material.
Incorrect Answers
A:When an expensive analysis path has low expected value after a reliable answer is found, this would be useful because a clear sufficiency condition avoids waste while preserving any mandatory validation or approval steps; this item instead calls for a way to decompose by opposing evidentiary roles.
B:This measure fits a different trigger: the coordinator keeps asking new workers for the same question. In that setting, Deduplicating work prevents an apparent multi-agent design from simply repeating the same investigation; it does not resolve the present need to decompose by opposing evidentiary roles.
C:Uncertain discovery benefits from adaptive next steps; the budget and tools still require host control; the alternative would make sense if an initial article may reveal unknown organizations that require follow-up queries. It does not directly fix the observed condition: an answer requires independently checking both supportive and contradictory evidence.
D:A finite inventory can be processed predictably without an autonomous planner deciding what to look at next; the relevant precondition would be the search space has a fixed list of ten known documents. The question instead describes an answer requires independently checking both supportive and contradictory evidence.
Question 291
An invoice-extraction team builds reliable prompting for standardized records. A document is missing a purchase-order number. Which mechanism should be selected?
- Define a shared field glossary and mapping rules before generation
- State the target ISO date format and how uncertain dates must be handled
- Require a null or explicit missing status instead of an invented identifier
- Define total, subtotal, tax, and discount semantics with examples
Explanation
Correct Answer
C:Missing fields should remain missing in the structured output; completeness must not be achieved by hallucinating values.
Incorrect Answers
A:When the same invoice is processed by multiple teams with different field naming, this would be useful because a stable schema prevents downstream systems from interpreting identical content under inconsistent attribute names; this item instead calls for a way to specify behavior for absent data.
B:Formatting criteria prevent ambiguous month/day interpretations and make downstream type checks meaningful; the relevant precondition would be extracted dates sometimes use locale-dependent shorthand. The question instead describes a document is missing a purchase-order number.
D:Financial field names need precise meanings; otherwise valid-looking numbers can be assigned to the wrong ledger fields; the alternative would make sense if the prompt says 'extract the total' without distinguishing gross and net amounts. It does not directly fix the observed condition: a document is missing a purchase-order number.
Question 292
An engineering assistant uses tool wrappers to standardize behavior. A service wraps raw exception traces containing internal hostnames. What should be implemented at the appropriate boundary?
- Check expected test coverage or completion markers in addition to the exit code
- Normalize both responses to a common file-and-line reference schema
- Convert exceptions into safe structured error categories with diagnostic IDs
- Deny mutation tools while the workflow is in the read-only discovery phase
Explanation
Correct Answer
C:Sanitized classifications help Claude choose recovery while retaining detailed traces in restricted operational logs.
Incorrect Answers
A:A zero exit status alone may not prove required checks ran; outcome validation should match the acceptance criteria; the alternative would make sense if a test runner returns a success exit code but logs an incomplete test suite. It does not directly fix the observed condition: a service wraps raw exception traces containing internal hostnames.
B:Common locations make evidence comparable and simplify provenance preservation across different retrieval implementations; the relevant precondition would be two code-search tools return incompatible source-location formats. The question instead describes a service wraps raw exception traces containing internal hostnames.
D:When a request policy allows read operations but forbids writes during discovery, this would be useful because phase-based permissions ensure exploration cannot silently become execution before an explicit workflow transition; this item instead calls for a way to avoid exposing sensitive internals in agent-facing errors.
Question 293
A support-orchestration service decides how to pass tasks between specialists. A specialist rejects an input because it lacks a case identifier. Which option best meets the operational need?
- Require both verified prerequisite states before dispatching the dependent worker
- Validate required fields before invoking the specialist
- Select a named specialist based on intent and permission boundaries
- Treat the unrecognized status as invalid and request clarification or manual review
Explanation
Correct Answer
B:Input checks at the coordinator boundary reduce wasted agent turns and expose missing fields early. For the stated case, the check is whether the system can correct the upstream handoff contract; this approach supplies that control.
Incorrect Answers
A:A conjunction of prerequisites prevents the next stage from treating one successful check as equivalent to full authorization; the alternative would make sense if a task needs both a billing result and an identity confirmation. It does not directly fix the observed condition: a specialist rejects an input because it lacks a case identifier.
C:An explicit dispatch decision links a validated customer need to a worker with relevant expertise and tool access; the relevant precondition would be a customer intent is classified, but no worker has been chosen. The question instead describes a specialist rejects an input because it lacks a case identifier.
D:This measure fits a different trigger: a delegated task completes but its result schema has an unknown status. In that setting, A closed status enumeration prevents unfamiliar values from accidentally being treated as success; it does not resolve the present need to correct the upstream handoff contract.
Question 294
A multi-agent research controller launches short-lived specialists. A worker is likely to call an expensive external tool excessively. What is the most appropriate design choice?
- Use a credential broker or application-side authorization rather than giving secrets in prompts
- Require status, result, and unresolved-work fields in each worker handoff
- Set agent-level execution limits and monitor per-task consumption
- Pass a curated task brief and the approved evidence only
Explanation
Correct Answer
C:Budget limits stop a narrow delegated task from silently exhausting the resources allocated to the entire orchestration.
Incorrect Answers
A:When an autonomous worker encounters an unexpected request for credentials, this would be useful because secrets placed in worker context are vulnerable to disclosure in logs or outputs; privileged access belongs in controlled service boundaries; this item instead calls for a way to bound resource use at the worker boundary.
B:This measure fits a different trigger: the coordinator cannot tell whether a worker finished or merely started searching. In that setting, A typed completion status allows the parent to distinguish finished evidence collection from a partial exploratory result; it does not resolve the present need to bound resource use at the worker boundary.
D:Specialized workers benefit from an explicit information boundary; inherited unrelated history can confuse task scope and expose sensitive data; the alternative would make sense if a writing specialist receives the entire private search history, including unrelated leads. It does not directly fix the observed condition: a worker is likely to call an expensive external tool excessively.
Question 295
A team wants repeatable Claude Code workflows for contributors. An individual uses a private note-cleanup command in many projects. Which response is most reliable?
- Put the command in the user's personal Claude Code command scope
- Package the instructions and supporting resources as a Claude Code Skill
- Design the command to accept and validate a module argument
- Create a project-scoped custom command with clear inputs and instructions
- Keep a concise skill overview and reference supplemental files as needed
Explanation
Correct Answer
A:User-level commands support individual workflow shortcuts without adding unapproved tasks to team configuration. This matches the workflow goal to keep personal automation outside shared repos rather than introducing an unrelated action.
Incorrect Answers
B:Skills can encapsulate specialized procedures with descriptions that support appropriate discovery and reuse; the alternative would make sense if a repository has a capability that Claude should discover when task context matches. It does not directly fix the observed condition: an individual uses a private note-cleanup command in many projects.
C:This measure fits a different trigger: a command needs a target module supplied by the developer. In that setting, Parameterized workflows remain reusable while tying file operations to a caller-specified scope instead of assuming a default; it does not resolve the present need to keep personal automation outside shared repos.
D:A named command makes an explicit routine easy to invoke consistently without embedding the same instructions in every chat; the relevant precondition would be developers repeatedly invoke a fixed changelog-generation routine by name. The question instead describes an individual uses a private note-cleanup command in many projects.
E:When a skill includes several bulky examples rarely needed for selection, this would be useful because progressive disclosure preserves context while still allowing detailed procedures to be consulted for the actual task; this item instead calls for a way to keep personal automation outside shared repos.
Question 296
A customer-service assistant may hand tasks to billing, returns, and policy specialists. A policy specialist can answer without any payment-system access. What should the team do to resolve this particular gap?
- Configure only the needed read-only policy tools for that specialist
- Check the current case state and ownership before starting an escalated job
- Pass narrowly scoped task context and redact irrelevant customer information
- Assign one authorized mutation owner and separate advisory from execution roles
Explanation
Correct Answer
A:Least-privilege tool access prevents a policy task from accidentally or maliciously exercising financial operations.
Incorrect Answers
B:When an escalation specialist is assigned a case that has already been resolved, this would be useful because state validation at handoff keeps asynchronous specialists from acting on superseded requests or producing redundant outcomes; this item instead calls for a way to restrict the policy worker's tools.
C:A smaller context packet reduces leakage and helps a specialist focus on the authorized decision instead of broad account history; the relevant precondition would be each specialist should see only the customer details it needs. The question instead describes a policy specialist can answer without any payment-system access.
D:A clear action boundary prevents double credits; two autonomous agents should not both be able to commit the same transaction; the alternative would make sense if billing and returns specialists could both initiate credits on the same order. It does not directly fix the observed condition: a policy specialist can answer without any payment-system access.
Question 297
A support assistant assigns risk and confidence to proposed customer actions. Low-risk policy responses need ongoing quality monitoring, but reviewing every response is overwhelming the support team. Which control is most directly relevant?
- Compare confidence buckets against observed correctness and adjust routing thresholds
- Route the transaction through the mandatory human approval gate
- Require actual policy checks and relevant source fields before approving action
- Audit a representative sample of routine resolutions while reviewing high-risk exceptions individually
Explanation
Correct Answer
D:Risk-stratified sampling gives reviewers evidence of routine decision quality without making every low-risk response wait for approval; mandatory high-risk gates remain in place.
Incorrect Answers
A:When monitoring shows confident unsupported answers increasing after a prompt change, this would be useful because reliability requires empirical error measurement; a fluent explanation is not proof that reported certainty matches accuracy; this item instead calls for a way to monitor routine decisions with risk-based sampling.
B:This measure fits a different trigger: a high-impact refund crosses a configured approval threshold. In that setting, The threshold is an execution policy independent of the model's expressed confidence about the refund; it does not resolve the present need to monitor routine decisions with risk-based sampling.
C:Confidence scores are not evidence; external authorization and validated facts determine whether a sensitive operation may proceed; the relevant precondition would be a high-confidence model verdict has no linked eligibility evidence. The question instead describes low-risk policy responses need ongoing quality monitoring, but reviewing every response is overwhelming the support team.
Question 298
A multi-agent developer assistant manages long-running refactoring tasks. A compaction step drops the list of migration prerequisites. How should the workflow be adjusted?
- Keep a checklist of prerequisites and blockers in the compacted handoff
- Mark stale notes superseded and record the new source revision
- Require entries keyed by task, file path, and evidence status
- Pass a summary with linked files, decisions, and unresolved questions
Explanation
Correct Answer
A:Losing a prerequisite can cause later stages to execute prematurely even when the prose summary appears coherent. For the stated case, the check is whether the system can preserve dependency state as mandatory context; this approach supplies that control.
Incorrect Answers
B:When an old scratchpad conflicts with an authoritative code search performed today, this would be useful because scratchpads are working memory, not authority; current repository evidence must win over obsolete summaries; this item instead calls for a way to preserve dependency state as mandatory context.
C:A consistent scratchpad makes cross-worker discoveries retrievable and reduces conflicting or orphaned notes; the relevant precondition would be multiple workers create unrelated notes with no common file identifiers. The question instead describes a compaction step drops the list of migration prerequisites.
D:This measure fits a different trigger: a worker wants to reuse another agent's whole transcript as context. In that setting, Raw transcripts contain irrelevant exploration and private context; scoped artifacts support collaboration more efficiently; it does not resolve the present need to preserve dependency state as mandatory context.
Question 299
A Claude Code assistant supports an engineering team during feature development. A new utility has no tests and several tricky null-handling cases. Which implementation decision is the best fit?
- Inspect the failed assertion and revise only the mismatched logic
- Reference nearby implementations and conventions while specifying differences
- Use a structured requirement interview covering behavior and constraints
- Create cases for missing, empty, and malformed inputs before coding
Explanation
Correct Answer
D:Explicit edge-case tests make the expected semantics observable and prevent silent incorrect defaults. For the stated case, the check is whether the system can define tests around boundary behavior first; this approach supplies that control.
Incorrect Answers
A:This measure fits a different trigger: the first implementation fails a specific assertion in continuous integration. In that setting, Failure traces narrow the search space and provide stronger evidence than asking the model to try again generally; it does not resolve the present need to define tests around boundary behavior first.
B:Real repository examples anchor the solution in established architecture without forcing the model to invent project-specific patterns; the alternative would make sense if a developer wants generated code to conform to existing examples. It does not directly fix the observed condition: a new utility has no tests and several tricky null-handling cases.
C:Clarifying choices reduces wasted implementation iterations and ensures stakeholders own product decisions; the relevant precondition would be the request has several plausible interpretations of the user experience. The question instead describes a new utility has no tests and several tricky null-handling cases.
Question 300
An organization wants scoped Claude Code instructions without huge root prompts. Documentation files use a distinct formatting standard. What should the architect specify in the design?
- Apply documentation rules only to matching Markdown paths
- Define a rule for generated paths that points to the generator command
- Create a dedicated rule for migration directories and file patterns
- Target only the legacy module rather than the repository root
- Enforce secret scanning in CI for the affected files
Explanation
Correct Answer
A:File targeting communicates when a doc-specific tool is relevant and prevents it displacing source-code tests. Here it serves the explicit need to scope document lint conventions without adding a separate unverified inference.
Incorrect Answers
B:When a generated file is matched, Claude should change the generator input rather than apply a patch that will be overwritten; the alternative would make sense if generated source files should not be edited by hand. It does not directly fix the observed condition: documentation files use a distinct formatting standard.
C:Targeted rules add critical checks when touching migrations without burdening unrelated UI tasks; the relevant precondition would be database migration files need extra review beyond normal code. The question instead describes documentation files use a distinct formatting standard.
D:This measure fits a different trigger: a rule is needed only for a deprecated module kept for compatibility. In that setting, A narrow rule preserves compatibility requirements without imposing obsolete practices on active packages; it does not resolve the present need to scope document lint conventions.
E:When developers accidentally commit secrets in test-fixture paths, this would be useful because path-specific instructions may remind Claude, but only a scanner or policy gate reliably blocks forbidden content before merge; this item instead calls for a way to scope document lint conventions.