Question 720
For a mobile client bug-fix task, a reviewer identifies two independent obligations: a delegated skill should not fill the caller's active context and the assistant locates files containing a particular symbol or string. Which proposal should be approved?
- load all investigation steps into the same conversation by default; and use Grep to search file contents
- configure the skill to run in an isolated forked context where supported; and use Grep to search file contents
- configure the skill to run in an isolated forked context where supported; and scan only filenames with Glob
- load all investigation steps into the same conversation by default; and scan only filenames with Glob
Explanation
Correct Answer
B:In a mobile client bug-fix task, a fork isolates exploratory work and returns a concise result to its caller; alongside this, text search locates occurrences efficiently before focused reading, satisfying the distinct requirements that a delegated skill should not fill the caller's active context and that the assistant locates files containing a particular symbol or string.
Incorrect Answers
A:In a mobile client bug-fix task, text search locates occurrences efficiently before focused reading, but the caller's window accumulates unnecessary intermediate details; therefore the separate requirement that a delegated skill should not fill the caller's active context would remain unsatisfied.
C:In a mobile client bug-fix task, a fork isolates exploratory work and returns a concise result to its caller, but path matching does not inspect symbol occurrences inside files; therefore the separate requirement that the assistant locates files containing a particular symbol or string would remain unsatisfied.
D:In a mobile client bug-fix task, the caller's window accumulates unnecessary intermediate details and path matching does not inspect symbol occurrences inside files; the design would fail both conditions: a delegated skill should not fill the caller's active context and the assistant locates files containing a particular symbol or string.
Question 721
A procurement processor encounters intermittent upstream service failures while its agent can also request destructive administrative actions. Choose TWO safeguards: one for selective retries and one for operation-time human authorization.
- interrupt or deny the tool until an authorization callback approves it
- include a retryable classification and bounded retry advice
- retry every error with the same request indefinitely
- collect a general approval at the start of the conversation
Explanation
Correct Answers
A:For a procurement document processing system, execution gates make the approval binding on the selected action and inputs, which directly establishes that a destructive tool receives human authorization at execution time; the separate requirement that temporary service faults can be retried selectively is handled by a different action.
B:For a procurement document processing system, typed transient failures allow backoff without treating permanent errors the same way, which directly establishes that temporary service faults can be retried selectively; the separate requirement that a destructive tool receives human authorization at execution time is handled by a different action.
Incorrect Answers
C:For a procurement document processing system, permission and validation failures will not heal through repetition, so this option cannot establish that temporary service faults can be retried selectively; correctly addressing a destructive tool receives human authorization at execution time elsewhere does not repair that deficiency.
D:For a procurement document processing system, blanket consent does not verify the later high-risk operation, so this option cannot establish that a destructive tool receives human authorization at execution time; correctly addressing temporary service faults can be retried selectively elsewhere does not repair that deficiency.
Question 722
A team operating an after-sales issue resolver wants to establish two separate behaviors: a payment-changing action obtains explicit user authorization; in addition, one specialist's crash does not discard other verified outputs. Which plan implements both?
- confirm the intended action and scope before invoking the write; and restart every agent and erase prior results after a single crash
- treat a request for information as permission to mutate the account; and isolate branch failures and preserve completed artifacts for coordination
- treat a request for information as permission to mutate the account; and restart every agent and erase prior results after a single crash
- confirm the intended action and scope before invoking the write; and isolate branch failures and preserve completed artifacts for coordination
Explanation
Correct Answer
D:In an after-sales issue resolver, consent is specific to the side effect and cannot be inferred from a general inquiry; alongside this, fault containment avoids losing good work while a failed branch is repaired, satisfying the distinct requirements that a payment-changing action obtains explicit user authorization and that one specialist's crash does not discard other verified outputs.
Incorrect Answers
A:In an after-sales issue resolver, consent is specific to the side effect and cannot be inferred from a general inquiry, but unaffected branches would be redone and provenance could be lost; therefore the separate requirement that one specialist's crash does not discard other verified outputs would remain unsatisfied.
B:In an after-sales issue resolver, fault containment avoids losing good work while a failed branch is repaired, but asking a question does not approve a financial change; therefore the separate requirement that a payment-changing action obtains explicit user authorization would remain unsatisfied.
C:In an after-sales issue resolver, asking a question does not approve a financial change and unaffected branches would be redone and provenance could be lost; the design would fail both conditions: a payment-changing action obtains explicit user authorization and one specialist's crash does not discard other verified outputs.
Question 723
In a cross-service developer portal, the acceptance criteria require that test-specific naming conventions run only when touching test files and that reviewer feedback points to a specific missed requirement. Which paired implementation meets both?
- use a test-file glob in the rules frontmatter; and repeat the original prompt verbatim and expect a different outcome
- use a test-file glob in the rules frontmatter; and turn the feedback into a concrete test or change request
- apply the same test naming rule to every source file; and repeat the original prompt verbatim and expect a different outcome
- apply the same test naming rule to every source file; and turn the feedback into a concrete test or change request
Explanation
Correct Answer
B:In a cross-service developer portal, glob matching limits enforcement guidance to the intended file families; alongside this, actionable feedback narrows the next edit and makes improvement measurable, satisfying the distinct requirements that test-specific naming conventions run only when touching test files and that reviewer feedback points to a specific missed requirement.
Incorrect Answers
A:In a cross-service developer portal, glob matching limits enforcement guidance to the intended file families, but unchanged inputs do not target the identified deficiency; therefore the separate requirement that reviewer feedback points to a specific missed requirement would remain unsatisfied.
C:In a cross-service developer portal, production files and configuration do not share the test naming context and unchanged inputs do not target the identified deficiency; the design would fail both conditions: test-specific naming conventions run only when touching test files and reviewer feedback points to a specific missed requirement.
D:In a cross-service developer portal, actionable feedback narrows the next edit and makes improvement measurable, but production files and configuration do not share the test naming context; therefore the separate requirement that test-specific naming conventions run only when touching test files would remain unsatisfied.
Question 724
Tests for a service-credit approval assistant will pass only if only one approved write tool is callable in a sensitive stage and if a payment-changing action obtains explicit user authorization. Which proposed design directly satisfies both checks?
- restrict the stage's allowed tool set and verify permissions in the executor; and treat a request for information as permission to mutate the account
- restrict the stage's allowed tool set and verify permissions in the executor; and confirm the intended action and scope before invoking the write
- let the model select from a broad global list of tools; and treat a request for information as permission to mutate the account
- let the model select from a broad global list of tools; and confirm the intended action and scope before invoking the write
Explanation
Correct Answer
B:In a service-credit approval assistant, capability scoping narrows possible side effects before model selection; alongside this, consent is specific to the side effect and cannot be inferred from a general inquiry, satisfying the distinct requirements that only one approved write tool is callable in a sensitive stage and that a payment-changing action obtains explicit user authorization.
Incorrect Answers
A:In a service-credit approval assistant, capability scoping narrows possible side effects before model selection, but asking a question does not approve a financial change; therefore the separate requirement that a payment-changing action obtains explicit user authorization would remain unsatisfied.
C:In a service-credit approval assistant, excess capabilities create avoidable routing and authorization risk and asking a question does not approve a financial change; the design would fail both conditions: only one approved write tool is callable in a sensitive stage and a payment-changing action obtains explicit user authorization.
D:In a service-credit approval assistant, consent is specific to the side effect and cannot be inferred from a general inquiry, 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.
Question 725
In a code-reference retrieval assistant, the acceptance criteria require that specialists return comparable artifacts for aggregation and that workload growth does not cause uncontrolled parallel fan-out. Which paired implementation meets both?
- implement only limit concurrency and schedule independent jobs against execution budgets; make no corresponding change for the first requirement
- give subagents a common results contract including claim, evidence, and status; and limit concurrency and schedule independent jobs against execution budgets
- give subagents a common results contract including claim, evidence, and status; and launch all possible child tasks at once without resource controls
- merge narrative responses by concatenating their text; and launch all possible child tasks at once without resource controls
- merge narrative responses by concatenating their text; and limit concurrency and schedule independent jobs against execution budgets
Explanation
Correct Answer
B:In a code-reference retrieval assistant, a typed handoff lets the coordinator compare like fields and detect missing support; alongside this, bounded orchestration balances throughput with tool quotas and downstream service capacity, satisfying the distinct requirements that specialists return comparable artifacts for aggregation and that workload growth does not cause uncontrolled parallel fan-out.
Incorrect Answers
A:In a code-reference retrieval assistant, bounded orchestration balances throughput with tool quotas and downstream service capacity, but the independent mechanism for the other criterion is absent: a typed handoff lets the coordinator compare like fields and detect missing support; as written, the design does not ensure that specialists return comparable artifacts for aggregation.
C:In a code-reference retrieval assistant, a typed handoff lets the coordinator compare like fields and detect missing support, but unbounded fan-out can overwhelm tools and blow through cost budgets; therefore the separate requirement that workload growth does not cause uncontrolled parallel fan-out would remain unsatisfied.
D:In a code-reference retrieval assistant, unstructured concatenation hides provenance and duplicate or conflicting claims and unbounded fan-out can overwhelm tools and blow through cost budgets; the design would fail both conditions: specialists return comparable artifacts for aggregation and workload growth does not cause uncontrolled parallel fan-out.
E:In a code-reference retrieval assistant, bounded orchestration balances throughput with tool quotas and downstream service capacity, but unstructured concatenation hides provenance and duplicate or conflicting claims; therefore the separate requirement that specialists return comparable artifacts for aggregation would remain unsatisfied.
Question 726
In a technical due-diligence report generator, the immediate design requirement is that a new agent gets only durable context from a completed job. Which change most directly establishes that behavior?
- preserve both branch identifiers and outcome summaries
- paste a full historical transcript into every new session
- initialize a fresh session with a verified structured summary
- fork the existing session into a separate line of exploration
Explanation
Correct Answer
C:For a technical due-diligence report generator, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context; this directly establishes that a new agent gets only durable context from a completed job instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although tracking lineage makes result comparison possible without confusing which session produced an artifact, that only supports the distinct goal that an exploratory branch can be compared with a baseline later, not the requirement that a new agent gets only durable context from a completed job in a technical due-diligence report generator.
B:In a technical due-diligence report generator, irrelevant turns can consume context and revive outdated assumptions; as a result, the stated requirement that a new agent gets only durable context from a completed job would still not be met.
D:Although a fork supports competing paths while preserving the original session history, that only supports the distinct goal that an alternate implementation is explored without rewriting the original branch, not the requirement that a new agent gets only durable context from a completed job in a technical due-diligence report generator.
Question 727
The release gate for a code policy conformance job requires that multiple subagent outputs can be traced to their individual tasks; it also requires that a required validation step runs before the final response even when the model does not support forced tool choice. Which TWO actions meet the specified checks? Choose TWO.
- attach task IDs and source references to returned artifacts
- enforce the validator in application control flow, using forced tool_choice only with compatible models
- strip origin metadata from each response before merging
- rely on a prompt asking the model to call the validator
Explanation
Correct Answers
A:For a code policy conformance job, traceable results let the coordinator identify which delegation produced each claim, which directly establishes that multiple subagent outputs can be traced to their individual tasks; the separate requirement that a required validation step runs before the final response even when the model does not support forced tool choice is handled by a different action.
B:For a code policy conformance job, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, which directly establishes that a required validation step runs before the final response even when the model does not support forced tool choice; the separate requirement that multiple subagent outputs can be traced to their individual tasks is handled by a different action.
Incorrect Answers
C:For a code policy conformance job, source-less aggregation impairs diagnosis and fact checking, so this option cannot establish that multiple subagent outputs can be traced to their individual tasks; correctly addressing a required validation step runs before the final response even when the model does not support forced tool choice elsewhere does not repair that deficiency.
D:For a code policy conformance job, prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions, so this option cannot establish that a required validation step runs before the final response even when the model does not support forced tool choice; correctly addressing multiple subagent outputs can be traced to their individual tasks elsewhere does not repair that deficiency.
Question 728
An incident postmortem for a build verification pipeline requires controls so that the report is not drafted before evidence is checked and that tool output is normalized before it enters the agent context. Which paired remedy covers both failure modes?
- place evidence validation before the drafting stage; and use a PostToolUse processing hook to standardize the returned data
- place evidence validation before the drafting stage; and preprocess only the original user message
- start drafting at the same time as the source search and assume success; and use a PostToolUse processing hook to standardize the returned data
- start drafting at the same time as the source search and assume success; and preprocess only the original user message
Explanation
Correct Answer
A:In a build verification pipeline, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions; 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 the report is not drafted before evidence is checked and that tool output is normalized before it enters the agent context.
Incorrect Answers
B:In a build verification pipeline, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions, 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.
C:In a build verification pipeline, post-execution interception can clean result fields and attach useful status without changing the model's tool selection, but the writer may treat unverified or absent evidence as real; therefore the separate requirement that the report is not drafted before evidence is checked would remain unsatisfied.
D:In a build verification pipeline, the writer may treat unverified or absent evidence as real and input normalization does not correct inconsistent tool outputs; the design would fail both conditions: the report is not drafted before evidence is checked and tool output is normalized before it enters the agent context.
Question 729
When designing an after-sales issue resolver, the requirement is not satisfied unless a corrected attempt preserves a record of prior validation findings and an extractor always returns the identifiers required by downstream code. Which implementation addresses the two independent conditions?
- replace all earlier outputs without recording the validation history; and declare mandatory schema fields in the required list
- replace all earlier outputs without recording the validation history; and treat every identifier as an optional free-form note
- retain the original source, response version, and retry feedback; and declare mandatory schema fields in the required list
- retain the original source, response version, and retry feedback; and treat every identifier as an optional free-form note
Explanation
Correct Answer
C:In an after-sales issue resolver, traceable attempts allow auditors to distinguish correction from silent overwrite; alongside this, required properties prevent accidental omission of key attributes, satisfying the distinct requirements that a corrected attempt preserves a record of prior validation findings and that an extractor always returns the identifiers required by downstream code.
Incorrect Answers
A:In an after-sales issue resolver, required properties prevent accidental omission of key attributes, 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.
B:In an after-sales issue resolver, the reason for a changed value becomes untraceable and the consumer cannot reliably rely on a field that may be omitted; the design would fail both conditions: a corrected attempt preserves a record of prior validation findings and an extractor always returns the identifiers required by downstream code.
D:In an after-sales issue resolver, traceable attempts allow auditors to distinguish correction from silent overwrite, but the consumer cannot reliably rely on a field that may be omitted; therefore the separate requirement that an extractor always returns the identifiers required by downstream code would remain unsatisfied.
Question 730
Production readiness for an order-cancellation service depends on ensuring that a new agent gets only durable context from a completed job and that partial completion of a multi-step operation is handled safely. Select the most appropriate combined approach.
- paste a full historical transcript into every new session; and treat the first successful tool call as proof that the entire workflow succeeded
- initialize a fresh session with a verified structured summary; and track individual stage outcomes and use explicit recovery or compensating actions
- paste a full historical transcript into every new session; and track individual stage outcomes and use explicit recovery or compensating actions
- initialize a fresh session with a verified structured summary; and treat the first successful tool call as proof that the entire workflow succeeded
Explanation
Correct Answer
B:In an order-cancellation service, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context; alongside this, an orchestrated workflow must not report overall success while a required step failed, satisfying the distinct requirements that a new agent gets only durable context from a completed job and that partial completion of a multi-step operation is handled safely.
Incorrect Answers
A:In an order-cancellation service, irrelevant turns can consume context and revive outdated assumptions and later actions can fail after an earlier side effect; the design would fail both conditions: a new agent gets only durable context from a completed job and partial completion of a multi-step operation is handled safely.
C:In an order-cancellation service, an orchestrated workflow must not report overall success while a required step failed, 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.
D:In an order-cancellation service, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, but later actions can fail after an earlier side effect; therefore the separate requirement that partial completion of a multi-step operation is handled safely would remain unsatisfied.