Question 690
For a supply-chain planning rollout, the proposed design uses Random audit of low-risk automation, relying on the claim that the control layer can sample approved outputs for independent periodic quality review. What enabling control must be in place to make that design enforceable?
- Verify identity-separated approval roles and tamper-evident logs
- Verify stratified audit plan and escalation thresholds
- Verify explicit side-effect classification and send permissions
- Verify queue retention, paging and explicit expiry policy
Explanation
Correct Answer
B:The prerequisite creates the necessary operating boundary: stratified audit plan and escalation thresholds. The system is intended to work because the control layer can sample approved outputs for independent periodic quality review. A release without that foundation may still suffer no-review automation can silently degrade after a distribution shift; use detected error rate and audit sampling coverage to evaluate the result.
Incorrect Answers
A:For the separate challenge where the same assistant could propose and approve high-impact access changes, the control layer can require a distinct authorized human or system role for approval; for this release, the team must first verify stratified audit plan and escalation thresholds.
C:For the separate challenge where a workflow can either draft a notice or send it to all customers, the control layer can require stronger approval before externally visible or irreversible steps; but the production dependency for Random audit of low-risk automation is stratified audit plan and escalation thresholds.
D:This prerequisite supports a method used when approval queues may be unattended overnight, because the control layer can hold or safely reject high-impact actions until review is complete; for this release, the team must first verify stratified audit plan and escalation thresholds.
Question 691
In a financial operations modernization project, a response confidently cites text that does not support the claim. Which approach best fits this specific operating constraint?
- Introduce Context truncation investigation
- Introduce Model capability mismatch test
- Introduce Retrieval recall diagnosis
- Introduce Unsupported-claim provenance analysis
- Introduce Tool-result integrity diagnosis
Explanation
Correct Answer
D:Under the stated constraints, the evaluation process can validate claim-to-span entailment rather than just link presence. That directly addresses the operational failure without relying on a generic prompt reminder. Production depends on source spans and expert claim verification; the result to monitor is unsupported claim rate by generation stage.
Incorrect Answers
A:When failures spike only when lengthy contracts include appendices, the evaluation process can inspect token budgets and the presence of decisive passages after packing; the current decision instead depends on a specific capability: the evaluation process can validate claim-to-span entailment rather than just link presence.
B:When complex cross-document inferences fail despite accurate retrieved passages, the evaluation process can evaluate a more capable tier on the same evidence and instructions; whereas the financial operations case must guard against the outcome that adding more citation markers can disguise hallucinations.
C:For a workload where generated answers omit a rule even though it exists in the knowledge base, the evaluation process can inspect whether relevant source passages reached the model; the missing operational behavior is specific: the evaluation process can validate claim-to-span entailment rather than just link presence.
E:For a workload where an agent selects correct tools but invents values absent from responses, the evaluation process can compare generated fields with raw tool result identifiers and values; whereas the financial operations case must guard against the outcome that adding more citation markers can disguise hallucinations.
Question 692
An operations analyst for travel operations must evaluate Sequential dependency-aware handoffs on real tasks. A test must detect whether parallelizing dependent tasks can validate stale or missing artifacts, even when outputs appear fluent. Which measure is appropriate?
- Audit rubric pass rate after a fixed maximum revision count
- Audit percentage of runs ending within declared budgets
- Audit prerequisite violations and successful handoff rate
- Audit cross-agent task completion without unauthorized tool calls
Explanation
Correct Answer
C:The correct signal is prerequisite violations and successful handoff rate; it must be computed for representative workloads and compared with a baseline. It checks whether the architecture can orchestrate a staged dependency graph with explicit prerequisites while surfacing the exposure that parallelizing dependent tasks can validate stale or missing artifacts.
Incorrect Answers
A:Where drafted release notes repeatedly miss mandatory restrictions, a relevant check would establish whether a separate evaluation pass checks defined criteria and requests capped revisions; by contrast, the supply-chain planning release needs evidence from prerequisite violations and successful handoff rate.
B:The proposed measure would suit a setting where a planner sometimes delegates recursively until requests time out, since the architecture can impose step, token, cost and time ceilings with explicit exit behavior; however, that proxy would not demonstrate prerequisite violations and successful handoff rate for the selected intervention.
D:When several specialists must cooperate without granting every one all tools, a supervisor assigns tasks and consolidates results within distinct permission scopes. A favorable result on that test would not establish prerequisite violations and successful handoff rate for this workflow, where a reviewer cannot assess a draft before verified citations are available; by contrast, the supply-chain planning release needs evidence from prerequisite violations and successful handoff rate.
Question 693
During technical sign-off for enterprise knowledge management, Hybrid lexical and semantic retrieval has been selected. The design premise is that the integration can combine keyword matches with embeddings and rank the merged results. Which enabling condition must be demonstrated before production traffic is allowed?
- Verify chunk-length experiment and duplicate suppression
- Verify parent-child mapping and document version IDs
- Verify synchronized lexical and vector indexes
- Verify source change events and reconciled index versions
Explanation
Correct Answer
C:Readiness depends on synchronized lexical and vector indexes, not just a design approval. That condition supports the mechanism in which the integration can combine keyword matches with embeddings and rank the merged results. Without it, semantic-only retrieval can miss exact identifiers while lexical-only misses paraphrases; monitoring recall on exact-code and paraphrase query subsets helps verify the deployed result.
Incorrect Answers
A:The setup is useful to enable the alternative's behavior where the integration can use measured overlap where splitting otherwise loses neighboring facts and factual statements often cross page or paragraph cut points; for this release, the team must first verify synchronized lexical and vector indexes.
B:The setup is useful to enable the alternative's behavior where the integration can search fine-grained chunks then return appropriate parent spans for grounding and short chunks are searchable but answers need full contractual sections; however, the named intervention needs synchronized lexical and vector indexes before its protection can be enforced.
D:The setup is useful to enable the alternative's behavior where the integration can synchronize create-update-delete events into the retrieval index and source policies change daily and retired versions must stop appearing; for this release, the team must first verify synchronized lexical and vector indexes.
Question 694
The logistics coordination staging review finds that end-to-end unattended merging removes an independent quality gate. Which design intervention is the most appropriate corrective action?
- Deploy Change provenance for agent edits
- Deploy Test-first agent change workflow
- Deploy Incremental refactoring checkpoints
- Deploy Parallel code-review assistance
- Deploy Bounded issue-to-patch automation
Explanation
Correct Answer
E:This intervention addresses the failure at its source because the engineering workflow can allow an agent to propose a patch and tests within a restricted repository scope. To keep the issue from recurring, establish issue reproduction, scoped permissions and merge protection and verify accepted patches without policy or test regressions; otherwise end-to-end unattended merging removes an independent quality gate can persist.
Incorrect Answers
A:Where release teams cannot tell why generated modifications were proposed, the engineering workflow can attach issue links, tests, diff summaries and reviewer approvals to patches; yet it would not correct the observed weakness: end-to-end unattended merging removes an independent quality gate.
B:Where agents generate plausible code that breaks existing behavior, the engineering workflow can require narrow changes with executable tests and review before merge; but this remedy operates on another boundary, not the case where end-to-end unattended merging removes an independent quality gate.
C:The alternative reduces the risk that a single sweeping rewrite is hard to validate and roll back because the engineering workflow can split refactors into reversible, individually tested commits; however, the logistics coordination defect follows the path in which end-to-end unattended merging removes an independent quality gate.
D:Where multiple quality concerns need independent assessment of a large change, the engineering workflow can run security, maintainability and API compatibility reviews separately; yet it would not correct the observed weakness: end-to-end unattended merging removes an independent quality gate.
Question 695
After installing Deterministic external computation in an enterprise knowledge management workflow, the team must validate whether it has reduced the exposure that free-form numeric reasoning can introduce avoidable calculation mistakes. Which measurement is most relevant?
- Evaluate required-criterion coverage per reviewed response
- Evaluate exact numeric pass rate across boundary values
- Evaluate held-out field accuracy with minimal prompt tokens
- Evaluate intermediate-step correctness and final consistency
Explanation
Correct Answer
B:The acceptance measure focuses on exact numeric pass rate across boundary values at the task or workflow boundary. Model fluency would not establish whether the model configuration can use code or a trusted service for calculations and Claude for interpretation, and it could conceal cases where free-form numeric reasoning can introduce avoidable calculation mistakes.
Incorrect Answers
A:When a compliance analysis skips one mandatory risk consideration, the model configuration can require a concise explicit checklist of required criteria before final output; by contrast, the enterprise knowledge management release needs evidence from exact numeric pass rate across boundary values.
C:When a well-defined extraction task has clear field names, no ambiguous labels and the model configuration can start with concise instructions before adding demonstrations that consume context; but the acceptance gate must instead inspect exact numeric pass rate across boundary values to detect the targeted failure.
D:The alternative indicator checks whether the model configuration can compute verifiable components separately before final synthesis when a negotiation report contains independent arithmetic and contractual judgments; by contrast, the enterprise knowledge management release needs evidence from exact numeric pass rate across boundary values.
Question 696
An enterprise knowledge management service owner is reviewing Service-tier differentiation after a canary rollout. The critical regression would occur if a single SLA overcommits low-priority work or underprotects critical flows. What observable acceptance signal belongs in the dashboard?
- Measure issue reports tied to uncommunicated changes
- Measure accepted task completion inside latency targets
- Measure SLA compliance by request tier under load
- Measure actionable bug reports and time to reproduce
- Measure escalation acknowledgment time by severity
Explanation
Correct Answer
C:Tracking sLA compliance by request tier under load provides direct evidence that the system delivers its intended effect: the delivery team can commit separate targets and fallback behaviors by priority class. The measure is more informative than prompt counts because the failure being measured is that a single SLA overcommits low-priority work or underprotects critical flows.
Incorrect Answers
A:Where prompt improvements can alter user-visible behavior without a UI release, a relevant check would establish whether the delivery team can announce consequential changes, effective dates and rollback contacts; however, that proxy would not demonstrate sLA compliance by request tier under load for the selected intervention.
B:The proposed measure would suit a setting where a service meets infrastructure uptime targets while its answers remain unusable, since the delivery team can specify user-observable success such as validated resolutions and response time; but the acceptance gate must instead inspect sLA compliance by request tier under load to detect the targeted failure.
D:The proposed measure would suit a setting where users report problems through scattered chats with no reproduction details, since the delivery team can capture task type, evidence, severity and version in one feedback queue; however, that proxy would not demonstrate sLA compliance by request tier under load for the selected intervention.
E:Where users do not know whom to call when generated advice causes harm, a relevant check would establish whether the delivery team can map severity levels to operational, security and business response roles; but the acceptance gate must instead inspect sLA compliance by request tier under load to detect the targeted failure.
Question 697
The research administration release team needs a numerical gate for Random audit of low-risk automation. Rather than equating deployment with success, it wants to catch cases in which no-review automation can silently degrade after a distribution shift. Which indicator should it track?
- Track severe error escape rate and review workload by tier
- Track unauthorized external dispatch rate during staging tests
- Track self-approved mutation attempts prevented
- Track detected error rate and audit sampling coverage
Explanation
Correct Answer
D:The correct signal is detected error rate and audit sampling coverage; it must be computed for representative workloads and compared with a baseline. It checks whether the control layer can sample approved outputs for independent periodic quality review while surfacing the exposure that no-review automation can silently degrade after a distribution shift.
Incorrect Answers
A:The alternative indicator checks whether the control layer can send consequential actions to authorized reviewers while allowing bounded automation elsewhere when low-risk drafts are common but a few decisions affect legal entitlements; but the acceptance gate must instead inspect detected error rate and audit sampling coverage to detect the targeted failure.
B:The proposed measure would suit a setting where a workflow can either draft a notice or send it to all customers, since the control layer can require stronger approval before externally visible or irreversible steps; by contrast, the research administration release needs evidence from detected error rate and audit sampling coverage.
C:When the same assistant could propose, approve high-impact access changes and the control layer can require a distinct authorized human or system role for approval; however, that proxy would not demonstrate detected error rate and audit sampling coverage for the selected intervention.
Question 698
The solution design for travel operations assumes that the evaluation process can validate claim-to-span entailment rather than just link presence. Before treating Unsupported-claim provenance analysis as production-ready, which dependency needs an owner and verification?
- Arrange serialized prompt capture with redaction
- Arrange paired cases with verified evidence
- Arrange query-to-source relevance labels
- Arrange source spans and expert claim verification
- Arrange clean holdout examples and example selection log
Explanation
Correct Answer
D:What makes the control operable is source spans and expert claim verification. It supplies the precondition for the mechanism whereby the evaluation process can validate claim-to-span entailment rather than just link presence. The residual failure to guard against is that adding more citation markers can disguise hallucinations, measured through unsupported claim rate by generation stage.
Incorrect Answers
A:The setup is useful to enable the alternative's behavior where the evaluation process can inspect token budgets and the presence of decisive passages after packing and failures spike only when lengthy contracts include appendices; but the production dependency for Unsupported-claim provenance analysis is source spans and expert claim verification.
B:Where complex cross-document inferences fail despite accurate retrieved passages, the evaluation process can evaluate a more capable tier on the same evidence and instructions; for this release, the team must first verify source spans and expert claim verification.
C:The setup is useful to enable the alternative's behavior where the evaluation process can inspect whether relevant source passages reached the model and generated answers omit a rule even though it exists in the knowledge base; however, the named intervention needs source spans and expert claim verification before its protection can be enforced.
E:Where a few-shot classifier works on familiar categories but fails novel wording, the evaluation process can test whether examples bias the model to surface patterns rather than policy rules; for this release, the team must first verify source spans and expert claim verification.
Question 699
A supply-chain planning release candidate fails review after assessors observe that parallelizing dependent tasks can validate stale or missing artifacts. What intervention should take priority?
- Apply Shared artifact contracts
- Apply Sequential dependency-aware handoffs
- Apply Budgeted orchestration stop policy
- Apply Independent critic with bounded revisions
Explanation
Correct Answer
B:The remediation acts at the relevant design boundary: the architecture can orchestrate a staged dependency graph with explicit prerequisites. That counteracts the observed hazard that parallelizing dependent tasks can validate stale or missing artifacts. Rollout should include structured handoff payloads and stage readiness checks, with regression evidence from prerequisite violations and successful handoff rate.
Incorrect Answers
A:When unconstrained natural-language handoffs lose provenance and state semantics, common schemas and immutable artifact versions make specialist outputs composable; whereas the supply-chain planning defect follows the path in which parallelizing dependent tasks can validate stale or missing artifacts.
C:Where a planner sometimes delegates recursively until requests time out, the architecture can impose step, token, cost and time ceilings with explicit exit behavior; but this remedy operates on another boundary, not the case where parallelizing dependent tasks can validate stale or missing artifacts.
D:When unbounded self-critique loops can raise cost without a convergence rule, a separate evaluation pass checks defined criteria and requests capped revisions; whereas the supply-chain planning defect follows the path in which parallelizing dependent tasks can validate stale or missing artifacts.
Question 700
A media licensing pilot has enabled Hybrid lexical and semantic retrieval. Because semantic-only retrieval can miss exact identifiers while lexical-only misses paraphrases, the release board wants evidence of effectiveness, not just a favorable demonstration. Which metric most directly tests the proposed control?
- Measure eligible-document retrieval precision after filtering
- Measure cross-boundary answer recall versus indexed token volume
- Measure time-to-index-freshness and stale-answer incidence
- Measure recall on exact-code and paraphrase query subsets
Explanation
Correct Answer
D:An appropriate gate measures recall on exact-code and paraphrase query subsets. It tests the mechanism in which the integration can combine keyword matches with embeddings and rank the merged results, rather than a cosmetic demonstration. That distinction matters because semantic-only retrieval can miss exact identifiers while lexical-only misses paraphrases.
Incorrect Answers
A:Where questions require filtering by jurisdiction and policy effective date, a relevant check would establish whether the integration can store reliable source metadata for filtering before similarity search; but the acceptance gate must instead inspect recall on exact-code and paraphrase query subsets to detect the targeted failure.
B:Where factual statements often cross page or paragraph cut points, a relevant check would establish whether the integration can use measured overlap where splitting otherwise loses neighboring facts; by contrast, the media licensing release needs evidence from recall on exact-code and paraphrase query subsets.
C:When source policies change daily, retired versions must stop appearing and the integration can synchronize create-update-delete events into the retrieval index; however, that proxy would not demonstrate recall on exact-code and paraphrase query subsets for the selected intervention.