Question 300
When designing a policy document normalization service, the requirement is not satisfied unless example selection stays relevant to the current workload and a corrected attempt preserves a record of prior validation findings. Which implementation addresses the two independent conditions?
- use a compact sample covering common cases and one important edge case; and retain the original source, response version, and retry feedback
- include dozens of unrelated demonstrations from other domains; and retain the original source, response version, and retry feedback
- use a compact sample covering common cases and one important edge case; and replace all earlier outputs without recording the validation history
- include dozens of unrelated demonstrations from other domains; and replace all earlier outputs without recording the validation history
Explanation
Correct Answer
A:In a policy document normalization service, high-signal examples guide the task without overloading context; alongside this, traceable attempts allow auditors to distinguish correction from silent overwrite, satisfying the distinct requirements that example selection stays relevant to the current workload and that a corrected attempt preserves a record of prior validation findings.
Incorrect Answers
B:In a policy document normalization service, traceable attempts allow auditors to distinguish correction from silent overwrite, but irrelevant examples dilute the pattern and consume tokens; therefore the separate requirement that example selection stays relevant to the current workload would remain unsatisfied.
C:In a policy document normalization service, high-signal examples guide the task without overloading context, 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.
D:In a policy document normalization service, irrelevant examples dilute the pattern and consume tokens and the reason for a changed value becomes untraceable; the design would fail both conditions: example selection stays relevant to the current workload and a corrected attempt preserves a record of prior validation findings.
Question 301
An architecture review of a multi-repository troubleshooting agent finds two missing guarantees: specialized agents work with only relevant permissions; independent stages of a complex job run efficiently. What two-part change closes both gaps?
- define each subagent role and expose the minimum matching tools; and divide work along independent outputs and run those stages in parallel
- define each subagent role and expose the minimum matching tools; and split the job into an arbitrary fixed chain of agents
- give every subagent the coordinator's complete tool inventory; and split the job into an arbitrary fixed chain of agents
- give every subagent the coordinator's complete tool inventory; and divide work along independent outputs and run those stages in parallel
Explanation
Correct Answer
A:In a multi-repository troubleshooting agent, tool scoping shrinks both decision confusion and the blast radius of delegated actions; alongside this, dependency-aware decomposition avoids serial work when branches do not consume one another, satisfying the distinct requirements that specialized agents work with only relevant permissions and that independent stages of a complex job run efficiently.
Incorrect Answers
B:In a multi-repository troubleshooting agent, tool scoping shrinks both decision confusion and the blast radius of delegated actions, 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.
C:In a multi-repository troubleshooting agent, unneeded write or network tools expand risk without improving the specialist task and a rigid sequence creates waits even where no dependency exists; the design would fail both conditions: specialized agents work with only relevant permissions and independent stages of a complex job run efficiently.
D:In a multi-repository troubleshooting agent, dependency-aware decomposition avoids serial work when branches do not consume one another, 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 302
In a technical review of a repository change-review job, the architect must address the following constraints together: a CI job invokes Claude without a terminal conversation; a broad tool catalog does not overwhelm a small task. Which change set is most defensible?
- launch an interactive Claude terminal in an unattended runner; and supply only context-relevant tools for the current agent
- run Claude Code in non-interactive print mode with -p; and load all available MCP tools into every specialist turn
- launch an interactive Claude terminal in an unattended runner; and load all available MCP tools into every specialist turn
- run Claude Code in non-interactive print mode with -p; and supply only context-relevant tools for the current agent
- implement only run Claude Code in non-interactive print mode with -p; make no corresponding change for the second requirement
Explanation
Correct Answer
D:In a repository change-review job, headless invocation permits scripted automation and exits after the requested task; alongside this, reducing irrelevant tool definitions improves selection and saves context, satisfying the distinct requirements that a CI job invokes Claude without a terminal conversation and that a broad tool catalog does not overwhelm a small task.
Incorrect Answers
A:In a repository change-review job, reducing irrelevant tool definitions improves selection and saves context, but an interactive session can block automation waiting for a person; therefore the separate requirement that a CI job invokes Claude without a terminal conversation would remain unsatisfied.
B:In a repository change-review job, headless invocation permits scripted automation and exits after the requested task, but tool bloat makes the available actions harder to discriminate; therefore the separate requirement that a broad tool catalog does not overwhelm a small task would remain unsatisfied.
C:In a repository change-review job, an interactive session can block automation waiting for a person and tool bloat makes the available actions harder to discriminate; the design would fail both conditions: a CI job invokes Claude without a terminal conversation and a broad tool catalog does not overwhelm a small task.
E:In a repository change-review job, headless invocation permits scripted automation and exits after the requested task, but the independent mechanism for the other criterion is absent: reducing irrelevant tool definitions improves selection and saves context; as written, the design does not ensure that a broad tool catalog does not overwhelm a small task.
Question 303
The release checklist for a vendor onboarding document pipeline explicitly checks that the model can use a tool result in its next decision; it also checks that contradictory evidence is reviewed before action. What coordinated solution meets the checklist?
- implement only append the assistant tool-use response and matching user tool_result blocks to history; make no corresponding change for the second requirement
- append the assistant tool-use response and matching user tool_result blocks to history; and select the most recent-looking sentence without checking its source
- put the tool output only in application logs; and mark the inconsistency and request resolution or human verification
- put the tool output only in application logs; and select the most recent-looking sentence without checking its source
- append the assistant tool-use response and matching user tool_result blocks to history; and mark the inconsistency and request resolution or human verification
Explanation
Correct Answer
E:In a vendor onboarding document pipeline, Claude needs the prior request and the execution output in the conversation for the next inference; alongside this, conflicting source claims are a knowledge gap, not authorization to guess, satisfying the distinct requirements that the model can use a tool result in its next decision and that contradictory evidence is reviewed before action.
Incorrect Answers
A:In a vendor onboarding document pipeline, Claude needs the prior request and the execution output in the conversation for the next inference, but the independent mechanism for the other criterion is absent: conflicting source claims are a knowledge gap, not authorization to guess; as written, the design does not ensure that contradictory evidence is reviewed before action.
B:In a vendor onboarding document pipeline, Claude needs the prior request and the execution output in the conversation for the next inference, but recency alone cannot establish which contradictory record is correct; therefore the separate requirement that contradictory evidence is reviewed before action would remain unsatisfied.
C:In a vendor onboarding document pipeline, conflicting source claims are a knowledge gap, not authorization to guess, but unseen logs cannot inform the model's next decision; therefore the separate requirement that the model can use a tool result in its next decision would remain unsatisfied.
D:In a vendor onboarding document pipeline, unseen logs cannot inform the model's next decision and recency alone cannot establish which contradictory record is correct; the design would fail both conditions: the model can use a tool result in its next decision and contradictory evidence is reviewed before action.
Question 304
When designing a document field validation service, the requirement is not satisfied unless a user-facing chat answer returns with low latency and a failed retrieval agent does not masquerade as having found no matches. Which implementation addresses the two independent conditions?
- submit the one message to an offline batch and block for completion; and return a typed failure status with its origin to the coordinator
- use synchronous Messages requests for the interactive path; and convert every retrieval failure into an empty list
- submit the one message to an offline batch and block for completion; and convert every retrieval failure into an empty list
- use synchronous Messages requests for the interactive path; and return a typed failure status with its origin to the coordinator
Explanation
Correct Answer
D:In a document field validation service, the caller needs an immediate result rather than an asynchronously retrieved batch output; alongside this, an operational error must remain distinguishable from a valid empty result, satisfying the distinct requirements that a user-facing chat answer returns with low latency and that a failed retrieval agent does not masquerade as having found no matches.
Incorrect Answers
A:In a document field validation service, an operational error must remain distinguishable from a valid empty result, but batch scheduling is a poor fit for a live conversational deadline; therefore the separate requirement that a user-facing chat answer returns with low latency would remain unsatisfied.
B:In a document field validation service, the caller needs an immediate result rather than an asynchronously retrieved batch output, but the final report could incorrectly claim no sources exist; therefore the separate requirement that a failed retrieval agent does not masquerade as having found no matches would remain unsatisfied.
C:In a document field validation service, batch scheduling is a poor fit for a live conversational deadline and the final report could incorrectly claim no sources exist; the design would fail both conditions: a user-facing chat answer returns with low latency and a failed retrieval agent does not masquerade as having found no matches.
Question 305
An architecture review of a code policy conformance job finds two missing guarantees: only a nested service uses specialized implementation rules; a formatter handles diverse legitimate examples consistently. What two-part change closes both gaps?
- place a dedicated CLAUDE.md in the relevant directory; and supply only a bare instruction to keep formatting consistent
- implement only place a dedicated CLAUDE.md in the relevant directory; make no corresponding change for the second requirement
- place a dedicated CLAUDE.md in the relevant directory; and give a small set of representative input-output demonstrations
- put all service-only details in the repository root instruction file; and give a small set of representative input-output demonstrations
- put all service-only details in the repository root instruction file; and supply only a bare instruction to keep formatting consistent
Explanation
Correct Answer
C:In a code policy conformance job, directory-specific context can refine instructions for work under that subtree; alongside this, few-shot examples show the intended mapping more concretely than broad style adjectives, satisfying the distinct requirements that only a nested service uses specialized implementation rules and that a formatter handles diverse legitimate examples consistently.
Incorrect Answers
A:In a code policy conformance job, directory-specific context can refine instructions for work under that subtree, but abstract instructions leave many output choices open; therefore the separate requirement that a formatter handles diverse legitimate examples consistently would remain unsatisfied.
B:In a code policy conformance job, directory-specific context can refine instructions for work under that subtree, but the independent mechanism for the other criterion is absent: few-shot examples show the intended mapping more concretely than broad style adjectives; as written, the design does not ensure that a formatter handles diverse legitimate examples consistently.
D:In a code policy conformance job, few-shot examples show the intended mapping more concretely than broad style adjectives, but globalizing narrow rules adds irrelevant instructions to unrelated work; therefore the separate requirement that only a nested service uses specialized implementation rules would remain unsatisfied.
E:In a code policy conformance job, globalizing narrow rules adds irrelevant instructions to unrelated work and abstract instructions leave many output choices open; the design would fail both conditions: only a nested service uses specialized implementation rules and a formatter handles diverse legitimate examples consistently.
Question 306
A team operating a deployment-readiness verification process wants to establish two separate behaviors: a team shares a repository-specific MCP server configuration; in addition, a delegated agent receives the background it needs to act. Which plan implements both?
- commit a reviewed project .mcp.json without credentials; and assume the child agent sees all previous coordinator turns
- commit a reviewed project .mcp.json without credentials; and pass the necessary task context and references explicitly at invocation
- configure each contributor's personal MCP registry manually; and assume the child agent sees all previous coordinator turns
- configure each contributor's personal MCP registry manually; and pass the necessary task context and references explicitly at invocation
Explanation
Correct Answer
B:In a deployment-readiness verification process, project-scoped configuration can be distributed with the repository while keeping secrets external; alongside this, subagents do not automatically inherit the coordinator's entire conversational history, satisfying the distinct requirements that a team shares a repository-specific MCP server configuration and that a delegated agent receives the background it needs to act.
Incorrect Answers
A:In a deployment-readiness verification process, project-scoped configuration can be distributed with the repository while keeping secrets external, but implicit context inheritance makes delegation fragile and incomplete; therefore the separate requirement that a delegated agent receives the background it needs to act would remain unsatisfied.
C:In a deployment-readiness verification process, local personal settings do not create a reproducible team project setup and implicit context inheritance makes delegation fragile and incomplete; the design would fail both conditions: a team shares a repository-specific MCP server configuration and a delegated agent receives the background it needs to act.
D:In a deployment-readiness verification process, subagents do not automatically inherit the coordinator's entire conversational history, but local personal settings do not create a reproducible team project setup; therefore the separate requirement that a team shares a repository-specific MCP server configuration would remain unsatisfied.
Question 307
In an order-cancellation service, the acceptance criteria require that policy decisions use measurable conditions rather than tone and that an ordinary in-policy question is not escalated needlessly. Which paired implementation meets both?
- describe exact observable triggers and exception rules; and reserve human handoff for specified triggers and let normal cases proceed
- ask the model to use its general intuition about severity; and reserve human handoff for specified triggers and let normal cases proceed
- ask the model to use its general intuition about severity; and send every low-risk question to a human as a default
- describe exact observable triggers and exception rules; and send every low-risk question to a human as a default
Explanation
Correct Answer
A:In an order-cancellation service, operationalized criteria reduce disagreement across similar inputs; alongside this, well-defined boundaries maintain autonomy without bypassing risky decisions, satisfying the distinct requirements that policy decisions use measurable conditions rather than tone and that an ordinary in-policy question is not escalated needlessly.
Incorrect Answers
B:In an order-cancellation service, well-defined boundaries maintain autonomy without bypassing risky decisions, but unquantified intuition varies between cases and reviewers; therefore the separate requirement that policy decisions use measurable conditions rather than tone would remain unsatisfied.
C:In an order-cancellation service, unquantified intuition varies between cases and reviewers and blanket escalation defeats the purpose of routine assistance; the design would fail both conditions: policy decisions use measurable conditions rather than tone and an ordinary in-policy question is not escalated needlessly.
D:In an order-cancellation service, operationalized criteria reduce disagreement across similar inputs, but blanket escalation defeats the purpose of routine assistance; therefore the separate requirement that an ordinary in-policy question is not escalated needlessly would remain unsatisfied.
Question 308
An architecture review of a vendor onboarding document pipeline finds two missing guarantees: a status field can contain only approved business states; a complex document receives focused quality checks. What two-part change closes both gaps?
- accept any model-generated status description; and separate factual, structural, and policy review passes
- accept any model-generated status description; and use one generic request to make the document better
- enforce the approved status enum with structured output and validate it in the consumer; and separate factual, structural, and policy review passes
- enforce the approved status enum with structured output and validate it in the consumer; and use one generic request to make the document better
Explanation
Correct Answer
C:In a vendor onboarding document pipeline, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values; alongside this, specialized criteria can detect different failure modes without one overloaded evaluation instruction, satisfying the distinct requirements that a status field can contain only approved business states and that a complex document receives focused quality checks.
Incorrect Answers
A:In a vendor onboarding document pipeline, specialized criteria can detect different failure modes without one overloaded evaluation instruction, but free-form status phrases can violate a fixed business-state contract; therefore the separate requirement that a status field can contain only approved business states would remain unsatisfied.
B:In a vendor onboarding document pipeline, free-form status phrases can violate a fixed business-state contract and an undifferentiated review can overlook specific required constraints; the design would fail both conditions: a status field can contain only approved business states and a complex document receives focused quality checks.
D:In a vendor onboarding document pipeline, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, but an undifferentiated review can overlook specific required constraints; therefore the separate requirement that a complex document receives focused quality checks would remain unsatisfied.
Question 309
In a compliance interpretation research team, the acceptance criteria require that a classifier avoids marking uncertain cases as confirmed violations and that a conclusion supported by model agreement is also tested against source evidence. Which paired implementation meets both?
- define explicit positive evidence and an abstain or review category; and require source and business-rule checks regardless of model agreement
- tell the model to flag anything that sounds suspicious; and require source and business-rule checks regardless of model agreement
- define explicit positive evidence and an abstain or review category; and promote agreement alone to a guaranteed correctness signal
- tell the model to flag anything that sounds suspicious; and promote agreement alone to a guaranteed correctness signal
Explanation
Correct Answer
A:In a compliance interpretation research team, clear decision thresholds separate direct evidence from weak similarity; alongside this, correlated model errors can survive consensus without external verification, satisfying the distinct requirements that a classifier avoids marking uncertain cases as confirmed violations and that a conclusion supported by model agreement is also tested against source evidence.
Incorrect Answers
B:In a compliance interpretation research team, correlated model errors can survive consensus without external verification, but vague semantic similarity raises false positives; therefore the separate requirement that a classifier avoids marking uncertain cases as confirmed violations would remain unsatisfied.
C:In a compliance interpretation research team, clear decision thresholds separate direct evidence from weak similarity, but shared biases can produce identical wrong conclusions; therefore the separate requirement that a conclusion supported by model agreement is also tested against source evidence would remain unsatisfied.
D:In a compliance interpretation research team, vague semantic similarity raises false positives and shared biases can produce identical wrong conclusions; the design would fail both conditions: a classifier avoids marking uncertain cases as confirmed violations and a conclusion supported by model agreement is also tested against source evidence.
Question 310
In a static analysis automation, the acceptance criteria require that a risky refactor is evaluated before any files change and that all contributors receive the repository's stable engineering conventions. Which paired implementation meets both?
- use plan mode to inspect dependencies and propose steps before execution; and put team-wide rules only in one developer's user-level instructions
- let the agent immediately edit every matching file; and put concise shared guidance in the repository root CLAUDE.md
- use plan mode to inspect dependencies and propose steps before execution; and put concise shared guidance in the repository root CLAUDE.md
- let the agent immediately edit every matching file; and put team-wide rules only in one developer's user-level instructions
- implement only put concise shared guidance in the repository root CLAUDE.md; make no corresponding change for the first requirement
Explanation
Correct Answer
C:In a static analysis automation, planning separates investigation and approval from code mutation; alongside this, project instructions travel with the codebase and establish common architecture and build constraints, satisfying the distinct requirements that a risky refactor is evaluated before any files change and that all contributors receive the repository's stable engineering conventions.
Incorrect Answers
A:In a static analysis automation, planning separates investigation and approval from code mutation, but personal files do not distribute the intended conventions to other contributors; therefore the separate requirement that all contributors receive the repository's stable engineering conventions would remain unsatisfied.
B:In a static analysis automation, project instructions travel with the codebase and establish common architecture and build constraints, but early writes can spread an unapproved assumption through the repository; therefore the separate requirement that a risky refactor is evaluated before any files change would remain unsatisfied.
D:In a static analysis automation, early writes can spread an unapproved assumption through the repository and personal files do not distribute the intended conventions to other contributors; the design would fail both conditions: a risky refactor is evaluated before any files change and all contributors receive the repository's stable engineering conventions.
E:In a static analysis automation, project instructions travel with the codebase and establish common architecture and build constraints, but the independent mechanism for the other criterion is absent: planning separates investigation and approval from code mutation; as written, the design does not ensure that a risky refactor is evaluated before any files change.