Question 680
An incident postmortem for a repository documentation project requires controls so that a shared skill can take a supplied target name or file path and that a common security rule remains active across the project. Which paired remedy covers both failure modes?
- copy a separate static instruction file for every target path; and scope the security instruction only to one unrelated test directory
- copy a separate static instruction file for every target path; and keep project-wide security guidance in shared instructions rather than a narrow path glob
- define how the skill accepts and uses invocation arguments; and keep project-wide security guidance in shared instructions rather than a narrow path glob
- define how the skill accepts and uses invocation arguments; and scope the security instruction only to one unrelated test directory
Explanation
Correct Answer
C:In a repository documentation project, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets; alongside this, cross-cutting obligations should not disappear when an agent changes directories, satisfying the distinct requirements that a shared skill can take a supplied target name or file path and that a common security rule remains active across the project.
Incorrect Answers
A:In a repository documentation project, duplicated procedures are costly to maintain and can diverge and other code paths would lack the universal control; the design would fail both conditions: a shared skill can take a supplied target name or file path and a common security rule remains active across the project.
B:In a repository documentation project, cross-cutting obligations should not disappear when an agent changes directories, but duplicated procedures are costly to maintain and can diverge; therefore the separate requirement that a shared skill can take a supplied target name or file path would remain unsatisfied.
D:In a repository documentation project, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets, but other code paths would lack the universal control; therefore the separate requirement that a common security rule remains active across the project would remain unsatisfied.
Question 681
Before expanding a competitive benchmarking pipeline, the owner must demonstrate that a new agent gets only durable context from a completed job, while also demonstrating that sensitive tool calls are denied before they reach an executor. Which design provides both controls?
- paste a full historical transcript into every new session; and register a PreToolUse hook that checks the operation against policy
- paste a full historical transcript into every new session; and write a stronger instruction in the system prompt
- initialize a fresh session with a verified structured summary; and register a PreToolUse hook that checks the operation against policy
- initialize a fresh session with a verified structured summary; and write a stronger instruction in the system prompt
Explanation
Correct Answer
C:In a competitive benchmarking pipeline, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context; alongside this, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, satisfying the distinct requirements that a new agent gets only durable context from a completed job and that sensitive tool calls are denied before they reach an executor.
Incorrect Answers
A:In a competitive benchmarking pipeline, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, but irrelevant turns can consume context and revive outdated assumptions; therefore the separate requirement that a new agent gets only durable context from a completed job would remain unsatisfied.
B:In a competitive benchmarking pipeline, irrelevant turns can consume context and revive outdated assumptions and an instruction alone does not provide deterministic execution-time authorization; the design would fail both conditions: a new agent gets only durable context from a completed job and sensitive tool calls are denied before they reach an executor.
D:In a competitive benchmarking pipeline, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, but an instruction alone does not provide deterministic execution-time authorization; therefore the separate requirement that sensitive tool calls are denied before they reach an executor would remain unsatisfied.
Question 682
In a competitive benchmarking pipeline, the engineering team must guarantee that thousands of independent documents can finish without interactive response deadlines. What is the most appropriate control?
- use asynchronous Message Batches processing for the bulk workload
- use synchronous Messages requests for the interactive path
- make every document a synchronous request inside the user interaction
- freeze the prompt version and schema for the submission set
Explanation
Correct Answer
A:For a competitive benchmarking pipeline, batching suits non-blocking independent requests and can reduce processing cost; this directly establishes that thousands of independent documents can finish without interactive response deadlines instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although the caller needs an immediate result rather than an asynchronously retrieved batch output, that only supports the distinct goal that a user-facing chat answer returns with low latency, not the requirement that thousands of independent documents can finish without interactive response deadlines in a competitive benchmarking pipeline.
C:In a competitive benchmarking pipeline, serial immediate calls add latency where no caller is waiting; as a result, the stated requirement that thousands of independent documents can finish without interactive response deadlines would still not be met.
D:Although versioned common instructions make independently processed records comparable, that only supports the distinct goal that a large batch shares a consistent evaluation rubric, not the requirement that thousands of independent documents can finish without interactive response deadlines in a competitive benchmarking pipeline.
Question 683
In a technical review of a customs paperwork processor, the architect must address the following constraints together: thousands of independent documents can finish without interactive response deadlines; the team can diagnose which fields repeatedly fail extraction. Which change set is most defensible?
- use asynchronous Message Batches processing for the bulk workload; and record validation failure codes and field paths per attempt
- make every document a synchronous request inside the user interaction; and record validation failure codes and field paths per attempt
- make every document a synchronous request inside the user interaction; and log only the final success-or-failure boolean
- use asynchronous Message Batches processing for the bulk workload; and log only the final success-or-failure boolean
Explanation
Correct Answer
A:In a customs paperwork processor, batching suits non-blocking independent requests and can reduce processing cost; alongside this, granular observability reveals schema weaknesses and document patterns, satisfying the distinct requirements that thousands of independent documents can finish without interactive response deadlines and that the team can diagnose which fields repeatedly fail extraction.
Incorrect Answers
B:In a customs paperwork processor, granular observability reveals schema weaknesses and document patterns, but serial immediate calls add latency where no caller is waiting; therefore the separate requirement that thousands of independent documents can finish without interactive response deadlines would remain unsatisfied.
C:In a customs paperwork processor, serial immediate calls add latency where no caller is waiting and an aggregate flag hides the source of extraction errors; the design would fail both conditions: thousands of independent documents can finish without interactive response deadlines and the team can diagnose which fields repeatedly fail extraction.
D:In a customs paperwork processor, batching suits non-blocking independent requests and can reduce processing cost, but an aggregate flag hides the source of extraction errors; therefore the separate requirement that the team can diagnose which fields repeatedly fail extraction would remain unsatisfied.
Question 684
When designing a source-grounded policy synthesis service, the requirement is not satisfied unless a large research job combines specialized findings into one answer and a failed MCP operation is visible as an error to the client. Which implementation addresses the two independent conditions?
- have all subagents independently publish the final answer; and mark the tool result as an error and supply structured failure details
- use a coordinator that delegates focused tasks and owns final synthesis; and mark the tool result as an error and supply structured failure details
- use a coordinator that delegates focused tasks and owns final synthesis; and return a success-shaped value saying the operation probably worked
- have all subagents independently publish the final answer; and return a success-shaped value saying the operation probably worked
Explanation
Correct Answer
B:In a source-grounded policy synthesis service, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter; alongside this, explicit error status separates failed execution from valid data content, satisfying the distinct requirements that a large research job combines specialized findings into one answer and that a failed MCP operation is visible as an error to the client.
Incorrect Answers
A:In a source-grounded policy synthesis service, explicit error status separates failed execution from valid data content, but independent final outputs offer no single point to reconcile contradictions; therefore the separate requirement that a large research job combines specialized findings into one answer would remain unsatisfied.
C:In a source-grounded policy synthesis service, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, but downstream agents can mistake a failure for verified business data; therefore the separate requirement that a failed MCP operation is visible as an error to the client would remain unsatisfied.
D:In a source-grounded policy synthesis service, independent final outputs offer no single point to reconcile contradictions and downstream agents can mistake a failure for verified business data; the design would fail both conditions: a large research job combines specialized findings into one answer and a failed MCP operation is visible as an error to the client.
Question 685
An incident postmortem for a subscription support service requires controls so that important workflow state survives context compression or process restarts and that several requested client tools are returned in one response. Which paired remedy covers both failure modes?
- persist authoritative task facts and artifact IDs outside ephemeral conversation text; and execute only the first returned tool call
- implement only persist authoritative task facts and artifact IDs outside ephemeral conversation text; make no corresponding change for the second requirement
- depend on the model remembering a prior value forever; and execute every tool_use block and return a result with each corresponding ID
- persist authoritative task facts and artifact IDs outside ephemeral conversation text; and execute every tool_use block and return a result with each corresponding ID
- depend on the model remembering a prior value forever; and execute only the first returned tool call
Explanation
Correct Answer
D:In a subscription support service, external durable state can be reloaded and checked when the session window changes; alongside this, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, satisfying the distinct requirements that important workflow state survives context compression or process restarts and that several requested client tools are returned in one response.
Incorrect Answers
A:In a subscription support service, external durable state can be reloaded and checked when the session window changes, but the unanswered tool uses remain unresolved and later reasoning loses evidence; therefore the separate requirement that several requested client tools are returned in one response would remain unsatisfied.
B:In a subscription support service, external durable state can be reloaded and checked when the session window changes, but the independent mechanism for the other criterion is absent: a multi-tool assistant turn can request independent actions and must receive all matching outcomes; as written, the design does not ensure that several requested client tools are returned in one response.
C:In a subscription support service, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, but context limits and summarization can lose exact identifiers; therefore the separate requirement that important workflow state survives context compression or process restarts would remain unsatisfied.
E:In a subscription support service, context limits and summarization can lose exact identifiers and the unanswered tool uses remain unresolved and later reasoning loses evidence; the design would fail both conditions: important workflow state survives context compression or process restarts and several requested client tools are returned in one response.
Question 686
Tests for a document field validation service will pass only if a user-facing chat answer returns with low latency and if reviewer changes remain auditable. Which proposed design directly satisfies both checks?
- submit the one message to an offline batch and block for completion; and overwrite an automated answer without preserving the reviewer decision
- use synchronous Messages requests for the interactive path; and log the reviewer identity, decision, justification, and artifact version
- submit the one message to an offline batch and block for completion; and log the reviewer identity, decision, justification, and artifact version
- use synchronous Messages requests for the interactive path; and overwrite an automated answer without preserving the reviewer decision
Explanation
Correct Answer
B:In a document field validation service, the caller needs an immediate result rather than an asynchronously retrieved batch output; alongside this, a versioned approval trail supports diagnosis and later governance reviews, satisfying the distinct requirements that a user-facing chat answer returns with low latency and that reviewer changes remain auditable.
Incorrect Answers
A:In a document field validation service, batch scheduling is a poor fit for a live conversational deadline and the final state loses the reason it changed; the design would fail both conditions: a user-facing chat answer returns with low latency and reviewer changes remain auditable.
C:In a document field validation service, a versioned approval trail supports diagnosis and later governance reviews, 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.
D:In a document field validation service, the caller needs an immediate result rather than an asynchronously retrieved batch output, but the final state loses the reason it changed; therefore the separate requirement that reviewer changes remain auditable would remain unsatisfied.
Question 687
The release gate for a cross-platform application migration requires that the implementation plan receives stakeholder sign-off; it also requires that a code investigation finds where a function is referenced. Which TWO actions meet the specified checks? Choose TWO.
- treat the agent's internally generated plan as implicit approval
- use Grep to locate occurrences before opening focused files
- ask for broad prose summaries of every package first
- present ordered changes, risks, and verification steps before switching to execution
Explanation
Correct Answers
B:For a cross-platform application migration, symbol searching narrows the evidence to files that mention the target, which directly establishes that a code investigation finds where a function is referenced; the separate requirement that the implementation plan receives stakeholder sign-off is handled by a different action.
D:For a cross-platform application migration, an explicit review point aligns the agent's work with the authorized scope, which directly establishes that the implementation plan receives stakeholder sign-off; the separate requirement that a code investigation finds where a function is referenced is handled by a different action.
Incorrect Answers
A:For a cross-platform application migration, the system cannot infer external authorization from its own reasoning, so this option cannot establish that the implementation plan receives stakeholder sign-off; correctly addressing a code investigation finds where a function is referenced elsewhere does not repair that deficiency.
C:For a cross-platform application migration, high-level summaries can miss the exact call site, so this option cannot establish that a code investigation finds where a function is referenced; correctly addressing the implementation plan receives stakeholder sign-off elsewhere does not repair that deficiency.
Question 688
When designing a pre-merge code inspection workflow, the requirement is not satisfied unless a forced tool call still honors business authorization and the agent executes tests and examines their exit status. Which implementation addresses the two independent conditions?
- combine tool_choice with server-side policy checks; and inspect the test configuration only with Read and claim tests passed
- treat a forced tool choice as equivalent to user approval; and inspect the test configuration only with Read and claim tests passed
- combine tool_choice with server-side policy checks; and use Bash with an approved test command
- treat a forced tool choice as equivalent to user approval; and use Bash with an approved test command
Explanation
Correct Answer
C:In a pre-merge code inspection workflow, selection controls when a tool is proposed but does not grant permission to execute; alongside this, the shell can run build tools and return execution feedback that Read cannot supply, satisfying the distinct requirements that a forced tool call still honors business authorization and that the agent executes tests and examines their exit status.
Incorrect Answers
A:In a pre-merge code inspection workflow, selection controls when a tool is proposed but does not grant permission to execute, but reading configuration does not execute a test suite; therefore the separate requirement that the agent executes tests and examines their exit status would remain unsatisfied.
B:In a pre-merge code inspection workflow, tool selection and authorization are different controls and reading configuration does not execute a test suite; the design would fail both conditions: a forced tool call still honors business authorization and the agent executes tests and examines their exit status.
D:In a pre-merge code inspection workflow, the shell can run build tools and return execution feedback that Read cannot supply, but tool selection and authorization are different controls; therefore the separate requirement that a forced tool call still honors business authorization would remain unsatisfied.
Question 689
While preparing a purchase-order parsing service for deployment, engineers must ensure that schema-valid output is also checked against source evidence; they must also ensure that the system distinguishes acceptable and unacceptable edge cases. Which combination best satisfies those requirements?
- assume a schema-conforming response is factually correct; and provide only a broad topic label as the classification rule
- validate semantic constraints and provenance in application logic; and provide only a broad topic label as the classification rule
- validate semantic constraints and provenance in application logic; and specify inclusion criteria and explicit exclusion conditions
- assume a schema-conforming response is factually correct; and specify inclusion criteria and explicit exclusion conditions
Explanation
Correct Answer
C:In a purchase-order parsing service, JSON shape does not prove that an extracted claim is supported by the document; alongside this, negative boundaries teach the model when a near-match must not trigger, satisfying the distinct requirements that schema-valid output is also checked against source evidence and that the system distinguishes acceptable and unacceptable edge cases.
Incorrect Answers
A:In a purchase-order parsing service, syntactic conformance cannot guarantee source-level truth and generic labels leave ambiguous boundary cases undefined; the design would fail both conditions: schema-valid output is also checked against source evidence and the system distinguishes acceptable and unacceptable edge cases.
B:In a purchase-order parsing service, JSON shape does not prove that an extracted claim is supported by the document, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.
D:In a purchase-order parsing service, negative boundaries teach the model when a near-match must not trigger, but syntactic conformance cannot guarantee source-level truth; therefore the separate requirement that schema-valid output is also checked against source evidence would remain unsatisfied.
Question 690
When designing a customer refund workflow, the requirement is not satisfied unless out-of-policy exceptions receive an authorized decision and tool output is normalized before it enters the agent context. Which implementation addresses the two independent conditions?
- route the exception to a human approval step before execution; and use a PostToolUse processing hook to standardize the returned data
- implement only route the exception to a human approval step before execution; make no corresponding change for the second requirement
- let the agent approve an exception whenever its wording sounds confident; and preprocess only the original user message
- let the agent approve an exception whenever its wording sounds confident; and use a PostToolUse processing hook to standardize the returned data
- route the exception to a human approval step before execution; and preprocess only the original user message
Explanation
Correct Answer
A:In a customer refund workflow, approval is a workflow boundary separate from language-model confidence; alongside this, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, satisfying the distinct requirements that out-of-policy exceptions receive an authorized decision and that tool output is normalized before it enters the agent context.
Incorrect Answers
B:In a customer refund workflow, approval is a workflow boundary separate from language-model confidence, but the independent mechanism for the other criterion is absent: post-execution interception can clean result fields and attach useful status without changing the model's tool selection; as written, the design does not ensure that tool output is normalized before it enters the agent context.
C:In a customer refund workflow, model confidence is not delegated business authority and input normalization does not correct inconsistent tool outputs; the design would fail both conditions: out-of-policy exceptions receive an authorized decision and tool output is normalized before it enters the agent context.
D:In a customer refund workflow, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, but model confidence is not delegated business authority; therefore the separate requirement that out-of-policy exceptions receive an authorized decision would remain unsatisfied.
E:In a customer refund workflow, approval is a workflow boundary separate from language-model confidence, but input normalization does not correct inconsistent tool outputs; therefore the separate requirement that tool output is normalized before it enters the agent context would remain unsatisfied.