Question 670
When designing a returns-and-billing assistant, the requirement is not satisfied unless an extractor always returns the identifiers required by downstream code and a support case missing an essential fact is not silently guessed. Which implementation addresses the two independent conditions?
- treat every identifier as an optional free-form note; and ask a focused clarifying question for the missing requirement
- treat every identifier as an optional free-form note; and invent a plausible value and continue automatically
- declare mandatory schema fields in the required list; and invent a plausible value and continue automatically
- declare mandatory schema fields in the required list; and ask a focused clarifying question for the missing requirement
Explanation
Correct Answer
D:In a returns-and-billing assistant, required properties prevent accidental omission of key attributes; alongside this, targeted clarification supplies the decision input before selecting an irreversible action, satisfying the distinct requirements that an extractor always returns the identifiers required by downstream code and that a support case missing an essential fact is not silently guessed.
Incorrect Answers
A:In a returns-and-billing assistant, targeted clarification supplies the decision input before selecting an irreversible action, 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.
B:In a returns-and-billing assistant, the consumer cannot reliably rely on a field that may be omitted and fabricated facts can cause the wrong account or policy to be applied; the design would fail both conditions: an extractor always returns the identifiers required by downstream code and a support case missing an essential fact is not silently guessed.
C:In a returns-and-billing assistant, required properties prevent accidental omission of key attributes, but fabricated facts can cause the wrong account or policy to be applied; therefore the separate requirement that a support case missing an essential fact is not silently guessed would remain unsatisfied.
Question 671
An audit of an insurance document extraction agent identifies two unmet requirements: conflicting model assessments of a disputed claim are reconciled against evidence and a classifier avoids marking uncertain cases as confirmed violations. Select TWO actions that remedy those particular deficiencies.
- resolve the dispute against cited source evidence rather than majority vote
- define explicit positive evidence and an abstain or review category
- select whichever answer appears in the most generated responses
- tell the model to flag anything that sounds suspicious
Explanation
Correct Answers
A:For an insurance document extraction agent, independent verification distinguishes a well-grounded minority view from shared guessing, which directly establishes that conflicting model assessments of a disputed claim are reconciled against evidence; the separate requirement that a classifier avoids marking uncertain cases as confirmed violations is handled by a different action.
B:For an insurance document extraction agent, clear decision thresholds separate direct evidence from weak similarity, which directly establishes that a classifier avoids marking uncertain cases as confirmed violations; the separate requirement that conflicting model assessments of a disputed claim are reconciled against evidence is handled by a different action.
Incorrect Answers
C:For an insurance document extraction agent, agreement among models is not a substitute for factual grounding, so this option cannot establish that conflicting model assessments of a disputed claim are reconciled against evidence; correctly addressing a classifier avoids marking uncertain cases as confirmed violations elsewhere does not repair that deficiency.
D:For an insurance document extraction agent, vague semantic similarity raises false positives, so this option cannot establish that a classifier avoids marking uncertain cases as confirmed violations; correctly addressing conflicting model assessments of a disputed claim are reconciled against evidence elsewhere does not repair that deficiency.
Question 672
A team operating a typed API generator project wants to establish two separate behaviors: long project guidance is divided into maintainable source files; in addition, the repository assistant discovers filenames matching a pattern. Which plan implements both?
- use CLAUDE.md imports to organize referenced instructions; and use Glob to locate candidate paths
- duplicate full instruction paragraphs in every directory; and use Glob to locate candidate paths
- use CLAUDE.md imports to organize referenced instructions; and search entire file contents with Grep to find paths by naming pattern
- duplicate full instruction paragraphs in every directory; and search entire file contents with Grep to find paths by naming pattern
Explanation
Correct Answer
A:In a typed API generator project, modular imports keep a short entry point while preserving reviewed details in separate files; alongside this, path globbing finds files by names and directory structure before content inspection, satisfying the distinct requirements that long project guidance is divided into maintainable source files and that the repository assistant discovers filenames matching a pattern.
Incorrect Answers
B:In a typed API generator project, path globbing finds files by names and directory structure before content inspection, but copying guidance encourages drift when policies change; therefore the separate requirement that long project guidance is divided into maintainable source files would remain unsatisfied.
C:In a typed API generator project, modular imports keep a short entry point while preserving reviewed details in separate files, but content search answers a different question and may miss empty files; therefore the separate requirement that the repository assistant discovers filenames matching a pattern would remain unsatisfied.
D:In a typed API generator project, copying guidance encourages drift when policies change and content search answers a different question and may miss empty files; the design would fail both conditions: long project guidance is divided into maintainable source files and the repository assistant discovers filenames matching a pattern.
Question 673
In a technical review of a policy document normalization service, the architect must address the following constraints together: ambiguous write timeouts do not trigger duplicate side effects; an ambiguous item is separated from routine automation. Which change set is most defensible?
- check operation status or use an idempotency key before retry; and put uncertain cases in an explicit review queue with priority and context
- implement only check operation status or use an idempotency key before retry; make no corresponding change for the second requirement
- repeat the mutation immediately because no success message arrived; and put uncertain cases in an explicit review queue with priority and context
- repeat the mutation immediately because no success message arrived; and automatically approve any case not rejected immediately
- check operation status or use an idempotency key before retry; and automatically approve any case not rejected immediately
Explanation
Correct Answer
A:In a policy document normalization service, a timeout can occur after the server commits the action, so retry safety needs state checks; alongside this, triage preserves unattended processing for low-risk cases while catching exceptions, satisfying the distinct requirements that ambiguous write timeouts do not trigger duplicate side effects and that an ambiguous item is separated from routine automation.
Incorrect Answers
B:In a policy document normalization service, a timeout can occur after the server commits the action, so retry safety needs state checks, but the independent mechanism for the other criterion is absent: triage preserves unattended processing for low-risk cases while catching exceptions; as written, the design does not ensure that an ambiguous item is separated from routine automation.
C:In a policy document normalization service, triage preserves unattended processing for low-risk cases while catching exceptions, but missing acknowledgment does not prove the first write was rolled back; therefore the separate requirement that ambiguous write timeouts do not trigger duplicate side effects would remain unsatisfied.
D:In a policy document normalization service, missing acknowledgment does not prove the first write was rolled back and absence of a prompt rejection is not affirmative evidence; the design would fail both conditions: ambiguous write timeouts do not trigger duplicate side effects and an ambiguous item is separated from routine automation.
E:In a policy document normalization service, a timeout can occur after the server commits the action, so retry safety needs state checks, but absence of a prompt rejection is not affirmative evidence; therefore the separate requirement that an ambiguous item is separated from routine automation would remain unsatisfied.
Question 674
A pull-request automation can force a tool choice only where supported, but execution still requires authorization; separately, long project guidance needs maintainable modular files. Choose TWO controls that address authorization and instruction management.
- treat a forced tool choice as equivalent to user approval
- use CLAUDE.md imports to organize referenced instructions
- duplicate full instruction paragraphs in every directory
- combine tool_choice with server-side policy checks
Explanation
Correct Answers
B:For a pull-request review pipeline, modular imports keep a short entry point while preserving reviewed details in separate files, which directly establishes that long project guidance is divided into maintainable source files; the separate requirement that a forced tool call still honors business authorization is handled by a different action.
D:For a pull-request review pipeline, selection controls when a tool is proposed but does not grant permission to execute, which directly establishes that a forced tool call still honors business authorization; the separate requirement that long project guidance is divided into maintainable source files is handled by a different action.
Incorrect Answers
A:For a pull-request review pipeline, tool selection and authorization are different controls, so this option cannot establish that a forced tool call still honors business authorization; correctly addressing long project guidance is divided into maintainable source files elsewhere does not repair that deficiency.
C:For a pull-request review pipeline, copying guidance encourages drift when policies change, so this option cannot establish that long project guidance is divided into maintainable source files; correctly addressing a forced tool call still honors business authorization elsewhere does not repair that deficiency.
Question 675
While preparing a competitive benchmarking pipeline for deployment, engineers must ensure that conflicting model assessments of a disputed claim are reconciled against evidence; they must also ensure that a classification uses a limited approved category set. Which combination best satisfies those requirements?
- select whichever answer appears in the most generated responses; and allow a free-form category for each case
- resolve the dispute against cited source evidence rather than majority vote; and define precise output labels and mapping rules
- resolve the dispute against cited source evidence rather than majority vote; and allow a free-form category for each case
- select whichever answer appears in the most generated responses; and define precise output labels and mapping rules
- implement only resolve the dispute against cited source evidence rather than majority vote; make no corresponding change for the second requirement
Explanation
Correct Answer
B:In a competitive benchmarking pipeline, independent verification distinguishes a well-grounded minority view from shared guessing; alongside this, controlled categories reduce schema drift and make downstream analytics comparable, satisfying the distinct requirements that conflicting model assessments of a disputed claim are reconciled against evidence and that a classification uses a limited approved category set.
Incorrect Answers
A:In a competitive benchmarking pipeline, agreement among models is not a substitute for factual grounding and unbounded labels fragment the intended taxonomy; the design would fail both conditions: conflicting model assessments of a disputed claim are reconciled against evidence and a classification uses a limited approved category set.
C:In a competitive benchmarking pipeline, independent verification distinguishes a well-grounded minority view from shared guessing, but unbounded labels fragment the intended taxonomy; therefore the separate requirement that a classification uses a limited approved category set would remain unsatisfied.
D:In a competitive benchmarking pipeline, controlled categories reduce schema drift and make downstream analytics comparable, but agreement among models is not a substitute for factual grounding; therefore the separate requirement that conflicting model assessments of a disputed claim are reconciled against evidence would remain unsatisfied.
E:In a competitive benchmarking pipeline, independent verification distinguishes a well-grounded minority view from shared guessing, but the independent mechanism for the other criterion is absent: controlled categories reduce schema drift and make downstream analytics comparable; as written, the design does not ensure that a classification uses a limited approved category set.
Question 676
Tests for a release-triage developer agent will pass only if independent research branches can finish without waiting on one another and if a selector accepts only supported operation names. Which proposed design directly satisfies both checks?
- dispatch the independent branches concurrently through the coordinator; and declare an operation enum in the schema and reject values outside it in the tool handler
- chain every research agent in a fixed serial pipeline; and declare an operation enum in the schema and reject values outside it in the tool handler
- dispatch the independent branches concurrently through the coordinator; and ask the model to invent a suitable action string
- chain every research agent in a fixed serial pipeline; and ask the model to invent a suitable action string
Explanation
Correct Answer
A:In a release-triage developer agent, parallel delegation reduces latency when individual investigations do not consume each other's outputs; alongside this, schema constraints guide valid selections and runtime validation blocks unsupported operation values, satisfying the distinct requirements that independent research branches can finish without waiting on one another and that a selector accepts only supported operation names.
Incorrect Answers
B:In a release-triage developer agent, schema constraints guide valid selections and runtime validation blocks unsupported operation values, but unnecessary sequential handoffs increase latency for independent subtasks; therefore the separate requirement that independent research branches can finish without waiting on one another would remain unsatisfied.
C:In a release-triage developer agent, parallel delegation reduces latency when individual investigations do not consume each other's outputs, but free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist; therefore the separate requirement that a selector accepts only supported operation names would remain unsatisfied.
D:In a release-triage developer agent, unnecessary sequential handoffs increase latency for independent subtasks and free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist; the design would fail both conditions: independent research branches can finish without waiting on one another and a selector accepts only supported operation names.
Question 677
Before expanding a monorepo feature modernization project, the owner must demonstrate that a long workflow preserves confirmed facts separately from speculation, while also demonstrating that the repository assistant discovers filenames matching a pattern. Which design provides both controls?
- combine guesses and verified attributes in one unqualified summary; and search entire file contents with Grep to find paths by naming pattern
- mark verified, user-reported, and unknown state explicitly; and search entire file contents with Grep to find paths by naming pattern
- mark verified, user-reported, and unknown state explicitly; and use Glob to locate candidate paths
- combine guesses and verified attributes in one unqualified summary; and use Glob to locate candidate paths
Explanation
Correct Answer
C:In a monorepo feature modernization project, epistemic labels stop a tentative suggestion becoming a confirmed action parameter; alongside this, path globbing finds files by names and directory structure before content inspection, satisfying the distinct requirements that a long workflow preserves confirmed facts separately from speculation and that the repository assistant discovers filenames matching a pattern.
Incorrect Answers
A:In a monorepo feature modernization project, downstream operations may rely on an assumption as though it were checked and content search answers a different question and may miss empty files; the design would fail both conditions: a long workflow preserves confirmed facts separately from speculation and the repository assistant discovers filenames matching a pattern.
B:In a monorepo feature modernization project, epistemic labels stop a tentative suggestion becoming a confirmed action parameter, but content search answers a different question and may miss empty files; therefore the separate requirement that the repository assistant discovers filenames matching a pattern would remain unsatisfied.
D:In a monorepo feature modernization project, path globbing finds files by names and directory structure before content inspection, but downstream operations may rely on an assumption as though it were checked; therefore the separate requirement that a long workflow preserves confirmed facts separately from speculation would remain unsatisfied.
Question 678
In a technical review of a document field validation service, the architect must address the following constraints together: an extractor always returns the identifiers required by downstream code; policy decisions use measurable conditions rather than tone. Which change set is most defensible?
- treat every identifier as an optional free-form note; and ask the model to use its general intuition about severity
- declare mandatory schema fields in the required list; and describe exact observable triggers and exception rules
- treat every identifier as an optional free-form note; and describe exact observable triggers and exception rules
- declare mandatory schema fields in the required list; and ask the model to use its general intuition about severity
Explanation
Correct Answer
B:In a document field validation service, required properties prevent accidental omission of key attributes; alongside this, operationalized criteria reduce disagreement across similar inputs, satisfying the distinct requirements that an extractor always returns the identifiers required by downstream code and that policy decisions use measurable conditions rather than tone.
Incorrect Answers
A:In a document field validation service, the consumer cannot reliably rely on a field that may be omitted and unquantified intuition varies between cases and reviewers; the design would fail both conditions: an extractor always returns the identifiers required by downstream code and policy decisions use measurable conditions rather than tone.
C:In a document field validation service, operationalized criteria reduce disagreement across similar inputs, 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 document field validation service, required properties prevent accidental omission of key attributes, but unquantified intuition varies between cases and reviewers; therefore the separate requirement that policy decisions use measurable conditions rather than tone would remain unsatisfied.
Question 679
During review of a contract clause extraction workflow, an unmet criterion states that conflicting sources are not silently flattened into one answer. Which measure resolves this specific gap?
- report the disagreement and explain evidence quality or recency
- express the uncertainty and identify what verification is missing
- carry citation identifiers and retrieval context through synthesis
- choose one assertion and omit the contradiction without investigation
Explanation
Correct Answer
A:For a contract clause extraction workflow, explicit conflicts preserve uncertainty rather than manufacturing unanimity; this directly establishes that conflicting sources are not silently flattened into one answer instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although calibrated language communicates a bounded evidence gap honestly, that only supports the distinct goal that an unresolved claim is qualified without inventing certainty, not the requirement that conflicting sources are not silently flattened into one answer in a contract clause extraction workflow.
C:Although provenance metadata must remain attached when intermediate summaries are merged, that only supports the distinct goal that source identity survives multi-agent research handoffs, not the requirement that conflicting sources are not silently flattened into one answer in a contract clause extraction workflow.
D:In a contract clause extraction workflow, suppressed disagreement creates false confidence; as a result, the stated requirement that conflicting sources are not silently flattened into one answer would still not be met.
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.