Question 60
For an unfamiliar monorepo investigation, a reviewer identifies two independent obligations: client-side tool requests trigger another model turn after execution and every high-impact tool invocation produces an audit event. Which proposal should be approved?
- branch on stop_reason tool_use and execute returned tool_use blocks; and record the tool name, permitted inputs, outcome, and task identifier in a hook
- branch on stop_reason tool_use and execute returned tool_use blocks; and infer tool activity from the final natural-language answer
- end the loop whenever assistant text appears; and record the tool name, permitted inputs, outcome, and task identifier in a hook
- end the loop whenever assistant text appears; and infer tool activity from the final natural-language answer
Explanation
Correct Answer
A:In an unfamiliar monorepo investigation, the response explicitly signals pending client execution and the loop must provide results before another model decision; alongside this, runtime instrumentation observes actual proposed or completed tool activity, satisfying the distinct requirements that client-side tool requests trigger another model turn after execution and that every high-impact tool invocation produces an audit event.
Incorrect Answers
B:In an unfamiliar monorepo investigation, the response explicitly signals pending client execution and the loop must provide results before another model decision, 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.
C:In an unfamiliar monorepo investigation, runtime instrumentation observes actual proposed or completed tool activity, but text may accompany a tool request and is not the completion signal; therefore the separate requirement that client-side tool requests trigger another model turn after execution would remain unsatisfied.
D:In an unfamiliar monorepo investigation, text may accompany a tool request and is not the completion signal and a summary can omit failed calls or delegated actions; the design would fail both conditions: client-side tool requests trigger another model turn after execution and every high-impact tool invocation produces an audit event.
Question 61
The release checklist for a vendor onboarding document pipeline explicitly checks that the reviewer does not simply echo the generator's confidence; it also checks that the agent can recover exact policy facts after compaction. What coordinated solution meets the checklist?
- provide the generator's score as the sole review criterion; and retrieve authoritative facts from a durable store when needed
- provide the generator's score as the sole review criterion; and treat the compressed summary as an immutable source of truth
- give the reviewer the source and rubric, not only the draft's self-rating; and treat the compressed summary as an immutable source of truth
- give the reviewer the source and rubric, not only the draft's self-rating; and retrieve authoritative facts from a durable store when needed
Explanation
Correct Answer
D:In a vendor onboarding document pipeline, independent evidence lets a critic challenge unsupported assertions; alongside this, re-reading source state restores precision that a condensed history cannot guarantee, satisfying the distinct requirements that the reviewer does not simply echo the generator's confidence and that the agent can recover exact policy facts after compaction.
Incorrect Answers
A:In a vendor onboarding document pipeline, re-reading source state restores precision that a condensed history cannot guarantee, but anchoring on a self-assigned grade hides actual defects; therefore the separate requirement that the reviewer does not simply echo the generator's confidence would remain unsatisfied.
B:In a vendor onboarding document pipeline, anchoring on a self-assigned grade hides actual defects and summaries may simplify caveats or omit an exception; the design would fail both conditions: the reviewer does not simply echo the generator's confidence and the agent can recover exact policy facts after compaction.
C:In a vendor onboarding document pipeline, independent evidence lets a critic challenge unsupported assertions, but summaries may simplify caveats or omit an exception; therefore the separate requirement that the agent can recover exact policy facts after compaction would remain unsatisfied.
Question 62
An audit of an analyst research coordinator identifies two unmet requirements: every high-impact tool invocation produces an audit event and temporary service faults can be retried selectively. Select TWO actions that remedy those particular deficiencies.
- retry every error with the same request indefinitely
- include a retryable classification and bounded retry advice
- infer tool activity from the final natural-language answer
- record the tool name, permitted inputs, outcome, and task identifier in a hook
Explanation
Correct Answers
B:For an analyst research coordinator, 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 every high-impact tool invocation produces an audit event is handled by a different action.
D:For an analyst research coordinator, runtime instrumentation observes actual proposed or completed tool activity, which directly establishes that every high-impact tool invocation produces an audit event; the separate requirement that temporary service faults can be retried selectively is handled by a different action.
Incorrect Answers
A:For an analyst research coordinator, permission and validation failures will not heal through repetition, so this option cannot establish that temporary service faults can be retried selectively; correctly addressing every high-impact tool invocation produces an audit event elsewhere does not repair that deficiency.
C:For an analyst research coordinator, a summary can omit failed calls or delegated actions, so this option cannot establish that every high-impact tool invocation produces an audit event; correctly addressing temporary service faults can be retried selectively elsewhere does not repair that deficiency.
Question 63
A team operating a service dependency exploration tool wants to establish two separate behaviors: a forced tool call still honors business authorization; in addition, the model can use a tool result in its next decision. Which plan implements both?
- treat a forced tool choice as equivalent to user approval; and append the assistant tool-use response and matching user tool_result blocks to history
- treat a forced tool choice as equivalent to user approval; and put the tool output only in application logs
- combine tool_choice with server-side policy checks; and put the tool output only in application logs
- combine tool_choice with server-side policy checks; and append the assistant tool-use response and matching user tool_result blocks to history
Explanation
Correct Answer
D:In a service dependency exploration tool, selection controls when a tool is proposed but does not grant permission to execute; alongside this, Claude needs the prior request and the execution output in the conversation for the next inference, satisfying the distinct requirements that a forced tool call still honors business authorization and that the model can use a tool result in its next decision.
Incorrect Answers
A:In a service dependency exploration tool, Claude needs the prior request and the execution output in the conversation for the next inference, but tool selection and authorization are different controls; therefore the separate requirement that a forced tool call still honors business authorization would remain unsatisfied.
B:In a service dependency exploration tool, tool selection and authorization are different controls and unseen logs cannot inform the model's next decision; the design would fail both conditions: a forced tool call still honors business authorization and the model can use a tool result in its next decision.
C:In a service dependency exploration tool, selection controls when a tool is proposed but does not grant permission to execute, 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.
Question 64
An incident postmortem for a research PDF metadata pipeline requires controls so that a failed extraction is retried with specific corrective information and that multiple draft branches are merged without contradictory statements. Which paired remedy covers both failure modes?
- implement only feed field-level validation errors back in a bounded retry; make no corresponding change for the second requirement
- repeat the same vague prompt after each failure; and concatenate every agent's conclusion into the final report
- feed field-level validation errors back in a bounded retry; and create a reconciliation stage that checks citations and resolves overlaps
- repeat the same vague prompt after each failure; and create a reconciliation stage that checks citations and resolves overlaps
- feed field-level validation errors back in a bounded retry; and concatenate every agent's conclusion into the final report
Explanation
Correct Answer
C:In a research PDF metadata pipeline, targeted feedback identifies what the next attempt must correct; alongside this, synthesis must select mutually consistent claims with defensible evidence, satisfying the distinct requirements that a failed extraction is retried with specific corrective information and that multiple draft branches are merged without contradictory statements.
Incorrect Answers
A:In a research PDF metadata pipeline, targeted feedback identifies what the next attempt must correct, but the independent mechanism for the other criterion is absent: synthesis must select mutually consistent claims with defensible evidence; as written, the design does not ensure that multiple draft branches are merged without contradictory statements.
B:In a research PDF metadata pipeline, unchanged requests do not reveal which constraint was violated and raw merger preserves disagreements and duplicated statements; the design would fail both conditions: a failed extraction is retried with specific corrective information and multiple draft branches are merged without contradictory statements.
D:In a research PDF metadata pipeline, synthesis must select mutually consistent claims with defensible evidence, but unchanged requests do not reveal which constraint was violated; therefore the separate requirement that a failed extraction is retried with specific corrective information would remain unsatisfied.
E:In a research PDF metadata pipeline, targeted feedback identifies what the next attempt must correct, 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 65
For a tender-response data extractor, a reviewer identifies two independent obligations: a missing MCP capability is diagnosed before changing prompts and a failed MCP operation is visible as an error to the client. Which proposal should be approved?
- increase the system prompt length to compensate for disconnected tools; and mark the tool result as an error and supply structured failure details
- verify server connection, transport, and exposed tool availability; and return a success-shaped value saying the operation probably worked
- increase the system prompt length to compensate for disconnected tools; and return a success-shaped value saying the operation probably worked
- verify server connection, transport, and exposed tool availability; and mark the tool result as an error and supply structured failure details
Explanation
Correct Answer
D:In a tender-response data extractor, tool discovery depends on a live configured integration, not just the prompt wording; alongside this, explicit error status separates failed execution from valid data content, satisfying the distinct requirements that a missing MCP capability is diagnosed before changing prompts and that a failed MCP operation is visible as an error to the client.
Incorrect Answers
A:In a tender-response data extractor, explicit error status separates failed execution from valid data content, but a model cannot call a capability absent from its available tool registry; therefore the separate requirement that a missing MCP capability is diagnosed before changing prompts would remain unsatisfied.
B:In a tender-response data extractor, tool discovery depends on a live configured integration, not just the prompt wording, 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.
C:In a tender-response data extractor, a model cannot call a capability absent from its available tool registry and downstream agents can mistake a failure for verified business data; the design would fail both conditions: a missing MCP capability is diagnosed before changing prompts and a failed MCP operation is visible as an error to the client.
Question 66
Tests for a structured case-file ingestion workflow will pass only if an extractor always returns the identifiers required by downstream code and if a partially failed batch is repaired efficiently. Which proposed design directly satisfies both checks?
- declare mandatory schema fields in the required list; and identify failed records and resubmit only safe retry candidates
- treat every identifier as an optional free-form note; and rerun the entire completed batch whenever one record fails
- treat every identifier as an optional free-form note; and identify failed records and resubmit only safe retry candidates
- declare mandatory schema fields in the required list; and rerun the entire completed batch whenever one record fails
Explanation
Correct Answer
A:In a structured case-file ingestion workflow, required properties prevent accidental omission of key attributes; alongside this, selective retry avoids paying again for already successful items, satisfying the distinct requirements that an extractor always returns the identifiers required by downstream code and that a partially failed batch is repaired efficiently.
Incorrect Answers
B:In a structured case-file ingestion workflow, the consumer cannot reliably rely on a field that may be omitted and successful work would be duplicated unnecessarily; the design would fail both conditions: an extractor always returns the identifiers required by downstream code and a partially failed batch is repaired efficiently.
C:In a structured case-file ingestion workflow, selective retry avoids paying again for already successful items, 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.
D:In a structured case-file ingestion workflow, required properties prevent accidental omission of key attributes, but successful work would be duplicated unnecessarily; therefore the separate requirement that a partially failed batch is repaired efficiently would remain unsatisfied.
Question 67
While preparing a shipping-exception helpdesk for deployment, engineers must ensure that a tool result includes enough fields to support audit and follow-on actions; they must also ensure that several requested client tools are returned in one response. Which combination best satisfies those requirements?
- return structured identifiers, status, and provenance with the data; and execute every tool_use block and return a result with each corresponding ID
- return only a friendly summary with no source identifier; and execute every tool_use block and return a result with each corresponding ID
- return only a friendly summary with no source identifier; and execute only the first returned tool call
- return structured identifiers, status, and provenance with the data; and execute only the first returned tool call
Explanation
Correct Answer
A:In a shipping-exception helpdesk, machine-readable outputs let downstream stages validate exactly what was retrieved; alongside this, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, satisfying the distinct requirements that a tool result includes enough fields to support audit and follow-on actions and that several requested client tools are returned in one response.
Incorrect Answers
B:In a shipping-exception helpdesk, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, but a paraphrase hides the record needed for verification or follow-up; therefore the separate requirement that a tool result includes enough fields to support audit and follow-on actions would remain unsatisfied.
C:In a shipping-exception helpdesk, a paraphrase hides the record needed for verification or follow-up and the unanswered tool uses remain unresolved and later reasoning loses evidence; the design would fail both conditions: a tool result includes enough fields to support audit and follow-on actions and several requested client tools are returned in one response.
D:In a shipping-exception helpdesk, machine-readable outputs let downstream stages validate exactly what was retrieved, 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.
Question 68
In a repository release validation process, the engineering team must guarantee that a classifier avoids marking uncertain cases as confirmed violations. What is the most appropriate control?
- state the conjunction of required matching conditions
- define explicit positive evidence and an abstain or review category
- instruct the model to return unknown or needs-review when evidence is absent
- tell the model to flag anything that sounds suspicious
Explanation
Correct Answer
B:For a repository release validation process, clear decision thresholds separate direct evidence from weak similarity; this directly establishes that a classifier avoids marking uncertain cases as confirmed violations instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although explicit multi-field criteria prevent a single suggestive field from dominating the outcome, that only supports the distinct goal that extracted records are labeled only when required fields agree, not the requirement that a classifier avoids marking uncertain cases as confirmed violations in a repository release validation process.
C:Although a defined abstention path avoids forced confident judgments without facts, that only supports the distinct goal that a risk prompt handles missing supporting evidence honestly, not the requirement that a classifier avoids marking uncertain cases as confirmed violations in a repository release validation process.
D:In a repository release validation process, vague semantic similarity raises false positives; as a result, the stated requirement that a classifier avoids marking uncertain cases as confirmed violations would still not be met.
Question 69
During review of a product landscape research agent, an unmet criterion states that the model can distinguish two similar business tools. Which measure resolves this specific gap?
- give both tools vague names with identical generic descriptions
- declare an operation enum in the schema and reject values outside it in the tool handler
- give each tool a specific purpose and exclusion examples in its description
- document examples and conditions where each tool must not be used
Explanation
Correct Answer
C:For a product landscape research agent, discriminative descriptions reduce wrong routing when operations sound alike; this directly establishes that the model can distinguish two similar business tools instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a product landscape research agent, a model cannot reliably select on boundaries that the interface never explains; as a result, the stated requirement that the model can distinguish two similar business tools would still not be met.
B:Although schema constraints guide valid selections and runtime validation blocks unsupported operation values, that only supports the distinct goal that a selector accepts only supported operation names, not the requirement that the model can distinguish two similar business tools in a product landscape research agent.
D:Although contrastive guidance helps tool choice when resource names look similar, that only supports the distinct goal that near-overlapping retrieval tools are selected by actual boundary, not the requirement that the model can distinguish two similar business tools in a product landscape research agent.
Question 70
During review of a dependency upgrade initiative, an unmet criterion states that the developer inspects a suspicious implementation in context. Which measure resolves this specific gap?
- replace source inspection with a guessed architecture overview
- discover paths using Glob before reading contents
- use Grep to locate occurrences before opening focused files
- read targeted code ranges and nearby dependencies
Explanation
Correct Answer
D:For a dependency upgrade initiative, focused inspection preserves exact implementation detail without loading the whole codebase; this directly establishes that the developer inspects a suspicious implementation in context instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a dependency upgrade initiative, a general overview cannot verify the specific logic being debugged; as a result, the stated requirement that the developer inspects a suspicious implementation in context would still not be met.
B:Although staged path discovery prevents unrelated modules from saturating the context, that only supports the distinct goal that a coding assistant first identifies relevant files in a large repository, not the requirement that the developer inspects a suspicious implementation in context in a dependency upgrade initiative.
C:Although symbol searching narrows the evidence to files that mention the target, that only supports the distinct goal that a code investigation finds where a function is referenced, not the requirement that the developer inspects a suspicious implementation in context in a dependency upgrade initiative.