Question 560
Before expanding a multi-source competitor research system, the owner must demonstrate that a high-risk result passes deterministic checks in addition to model critique, while also demonstrating that a delegated reviewer has no production write capability. Which design provides both controls?
- replace all validation checks with a second model's opinion; and provide only the read-oriented tools required by that reviewer
- combine independent review with schema and business-rule validation; and give the reviewer every administrative tool and ask for restraint
- combine independent review with schema and business-rule validation; and provide only the read-oriented tools required by that reviewer
- replace all validation checks with a second model's opinion; and give the reviewer every administrative tool and ask for restraint
Explanation
Correct Answer
C:In a multi-source competitor research system, a critique may improve quality but cannot enforce machine-testable invariants by itself; alongside this, agent-scoped tool exposure prevents a write path in a read-only role, satisfying the distinct requirements that a high-risk result passes deterministic checks in addition to model critique and that a delegated reviewer has no production write capability.
Incorrect Answers
A:In a multi-source competitor research system, agent-scoped tool exposure prevents a write path in a read-only role, but probabilistic agreement does not guarantee compliance; therefore the separate requirement that a high-risk result passes deterministic checks in addition to model critique would remain unsatisfied.
B:In a multi-source competitor research system, a critique may improve quality but cannot enforce machine-testable invariants by itself, but prompt restraint is weaker than withholding execution capability; therefore the separate requirement that a delegated reviewer has no production write capability would remain unsatisfied.
D:In a multi-source competitor research system, probabilistic agreement does not guarantee compliance and prompt restraint is weaker than withholding execution capability; the design would fail both conditions: a high-risk result passes deterministic checks in addition to model critique and a delegated reviewer has no production write capability.
Question 561
During review of an automated CI review service, an unmet criterion states that the CI parser receives predictable machine-readable Claude output. Which measure resolves this specific gap?
- use the CLI structured-output schema option for the response
- request the CLI JSON output format and parse its documented structure
- run Claude Code in non-interactive print mode with -p
- scrape a human-oriented terminal transcript with regular expressions
- persist structured errors, relevant logs, and a bounded diagnostic summary
Explanation
Correct Answer
B:For an automated CI review service, machine-readable envelopes avoid brittle extraction from colored console prose; this directly establishes that the CI parser receives predictable machine-readable Claude output instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although schema-constrained output is more robust for downstream integrations than prompt-only formatting, that only supports the distinct goal that an automation expects a defined JSON result schema, not the requirement that the CI parser receives predictable machine-readable Claude output in an automated CI review service.
C:Although headless invocation permits scripted automation and exits after the requested task, that only supports the distinct goal that a CI job invokes Claude without a terminal conversation, not the requirement that the CI parser receives predictable machine-readable Claude output in an automated CI review service.
D:In an automated CI review service, presentation formatting can change and break the parser; as a result, the stated requirement that the CI parser receives predictable machine-readable Claude output would still not be met.
E:Although stable artifacts help maintainers reproduce the problem without rerunning a chat, that only supports the distinct goal that CI failures provide actionable evidence to maintainers, not the requirement that the CI parser receives predictable machine-readable Claude output in an automated CI review service.
Question 562
In a CLI application maintenance task, the engineering team must guarantee that a source change is validated against the right dependency chain. What is the most appropriate control?
- review only the edited line with no caller context
- discover paths using Glob before reading contents
- read targeted code ranges and nearby dependencies
- trace imports and call sites from the touched module outward
Explanation
Correct Answer
D:For a CLI application maintenance task, dependency-focused exploration spots affected behavior without indiscriminate reading; this directly establishes that a source change is validated against the right dependency chain instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a CLI application maintenance task, local correctness may miss consumers that rely on the old behavior; as a result, the stated requirement that a source change is validated against the right dependency chain 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 a source change is validated against the right dependency chain in a CLI application maintenance task.
C:Although focused inspection preserves exact implementation detail without loading the whole codebase, that only supports the distinct goal that the developer inspects a suspicious implementation in context, not the requirement that a source change is validated against the right dependency chain in a CLI application maintenance task.
Question 563
An audit of a code-reference retrieval assistant identifies two unmet requirements: secrets are not embedded in a shared MCP setup and only one approved write tool is callable in a sensitive stage. Select TWO actions that remedy those particular deficiencies.
- let the model select from a broad global list of tools
- place long-lived access tokens directly in .mcp.json
- restrict the stage's allowed tool set and verify permissions in the executor
- inject credentials through approved environment or secret-management mechanisms
Explanation
Correct Answers
C:For a code-reference retrieval assistant, capability scoping narrows possible side effects before model selection, which directly establishes that only one approved write tool is callable in a sensitive stage; the separate requirement that secrets are not embedded in a shared MCP setup is handled by a different action.
D:For a code-reference retrieval assistant, separating credentials from versioned configuration limits accidental disclosure, which directly establishes that secrets are not embedded in a shared MCP setup; the separate requirement that only one approved write tool is callable in a sensitive stage is handled by a different action.
Incorrect Answers
A:For a code-reference retrieval assistant, excess capabilities create avoidable routing and authorization risk, so this option cannot establish that only one approved write tool is callable in a sensitive stage; correctly addressing secrets are not embedded in a shared MCP setup elsewhere does not repair that deficiency.
B:For a code-reference retrieval assistant, repository history can expose tokens to everyone with code access, so this option cannot establish that secrets are not embedded in a shared MCP setup; correctly addressing only one approved write tool is callable in a sensitive stage elsewhere does not repair that deficiency.
Question 564
In a claims form processing assistant, the design must ensure that a classification uses a limited approved category set and that offline extraction cost is controlled without missing a service-level deadline. Choose TWO independent changes that directly meet these two requirements.
- allow a free-form category for each case
- select the lowest-cost async path even for strict real-time actions
- define precise output labels and mapping rules
- compare batch turnaround with the workload's time requirements
Explanation
Correct Answers
C:For a claims form processing assistant, controlled categories reduce schema drift and make downstream analytics comparable, which directly establishes that a classification uses a limited approved category set; the separate requirement that offline extraction cost is controlled without missing a service-level deadline is handled by a different action.
D:For a claims form processing assistant, asynchronous savings are appropriate only when delayed completion is acceptable, which directly establishes that offline extraction cost is controlled without missing a service-level deadline; the separate requirement that a classification uses a limited approved category set is handled by a different action.
Incorrect Answers
A:For a claims form processing assistant, unbounded labels fragment the intended taxonomy, so this option cannot establish that a classification uses a limited approved category set; correctly addressing offline extraction cost is controlled without missing a service-level deadline elsewhere does not repair that deficiency.
B:For a claims form processing assistant, meeting a live deadline can matter more than per-request savings, so this option cannot establish that offline extraction cost is controlled without missing a service-level deadline; correctly addressing a classification uses a limited approved category set elsewhere does not repair that deficiency.
Question 565
For a customs paperwork processor, a reviewer identifies two independent obligations: partial completion of a multi-step operation is handled safely and each tool interface has a single clear operation boundary. Which proposal should be approved?
- track individual stage outcomes and use explicit recovery or compensating actions; and use a single universal tool that infers read versus write from prose
- track individual stage outcomes and use explicit recovery or compensating actions; and separate read-only lookup from side-effecting update interfaces
- treat the first successful tool call as proof that the entire workflow succeeded; and use a single universal tool that infers read versus write from prose
- treat the first successful tool call as proof that the entire workflow succeeded; and separate read-only lookup from side-effecting update interfaces
Explanation
Correct Answer
B:In a customs paperwork processor, an orchestrated workflow must not report overall success while a required step failed; alongside this, clear operation boundaries support least privilege and understandable approvals, satisfying the distinct requirements that partial completion of a multi-step operation is handled safely and that each tool interface has a single clear operation boundary.
Incorrect Answers
A:In a customs paperwork processor, an orchestrated workflow must not report overall success while a required step failed, but overloading hides effects and makes execution review harder; therefore the separate requirement that each tool interface has a single clear operation boundary would remain unsatisfied.
C:In a customs paperwork processor, later actions can fail after an earlier side effect and overloading hides effects and makes execution review harder; the design would fail both conditions: partial completion of a multi-step operation is handled safely and each tool interface has a single clear operation boundary.
D:In a customs paperwork processor, clear operation boundaries support least privilege and understandable approvals, 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.
Question 566
When designing an order-cancellation service, the requirement is not satisfied unless a status field can contain only approved business states and a synthesized statement can be traced to its supporting source. Which implementation addresses the two independent conditions?
- accept any model-generated status description; and attach source IDs and relevant excerpts to individual claims
- accept any model-generated status description; and publish a source list detached from the statements it supports
- enforce the approved status enum with structured output and validate it in the consumer; and attach source IDs and relevant excerpts to individual claims
- enforce the approved status enum with structured output and validate it in the consumer; and publish a source list detached from the statements it supports
Explanation
Correct Answer
C:In an order-cancellation service, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values; alongside this, claim-level provenance enables an auditor to verify each assertion, satisfying the distinct requirements that a status field can contain only approved business states and that a synthesized statement can be traced to its supporting source.
Incorrect Answers
A:In an order-cancellation service, claim-level provenance enables an auditor to verify each assertion, but free-form status phrases can violate a fixed business-state contract; therefore the separate requirement that a status field can contain only approved business states would remain unsatisfied.
B:In an order-cancellation service, free-form status phrases can violate a fixed business-state contract and a bibliography alone does not show which evidence backs each claim; the design would fail both conditions: a status field can contain only approved business states and a synthesized statement can be traced to its supporting source.
D:In an order-cancellation service, a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, but a bibliography alone does not show which evidence backs each claim; therefore the separate requirement that a synthesized statement can be traced to its supporting source would remain unsatisfied.
Question 567
Before expanding an engineering knowledge assistant, the owner must demonstrate that the model can use a tool result in its next decision, while also demonstrating that a team shares a repository-specific MCP server configuration. Which design provides both controls?
- put the tool output only in application logs; and configure each contributor's personal MCP registry manually
- put the tool output only in application logs; and commit a reviewed project .mcp.json without credentials
- append the assistant tool-use response and matching user tool_result blocks to history; and configure each contributor's personal MCP registry manually
- append the assistant tool-use response and matching user tool_result blocks to history; and commit a reviewed project .mcp.json without credentials
Explanation
Correct Answer
D:In an engineering knowledge assistant, Claude needs the prior request and the execution output in the conversation for the next inference; alongside this, project-scoped configuration can be distributed with the repository while keeping secrets external, satisfying the distinct requirements that the model can use a tool result in its next decision and that a team shares a repository-specific MCP server configuration.
Incorrect Answers
A:In an engineering knowledge assistant, unseen logs cannot inform the model's next decision and local personal settings do not create a reproducible team project setup; the design would fail both conditions: the model can use a tool result in its next decision and a team shares a repository-specific MCP server configuration.
B:In an engineering knowledge assistant, project-scoped configuration can be distributed with the repository while keeping secrets external, 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.
C:In an engineering knowledge assistant, Claude needs the prior request and the execution output in the conversation for the next inference, but local personal settings do not create a reproducible team project setup; therefore the separate requirement that a team shares a repository-specific MCP server configuration would remain unsatisfied.
Question 568
An audit of a continuous integration repair assistant asks how to make sure that a required validation step runs before the final response even when the model does not support forced tool choice. Which implementation should be selected?
- use automatic tool choice when a call is optional
- combine tool_choice with server-side policy checks
- enforce the validator in application control flow, using forced tool_choice only with compatible models
- rely on a prompt asking the model to call the validator
Explanation
Correct Answer
C:For a continuous integration repair assistant, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings; this directly establishes that a required validation step runs before the final response even when the model does not support forced tool choice instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although auto allows the model to answer directly when no external side effect or fresh data is needed, that only supports the distinct goal that a conversational task does not invoke tools needlessly, not the requirement that a required validation step runs before the final response even when the model does not support forced tool choice in a continuous integration repair assistant.
B:Although selection controls when a tool is proposed but does not grant permission to execute, that only supports the distinct goal that a forced tool call still honors business authorization, not the requirement that a required validation step runs before the final response even when the model does not support forced tool choice in a continuous integration repair assistant.
D:In a continuous integration repair assistant, prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions; as a result, the stated requirement that a required validation step runs before the final response even when the model does not support forced tool choice would still not be met.
Question 569
The release gate for a source-grounded policy synthesis service requires that the coordinator can identify which subagent produced a broken artifact; it also requires that a classifier avoids marking uncertain cases as confirmed violations. Which TWO actions meet the specified checks? Choose TWO.
- replace all nested errors with a generic coordinator failure
- define explicit positive evidence and an abstain or review category
- propagate task IDs, error codes, and correlation references
- tell the model to flag anything that sounds suspicious
Explanation
Correct Answers
B:For a source-grounded policy synthesis service, 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 the coordinator can identify which subagent produced a broken artifact is handled by a different action.
C:For a source-grounded policy synthesis service, tracing execution lineage helps route the incident to the right failing component, which directly establishes that the coordinator can identify which subagent produced a broken artifact; the separate requirement that a classifier avoids marking uncertain cases as confirmed violations is handled by a different action.
Incorrect Answers
A:For a source-grounded policy synthesis service, the original failing operation becomes opaque, so this option cannot establish that the coordinator can identify which subagent produced a broken artifact; correctly addressing a classifier avoids marking uncertain cases as confirmed violations elsewhere does not repair that deficiency.
D:For a source-grounded policy synthesis service, vague semantic similarity raises false positives, so this option cannot establish that a classifier avoids marking uncertain cases as confirmed violations; correctly addressing the coordinator can identify which subagent produced a broken artifact elsewhere does not repair that deficiency.
Question 570
The architect for a vendor onboarding document pipeline needs to ensure that a missing MCP capability is diagnosed before changing prompts. What should the team implement?
- verify server connection, transport, and exposed tool availability
- use a user-local MCP configuration rather than committing project configuration
- increase the system prompt length to compensate for disconnected tools
- review and approve project-scoped server configuration before connecting interactively
Explanation
Correct Answer
A:For a vendor onboarding document pipeline, tool discovery depends on a live configured integration, not just the prompt wording; this directly establishes that a missing MCP capability is diagnosed before changing prompts instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although user scope is appropriate for personal endpoints and avoids distributing local paths, that only supports the distinct goal that one developer keeps an MCP server private to their machine, not the requirement that a missing MCP capability is diagnosed before changing prompts in a vendor onboarding document pipeline.
C:In a vendor onboarding document pipeline, a model cannot call a capability absent from its available tool registry; as a result, the stated requirement that a missing MCP capability is diagnosed before changing prompts would still not be met.
D:Although interactive project trust checks limit execution of unfamiliar server commands and endpoints, that only supports the distinct goal that untrusted project MCP definitions receive approval in interactive Claude Code sessions, not the requirement that a missing MCP capability is diagnosed before changing prompts in a vendor onboarding document pipeline.