Question 180
A research pipeline asks Claude to emit machine-readable evidence records. The model invents unrecognized status strings such as 'sort-of-verified'. Which control is most directly relevant?
- Use a list of claim objects, each with its own source references and stance
- Check source IDs against the approved evidence registry after parsing
- Use an enum for allowed verification statuses
- Allow a conditional locator such as a page or URL fragment as appropriate
- Define source_id and publication_date as required schema properties
Explanation
Correct Answer
C:Enumerated values make downstream control flow predictable and prevent speculative status text from being treated as a recognized gate.
Incorrect Answers
A:Structured claim-level provenance prevents competing interpretations from being collapsed into one misleading free-text conclusion; that applies when results need to preserve multiple contradictory claims from one source set, whereas this case requires a response to the model invents unrecognized status strings such as 'sort-of-verified'.
B:JSON Schema checks shape and types, not whether a purported reference actually exists or supports the claim; it protects against the case where a tool-call payload satisfies syntax but cites an unknown document ID, rather than the failure described here: the model invents unrecognized status strings such as 'sort-of-verified'.
D:The schema should reflect source-type differences; forcing a PDF page number for HTML would create meaningless metadata; this is useful for some sources have no stable page number because they are HTML, but it leaves the stated requirement to restrict outputs to approved states unmet.
E:This measure fits a different trigger: a citation must include both source ID and publication date. In that setting, Required fields expose missing citation metadata early instead of allowing evidence records that cannot later be traced; it does not resolve the present need to restrict outputs to approved states.
Question 181
A Claude Code team audits the quality of its persistent project instructions. Two instruction files issue contradictory formatting requirements. How should the workflow be adjusted?
- Resolve the conflict and express one authoritative formatting rule
- Document the actual lint, test, and review procedures with relevant paths
- Enforce the gate in CI or permission policy, while keeping guidance aligned
- Replace the secret with a safe placeholder and managed-secret guidance
Explanation
Correct Answer
A:Conflicting directives can produce nondeterministic edits; a clear standard prevents wasted patch iterations. The relevant requirement is to make instructions consistent across loaded scopes, and this measure operates at that decision point.
Incorrect Answers
B:This measure fits a different trigger: CLAUDE.md contains vague advice to 'write good code' but omits repository commands. In that setting, Specific commands and expected outcomes give Claude verifiable steps; broad style slogans offer little operational guidance; it does not resolve the present need to make instructions consistent across loaded scopes.
C:Prompt instructions are not an authoritative security boundary; a required check should fail independently of the assistant's compliance; it protects against the case where one developer asks Claude Code to ignore a required security gate for speed, rather than the failure described here: two instruction files issue contradictory formatting requirements.
D:Persistent instructions may be read by agents and committed to version control; secrets do not belong in them; this is useful for a temporary secret appears in a copied setup example, but it leaves the stated requirement to make instructions consistent across loaded scopes unmet.
Question 182
A Claude Agent SDK application maintains long-running support sessions. A supervisor wants an independent second assessment without overwriting the original. Which implementation decision is the best fit?
- Store session identifiers and required checkpoints in a durable backing store
- Use the saved session identity and recover relevant persisted messages
- Create a fresh session scoped to the new customer's identity
- Fork the session for a separate review path
Explanation
Correct Answer
D:A fork preserves a common starting context while allowing a different conclusion or investigation without corrupting the original trail.
Incorrect Answers
A:Recoverable state allows orchestration to continue after host failure, unlike in-memory variables lost on restart; it protects against the case where a long-running session needs to survive application restarts, rather than the failure described here: a supervisor wants an independent second assessment without overwriting the original.
B:This measure fits a different trigger: a returning customer asks about a previously paused case with the same conversation state. In that setting, Resumption preserves continuity for the same case, provided the application verifies authorization and current account state; it does not resolve the present need to branch an existing analytical session.
C:A new identity requires isolated conversation state; reusing a previous customer's session can disclose private history; this is useful for a support case is closed, and a new unrelated customer starts a chat, but it leaves the stated requirement to branch an existing analytical session unmet.
Question 183
A Claude Code automation project uses lifecycle hooks for deterministic behavior. A shell command would write to a protected production directory. What should the architect specify in the design?
- Capture the subagent lifecycle completion event for orchestration tracking
- Run the targeted test through an appropriate post-tool hook or workflow stage
- Use session initialization to provide relevant instructions or environment facts
- Check command and path policy through a pre-tool validation hook
Explanation
Correct Answer
D:Pre-execution enforcement can stop the command before any files are changed; post-execution review would be too late.
Incorrect Answers
A:A completion event is the right place to record the specialist's result without confusing it with the parent agent's final turn; that applies when a subagent finishes a task, and its completion status must be recorded centrally, whereas this case requires a response to a shell command would write to a protected production directory.
B:This measure fits a different trigger: a test command must run after a source-editing tool successfully changes code. In that setting, The validation is bound to the actual modification event, not to whether Claude remembers a reminder at the end of the conversation; it does not resolve the present need to block the risky command before it starts.
C:Start-of-session hooks can make standard setup repeatable rather than relying on each developer to manually paste conventions; this is useful for a session needs to load its approved repository-specific working conventions, but it leaves the stated requirement to block the risky command before it starts unmet.
Question 184
A monorepo uses different coding guidelines for backend and frontend files. Python services require an alternate unit-test command. Which change most directly addresses this condition?
- Keep the common style principle in root project instructions
- Scope the testing guidance to Python service paths
- Correct the rule's glob or path targeting to match actual edited files
- Create a path-scoped rule targeting the web source patterns
Explanation
Correct Answer
B:A service-specific rule prevents Claude from running a frontend command on an unrelated backend change. The relevant requirement is to target the rule to the service's source tree, and this measure operates at that decision point.
Incorrect Answers
A:Shared behavior should have one clear home rather than several overlapping path rules that can contradict one another; this is useful for a global style rule applies to every source file in the repository, but it leaves the stated requirement to target the rule to the service's source tree unmet.
C:Path-scoped rules depend on matching paths; the model cannot follow instructions that the configuration never selects; that applies when a rule never loads because its path pattern misses nested packages, whereas this case requires a response to python services require an alternate unit-test command.
D:This measure fits a different trigger: typeScript files under web/ require browser-specific linting rules. In that setting, Path-specific guidance appears for relevant work instead of affecting backend files that use different tooling; it does not resolve the present need to target the rule to the service's source tree.
Question 185
A document-processing architecture decides between online calls and batch jobs. A cashier needs a tax calculation before finishing the same transaction. What is the most defensible next step?
- Compute field-level error metrics by input cohort and workflow version
- Maintain stable item IDs and a durable submission ledger
- Use batch requests with durable tracking and completion monitoring
- Mark uncertain items for separate human adjudication while preserving successful outputs
- Invoke the model synchronously with bounded timeout and fallback
Explanation
Correct Answer
E:A transaction depends on the output now; asynchronous batch scheduling would not satisfy the immediate completion dependency.
Incorrect Answers
A:Aggregate success status does not prove accuracy; scored examples reveal changes in extraction behavior over time; it protects against the case where the team wants to know whether extraction quality changes over several nightly runs, rather than the failure described here: a cashier needs a tax calculation before finishing the same transaction.
B:A replay-safe manifest distinguishes outstanding items from completed or already submitted work and prevents accidental duplicate processing; this is useful for a batch worker may retry failed items after network interruption, but it leaves the stated requirement to use an online call for a synchronous dependency unmet.
C:This measure fits a different trigger: a nightly backlog consists of independent invoices due by the next morning. In that setting, The deadline tolerates deferred execution and requests are independent, making batch orchestration a suitable operational pattern; it does not resolve the present need to use an online call for a synchronous dependency.
D:Partial automation can still be useful, but the pipeline must not pretend every item met the same confidence threshold; that applies when a large job contains some documents that require human review, whereas this case requires a response to a cashier needs a tax calculation before finishing the same transaction.
Question 186
A customer-support assistant must decide when to request human assistance. The user provides conflicting account ownership details. Which approach satisfies the stated constraint?
- Mark the policy gap and hand off to an authorized human
- Pause account changes and request approved verification or support review
- Apply the verified rule within delegated permission and record the decision
- Trigger the organization's urgent human handoff process
Explanation
Correct Answer
B:Conflicting identity evidence makes a mutation unsafe; a fluent guessed choice is not a substitute for authentication.
Incorrect Answers
A:This measure fits a different trigger: a request falls outside every published returns-policy category. In that setting, The model should not create a new rule for an unaddressed case; a documented gap requires accountable policy interpretation; it does not resolve the present need to resolve identity ambiguity before sensitive operations.
C:Human review should be focused on risk or uncertainty; routine well-defined cases can proceed under controlled authorization; it protects against the case where a support specialist finds the policy clear and customer eligibility already verified, rather than the failure described here: the user provides conflicting account ownership details.
D:High-impact, ambiguous reports warrant a trained responder and documented procedure rather than an autonomous improvised resolution; that applies when a customer reports urgent harm that the assistant cannot safely assess, whereas this case requires a response to the user provides conflicting account ownership details.
Question 187
A multi-agent developer assistant manages long-running refactoring tasks. The context summary says 'tests passed' but omits which revision was tested. Which mechanism should be selected?
- Require entries keyed by task, file path, and evidence status
- Keep a checklist of prerequisites and blockers in the compacted handoff
- Pass a summary with linked files, decisions, and unresolved questions
- Record the commit or diff identifier with each test result
Explanation
Correct Answer
D:A green status without a revision cannot establish validity after further edits; provenance is necessary for trustworthy continuation.
Incorrect Answers
A:This measure fits a different trigger: multiple workers create unrelated notes with no common file identifiers. In that setting, A consistent scratchpad makes cross-worker discoveries retrievable and reduces conflicting or orphaned notes; it does not resolve the present need to bind verification to code state.
B:Losing a prerequisite can cause later stages to execute prematurely even when the prose summary appears coherent; this is useful for a compaction step drops the list of migration prerequisites, but it leaves the stated requirement to bind verification to code state unmet.
C:Raw transcripts contain irrelevant exploration and private context; scoped artifacts support collaboration more efficiently; that applies when a worker wants to reuse another agent's whole transcript as context, whereas this case requires a response to the context summary says 'tests passed' but omits which revision was tested.
Question 188
A repository assistant uses several parallel agents to examine unfamiliar services. A search agent finishes with fifty raw file excerpts. What should be implemented at the appropriate boundary?
- Partition write ownership or serialize changes to the shared file
- Return a concise file-indexed summary and paths to relevant excerpts
- Limit task nesting and keep coordination responsibility at the parent
- State the expected test command and success condition in the delegated task
Explanation
Correct Answer
B:A narrow handoff saves parent context while retaining references that can be reopened when deeper inspection is needed.
Incorrect Answers
A:This measure fits a different trigger: two agents intend to edit the same config file concurrently. In that setting, Parallel reads may be safe, but simultaneous edits to shared state invite races and difficult-to-merge patches; it does not resolve the present need to compress findings without dropping essential evidence.
C:Unbounded subagent spawning increases cost and makes failure ownership obscure; a bounded hierarchy is more predictable; that applies when an analysis worker stalls after requesting another worker recursively, whereas this case requires a response to a search agent finishes with fifty raw file excerpts.
D:A specialist with explicit verification criteria can return evidence of completion instead of an untested code suggestion; this is useful for a worker must verify that its proposed fix passes a particular unit test, but it leaves the stated requirement to compress findings without dropping essential evidence unmet.
Question 189
A customer-service assistant may hand tasks to billing, returns, and policy specialists. Billing and returns specialists could both initiate credits on the same order. Which option best meets the operational need?
- Assign one authorized mutation owner and separate advisory from execution roles
- Make identity verification an explicit prerequisite in the coordinator workflow
- Pass narrowly scoped task context and redact irrelevant customer information
- Check the current case state and ownership before starting an escalated job
Explanation
Correct Answer
A:A clear action boundary prevents double credits; two autonomous agents should not both be able to commit the same transaction.
Incorrect Answers
B:A worker should not process a customer-specific return against an unverified identity; graph ordering enforces the prerequisite; that applies when a returns worker needs a decision made by the identity-verification worker, whereas this case requires a response to billing and returns specialists could both initiate credits on the same order.
C:This measure fits a different trigger: each specialist should see only the customer details it needs. In that setting, A smaller context packet reduces leakage and helps a specialist focus on the authorized decision instead of broad account history; it does not resolve the present need to avoid overlapping ownership of refunds.
D:State validation at handoff keeps asynchronous specialists from acting on superseded requests or producing redundant outcomes; it protects against the case where an escalation specialist is assigned a case that has already been resolved, rather than the failure described here: billing and returns specialists could both initiate credits on the same order.
Question 190
A Claude Code team shares MCP connections across several repositories. A developer uses the same safe personal reference server across many projects. What is the most appropriate design choice?
- Store the connection in the supported project-scoped configuration
- Verify each effective user, project, and local configuration layer
- Use a user-scoped MCP configuration for the reusable personal connection
- Audit server provenance, tool definitions, and permission prompts before enablement
- Inject the secret through a managed environment or credential store
Explanation
Correct Answer
C:User scope supports broadly useful tooling without copying the connection into every repository. Here it serves the explicit need to make the server available in the user's environment without adding a separate unverified inference.
Incorrect Answers
A:This measure fits a different trigger: a repository requires a custom issue tracker MCP server not needed anywhere else. In that setting, A project-level definition keeps repo-specific capabilities with the project instead of exposing them to unrelated workspaces; it does not resolve the present need to make the server available in the user's environment.
B:Effective tool availability can differ when local overrides or older definitions remain; inspecting the active scope resolves the discrepancy; it protects against the case where a team updates server configuration but different developers still see inconsistent tools, rather than the failure described here: a developer uses the same safe personal reference server across many projects.
D:External servers can expose surprising side effects or injected descriptions; installation is not authorization for every capability; that applies when a new MCP server exposes a tool that should not be trusted automatically, whereas this case requires a response to a developer uses the same safe personal reference server across many projects.
E:Project configuration can be shared and reviewed, but credentials belong in protected storage rather than plaintext repository files; this is useful for a secret API token is needed by a configured MCP server, but it leaves the stated requirement to make the server available in the user's environment unmet.