Question 530
The release checklist for a service-credit approval assistant explicitly checks that persistent ambiguous data receives human review; it also checks that a classifier avoids marking uncertain cases as confirmed violations. What coordinated solution meets the checklist?
- keep retrying until the model finally emits something that passes; and tell the model to flag anything that sounds suspicious
- keep retrying until the model finally emits something that passes; and define explicit positive evidence and an abstain or review category
- stop after defined retries and route unresolved cases to a reviewer; and define explicit positive evidence and an abstain or review category
- implement only stop after defined retries and route unresolved cases to a reviewer; make no corresponding change for the second requirement
- stop after defined retries and route unresolved cases to a reviewer; and tell the model to flag anything that sounds suspicious
Explanation
Correct Answer
C:In a service-credit approval assistant, a bounded escalation path prevents infinite loops and invented resolutions; alongside this, clear decision thresholds separate direct evidence from weak similarity, satisfying the distinct requirements that persistent ambiguous data receives human review and that a classifier avoids marking uncertain cases as confirmed violations.
Incorrect Answers
A:In a service-credit approval assistant, unlimited retries waste resources and can reinforce guesses and vague semantic similarity raises false positives; the design would fail both conditions: persistent ambiguous data receives human review and a classifier avoids marking uncertain cases as confirmed violations.
B:In a service-credit approval assistant, clear decision thresholds separate direct evidence from weak similarity, but unlimited retries waste resources and can reinforce guesses; therefore the separate requirement that persistent ambiguous data receives human review would remain unsatisfied.
D:In a service-credit approval assistant, a bounded escalation path prevents infinite loops and invented resolutions, but the independent mechanism for the other criterion is absent: clear decision thresholds separate direct evidence from weak similarity; as written, the design does not ensure that a classifier avoids marking uncertain cases as confirmed violations.
E:In a service-credit approval assistant, a bounded escalation path prevents infinite loops and invented resolutions, but vague semantic similarity raises false positives; therefore the separate requirement that a classifier avoids marking uncertain cases as confirmed violations would remain unsatisfied.
Question 531
An architecture review of a code-reference retrieval assistant finds two missing guarantees: a selector accepts only supported operation names; conflicting subagent findings produce one accountable interpretation. What two-part change closes both gaps?
- ask the model to invent a suitable action string; and let the fastest subagent override other findings automatically
- declare an operation enum in the schema and reject values outside it in the tool handler; and let the fastest subagent override other findings automatically
- declare an operation enum in the schema and reject values outside it in the tool handler; and have the coordinator compare claims and sources before synthesis
- ask the model to invent a suitable action string; and have the coordinator compare claims and sources before synthesis
Explanation
Correct Answer
C:In a code-reference retrieval assistant, schema constraints guide valid selections and runtime validation blocks unsupported operation values; alongside this, central reconciliation can distinguish evidence disagreement from a formatting difference, satisfying the distinct requirements that a selector accepts only supported operation names and that conflicting subagent findings produce one accountable interpretation.
Incorrect Answers
A:In a code-reference retrieval assistant, free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist and completion order is not a sound evidence-ranking rule; the design would fail both conditions: a selector accepts only supported operation names and conflicting subagent findings produce one accountable interpretation.
B:In a code-reference retrieval assistant, schema constraints guide valid selections and runtime validation blocks unsupported operation values, but completion order is not a sound evidence-ranking rule; therefore the separate requirement that conflicting subagent findings produce one accountable interpretation would remain unsatisfied.
D:In a code-reference retrieval assistant, central reconciliation can distinguish evidence disagreement from a formatting difference, but free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist; therefore the separate requirement that a selector accepts only supported operation names would remain unsatisfied.
Question 532
Before expanding an order-cancellation service, the owner must demonstrate that invalid parameters lead to a clear correction rather than a blind retry, while also demonstrating that only one approved write tool is callable in a sensitive stage. Which design provides both controls?
- return a non-retryable validation error with the field and expected constraint; and let the model select from a broad global list of tools
- hide the invalid field behind a generic internal-error message; and restrict the stage's allowed tool set and verify permissions in the executor
- hide the invalid field behind a generic internal-error message; and let the model select from a broad global list of tools
- return a non-retryable validation error with the field and expected constraint; and restrict the stage's allowed tool set and verify permissions in the executor
Explanation
Correct Answer
D:In an order-cancellation service, field-specific feedback lets the caller fix the input before resubmission; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that invalid parameters lead to a clear correction rather than a blind retry and that only one approved write tool is callable in a sensitive stage.
Incorrect Answers
A:In an order-cancellation service, field-specific feedback lets the caller fix the input before resubmission, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.
B:In an order-cancellation service, capability scoping narrows possible side effects before model selection, but the client lacks the information needed to repair the request; therefore the separate requirement that invalid parameters lead to a clear correction rather than a blind retry would remain unsatisfied.
C:In an order-cancellation service, the client lacks the information needed to repair the request and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: invalid parameters lead to a clear correction rather than a blind retry and only one approved write tool is callable in a sensitive stage.
Question 533
Tests for a compliance interpretation research team will pass only if extracted records are labeled only when required fields agree and if multiple draft branches are merged without contradictory statements. Which proposed design directly satisfies both checks?
- state the conjunction of required matching conditions; and create a reconciliation stage that checks citations and resolves overlaps
- classify as a match when any one keyword overlaps; and create a reconciliation stage that checks citations and resolves overlaps
- classify as a match when any one keyword overlaps; and concatenate every agent's conclusion into the final report
- state the conjunction of required matching conditions; and concatenate every agent's conclusion into the final report
Explanation
Correct Answer
A:In a compliance interpretation research team, explicit multi-field criteria prevent a single suggestive field from dominating the outcome; alongside this, synthesis must select mutually consistent claims with defensible evidence, satisfying the distinct requirements that extracted records are labeled only when required fields agree and that multiple draft branches are merged without contradictory statements.
Incorrect Answers
B:In a compliance interpretation research team, synthesis must select mutually consistent claims with defensible evidence, but a shared keyword does not prove record identity; therefore the separate requirement that extracted records are labeled only when required fields agree would remain unsatisfied.
C:In a compliance interpretation research team, a shared keyword does not prove record identity and raw merger preserves disagreements and duplicated statements; the design would fail both conditions: extracted records are labeled only when required fields agree and multiple draft branches are merged without contradictory statements.
D:In a compliance interpretation research team, explicit multi-field criteria prevent a single suggestive field from dominating the outcome, but raw merger preserves disagreements and duplicated statements; therefore the separate requirement that multiple draft branches are merged without contradictory statements would remain unsatisfied.
Question 534
In a customer case-management agent, the engineering team must guarantee that fast-changing information is checked against its publication date. What is the most appropriate control?
- carry citation identifiers and retrieval context through synthesis
- label direct source facts separately from analytical conclusions
- reuse an old cached claim without its date
- record source timestamps and refresh time-sensitive evidence
Explanation
Correct Answer
D:For a customer case-management agent, freshness determines whether an otherwise credible fact applies now; this directly establishes that fast-changing information is checked against its publication date instead of relying on an unrelated workflow control.
Incorrect Answers
A: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 fast-changing information is checked against its publication date in a customer case-management agent.
B:Although distinguishing evidence from interpretation prevents inference being misattributed to a document, that only supports the distinct goal that a report separates documented findings from its own inference, not the requirement that fast-changing information is checked against its publication date in a customer case-management agent.
C:In a customer case-management agent, stale evidence may no longer describe the current state; as a result, the stated requirement that fast-changing information is checked against its publication date would still not be met.
Question 535
For a service-credit approval assistant, acceptance depends on demonstrating that a payment-changing action obtains explicit user authorization. Which approach is the strongest fit?
- confirm the intended action and scope before invoking the write
- set a clear evidence or confidence boundary and require review below it
- mark the inconsistency and request resolution or human verification
- treat a request for information as permission to mutate the account
- ask a focused clarifying question for the missing requirement
Explanation
Correct Answer
A:For a service-credit approval assistant, consent is specific to the side effect and cannot be inferred from a general inquiry; this directly establishes that a payment-changing action obtains explicit user authorization instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although risk-weighted gates limit autonomous actions when support is inadequate, that only supports the distinct goal that an uncertain high-impact decision is routed for review instead of automatic execution, not the requirement that a payment-changing action obtains explicit user authorization in a service-credit approval assistant.
C:Although conflicting source claims are a knowledge gap, not authorization to guess, that only supports the distinct goal that contradictory evidence is reviewed before action, not the requirement that a payment-changing action obtains explicit user authorization in a service-credit approval assistant.
D:In a service-credit approval assistant, asking a question does not approve a financial change; as a result, the stated requirement that a payment-changing action obtains explicit user authorization would still not be met.
E:Although targeted clarification supplies the decision input before selecting an irreversible action, that only supports the distinct goal that a support case missing an essential fact is not silently guessed, not the requirement that a payment-changing action obtains explicit user authorization in a service-credit approval assistant.
Question 536
Before expanding a merge-request policy gate, the owner must demonstrate that developers can explicitly invoke an established project procedure, while also demonstrating that API conventions apply only to source files under an API directory. Which design provides both controls?
- write undocumented one-off ad hoc prompts for each engineer; and add a .claude/rules file with paths matching the API subtree
- make the skill available under a recognizable slash invocation; and put API-specific formatting rules in always-on project guidance
- write undocumented one-off ad hoc prompts for each engineer; and put API-specific formatting rules in always-on project guidance
- make the skill available under a recognizable slash invocation; and add a .claude/rules file with paths matching the API subtree
Explanation
Correct Answer
D:In a merge-request policy gate, a discoverable workflow gives the team a consistent entry point for repetitive work; alongside this, path-scoped rules load when the target context matches, keeping unrelated tasks clean, satisfying the distinct requirements that developers can explicitly invoke an established project procedure and that API conventions apply only to source files under an API directory.
Incorrect Answers
A:In a merge-request policy gate, path-scoped rules load when the target context matches, keeping unrelated tasks clean, but unshared prompts make results hard to reproduce and review; therefore the separate requirement that developers can explicitly invoke an established project procedure would remain unsatisfied.
B:In a merge-request policy gate, a discoverable workflow gives the team a consistent entry point for repetitive work, 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.
C:In a merge-request policy gate, unshared prompts make results hard to reproduce and review and frontend and documentation tasks then receive irrelevant instructions; the design would fail both conditions: developers can explicitly invoke an established project procedure and API conventions apply only to source files under an API directory.
Question 537
An architecture review of a cross-platform application migration finds two missing guarantees: specialized agents work with only relevant permissions; secrets are not embedded in a shared MCP setup. What two-part change closes both gaps?
- define each subagent role and expose the minimum matching tools; and place long-lived access tokens directly in .mcp.json
- give every subagent the coordinator's complete tool inventory; and place long-lived access tokens directly in .mcp.json
- give every subagent the coordinator's complete tool inventory; and inject credentials through approved environment or secret-management mechanisms
- define each subagent role and expose the minimum matching tools; and inject credentials through approved environment or secret-management mechanisms
Explanation
Correct Answer
D:In a cross-platform application migration, tool scoping shrinks both decision confusion and the blast radius of delegated actions; alongside this, separating credentials from versioned configuration limits accidental disclosure, satisfying the distinct requirements that specialized agents work with only relevant permissions and that secrets are not embedded in a shared MCP setup.
Incorrect Answers
A:In a cross-platform application migration, tool scoping shrinks both decision confusion and the blast radius of delegated actions, but repository history can expose tokens to everyone with code access; therefore the separate requirement that secrets are not embedded in a shared MCP setup would remain unsatisfied.
B:In a cross-platform application migration, unneeded write or network tools expand risk without improving the specialist task and repository history can expose tokens to everyone with code access; the design would fail both conditions: specialized agents work with only relevant permissions and secrets are not embedded in a shared MCP setup.
C:In a cross-platform application migration, separating credentials from versioned configuration limits accidental disclosure, but unneeded write or network tools expand risk without improving the specialist task; therefore the separate requirement that specialized agents work with only relevant permissions would remain unsatisfied.
Question 538
Tests for a developer codebase exploration assistant will pass only if the assistant can use external service capabilities via MCP and if a conversational task does not invoke tools needlessly. Which proposed design directly satisfies both checks?
- describe the external API in a prompt without connecting any tool; and use automatic tool choice when a call is optional
- describe the external API in a prompt without connecting any tool; and force a tool on every message regardless of intent
- configure a compatible MCP server and expose its declared tools to the client; and force a tool on every message regardless of intent
- configure a compatible MCP server and expose its declared tools to the client; and use automatic tool choice when a call is optional
Explanation
Correct Answer
D:In a developer codebase exploration assistant, MCP bridges a client to provider-defined capabilities rather than inventing a Claude built-in; alongside this, auto allows the model to answer directly when no external side effect or fresh data is needed, satisfying the distinct requirements that the assistant can use external service capabilities via MCP and that a conversational task does not invoke tools needlessly.
Incorrect Answers
A:In a developer codebase exploration assistant, auto allows the model to answer directly when no external side effect or fresh data is needed, but instructions cannot create an executable integration endpoint; therefore the separate requirement that the assistant can use external service capabilities via MCP would remain unsatisfied.
B:In a developer codebase exploration assistant, instructions cannot create an executable integration endpoint and mandatory calls add latency and can invoke irrelevant operations; the design would fail both conditions: the assistant can use external service capabilities via MCP and a conversational task does not invoke tools needlessly.
C:In a developer codebase exploration assistant, MCP bridges a client to provider-defined capabilities rather than inventing a Claude built-in, 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.
Question 539
While preparing a monorepo testing overhaul for deployment, engineers must ensure that delegated investigations stay within bounded scope; they must also ensure that every high-impact tool invocation produces an audit event. Which combination best satisfies those requirements?
- ask every subagent to investigate everything it can find; and infer tool activity from the final natural-language answer
- implement only specify the question, allowed sources, expected output, and stopping criterion; make no corresponding change for the second requirement
- specify the question, allowed sources, expected output, and stopping criterion; and record the tool name, permitted inputs, outcome, and task identifier in a hook
- ask every subagent to investigate everything it can find; and record the tool name, permitted inputs, outcome, and task identifier in a hook
- specify the question, allowed sources, expected output, and stopping criterion; and infer tool activity from the final natural-language answer
Explanation
Correct Answer
C:In a monorepo testing overhaul, a task contract prevents specialist exploration from swallowing the coordinator's larger goal; alongside this, runtime instrumentation observes actual proposed or completed tool activity, satisfying the distinct requirements that delegated investigations stay within bounded scope and that every high-impact tool invocation produces an audit event.
Incorrect Answers
A:In a monorepo testing overhaul, unbounded exploration dilutes signal and inflates context and latency and a summary can omit failed calls or delegated actions; the design would fail both conditions: delegated investigations stay within bounded scope and every high-impact tool invocation produces an audit event.
B:In a monorepo testing overhaul, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but the independent mechanism for the other criterion is absent: runtime instrumentation observes actual proposed or completed tool activity; as written, the design does not ensure that every high-impact tool invocation produces an audit event.
D:In a monorepo testing overhaul, runtime instrumentation observes actual proposed or completed tool activity, but unbounded exploration dilutes signal and inflates context and latency; therefore the separate requirement that delegated investigations stay within bounded scope would remain unsatisfied.
E:In a monorepo testing overhaul, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but a summary can omit failed calls or delegated actions; therefore the separate requirement that every high-impact tool invocation produces an audit event would remain unsatisfied.
Question 540
A readiness review for a typed API generator project requires that test-specific naming conventions run only when touching test files; that an existing file receives a precise localized replacement; and that secrets are not embedded in a shared MCP setup. Which THREE actions directly implement those distinct requirements? Choose THREE.
- place long-lived access tokens directly in .mcp.json
- use Edit for an exact targeted change
- use a test-file glob in the rules frontmatter
- apply the same test naming rule to every source file
- overwrite the whole file with a newly generated copy
- inject credentials through approved environment or secret-management mechanisms
Explanation
Correct Answers
B:For a typed API generator project, surgical edits preserve unrelated lines and provide reviewable diffs, which directly establishes that an existing file receives a precise localized replacement; the separate requirement that secrets are not embedded in a shared MCP setup is handled by a different action.
C:For a typed API generator project, glob matching limits enforcement guidance to the intended file families, which directly establishes that test-specific naming conventions run only when touching test files; the separate requirement that an existing file receives a precise localized replacement is handled by a different action.
F:For a typed API generator project, separating credentials from versioned configuration limits accidental disclosure, which directly establishes that secrets are not embedded in a shared MCP setup; the separate requirement that test-specific naming conventions run only when touching test files is handled by a different action.
Incorrect Answers
A:For a typed API generator project, repository history can expose tokens to everyone with code access, so this option cannot establish that secrets are not embedded in a shared MCP setup; correctly addressing test-specific naming conventions run only when touching test files elsewhere does not repair that deficiency.
D:For a typed API generator project, production files and configuration do not share the test naming context, so this option cannot establish that test-specific naming conventions run only when touching test files; correctly addressing an existing file receives a precise localized replacement elsewhere does not repair that deficiency.
E:For a typed API generator project, full replacement risks losing unrelated code and formatting, so this option cannot establish that an existing file receives a precise localized replacement; correctly addressing secrets are not embedded in a shared MCP setup elsewhere does not repair that deficiency.