Question 550
Engineers are splitting a data pipeline service into two independently tested functions. Function A must reject a malformed tool argument payload before calling a payroll service, while function B must activate a new tool execution path for only internal testers. Which plan is sound?
- First component: Validate JSON before deserialization. Second component: Use feature flags for risky behavior changes.
- First component: Separate integration tests from unit tests. Second component: Use pull requests and focused code review.
- First component: Use pull requests and focused code review. Second component: Use feature flags for risky behavior changes.
- First component: Validate JSON before deserialization. Second component: Separate integration tests from unit tests.
Explanation
Correct Answer
A:The first proposal fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects, while the second proposal fits its assigned role because runtime controls can segment rollout and permit quick disabling without a code rebuild; their respective acceptance criteria are to reject a malformed tool argument payload before calling a payroll service and to activate a new tool execution path for only internal testers.
Incorrect Answers
B:The first proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned first role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal serves the different purpose to detect unsafe permissions and schema changes before merging an agent tool instead of the assigned second role because peer review creates an explicit checkpoint for correctness, security, and maintainability; their respective acceptance criteria are to reject a malformed tool argument payload before calling a payroll service and to activate a new tool execution path for only internal testers.
C:The first proposal serves the different purpose to detect unsafe permissions and schema changes before merging an agent tool instead of the assigned first role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal fits its assigned role because runtime controls can segment rollout and permit quick disabling without a code rebuild; their respective acceptance criteria are to reject a malformed tool argument payload before calling a payroll service and to activate a new tool execution path for only internal testers.
D:The first proposal fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects, while the second proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned second role because integration tests exercise boundaries and serialization that isolated mocks may miss; their respective acceptance criteria are to reject a malformed tool argument payload before calling a payroll service and to activate a new tool execution path for only internal testers.
Question 551
A release plan for an agent governance platform has two acceptance checks: component one must capture which files an approved agent operation actually modified; component two must stop a coding agent from running a destructive deployment command before execution. Which proposal passes both?
- First component: Keep hook scripts under change control. Second component: Test hook input and exit handling.
- First component: Test hook input and exit handling. Second component: Use a pre-tool hook to deny dangerous commands.
- First component: Use a post-tool hook to record outcomes. Second component: Use a pre-tool hook to deny dangerous commands.
- First component: Use a post-tool hook to record outcomes. Second component: Keep hook scripts under change control.
Explanation
Correct Answer
C:The first proposal fits its assigned role because post-execution events are useful for audit, metrics, and follow-up checks once the tool has run, while the second proposal fits its assigned role because pre-execution interception provides a deterministic opportunity to reject a proposed tool call; their respective acceptance criteria are to capture which files an approved agent operation actually modified and to stop a coding agent from running a destructive deployment command before execution.
Incorrect Answers
A:The first proposal serves the different purpose to prevent an unnoticed local edit from disabling a team's protection of secret files instead of the assigned first role because versioning and review make guardrail behavior inspectable and reproducible, while the second proposal serves the different purpose to ensure a policy block is interpreted correctly by the Claude Code runtime instead of the assigned second role because hook contracts specify the event, supplied data, and supported control response; integration tests verify expected enforcement; their respective acceptance criteria are to capture which files an approved agent operation actually modified and to stop a coding agent from running a destructive deployment command before execution.
B:The first proposal serves the different purpose to ensure a policy block is interpreted correctly by the Claude Code runtime instead of the assigned first role because hook contracts specify the event, supplied data, and supported control response; integration tests verify expected enforcement, while the second proposal fits its assigned role because pre-execution interception provides a deterministic opportunity to reject a proposed tool call; their respective acceptance criteria are to capture which files an approved agent operation actually modified and to stop a coding agent from running a destructive deployment command before execution.
D:The first proposal fits its assigned role because post-execution events are useful for audit, metrics, and follow-up checks once the tool has run, while the second proposal serves the different purpose to prevent an unnoticed local edit from disabling a team's protection of secret files instead of the assigned second role because versioning and review make guardrail behavior inspectable and reproducible; their respective acceptance criteria are to capture which files an approved agent operation actually modified and to stop a coding agent from running a destructive deployment command before execution.
Question 552
A technical specification for a Claude application application assigns two jobs to separate modules: module A must require manual signoff when an AI-produced recommendation exceeds a financial threshold, and module B must ensure protected records are processed only in approved jurisdictions. Which two-part solution is appropriate?
- First component: Specify human-review triggers. Second component: Set an explicit data residency constraint.
- First component: Document functional acceptance criteria. Second component: Set an explicit data residency constraint.
- First component: Record nonfunctional latency targets. Second component: Document functional acceptance criteria.
- First component: Specify human-review triggers. Second component: Record nonfunctional latency targets.
Explanation
Correct Answer
A:The first proposal fits its assigned role because decision thresholds turn governance expectations into testable escalation rules, while the second proposal fits its assigned role because documented residency requirements inform cloud placement, logging, storage, and vendor selection; their respective acceptance criteria are to require manual signoff when an AI-produced recommendation exceeds a financial threshold and to ensure protected records are processed only in approved jurisdictions.
Incorrect Answers
B:The first proposal serves the different purpose to turn a vague request for an AI claims assistant into observable user actions and outputs instead of the assigned first role because acceptance criteria specify inputs, outputs, and successful behavior that can be tested before release, while the second proposal fits its assigned role because documented residency requirements inform cloud placement, logging, storage, and vendor selection; their respective acceptance criteria are to require manual signoff when an AI-produced recommendation exceeds a financial threshold and to ensure protected records are processed only in approved jurisdictions.
C:The first proposal serves the different purpose to decide between streaming and offline processing for a time-sensitive support assistant instead of the assigned first role because a measurable response-time objective constrains interaction design and infrastructure choices, while the second proposal serves the different purpose to turn a vague request for an AI claims assistant into observable user actions and outputs instead of the assigned second role because acceptance criteria specify inputs, outputs, and successful behavior that can be tested before release; their respective acceptance criteria are to require manual signoff when an AI-produced recommendation exceeds a financial threshold and to ensure protected records are processed only in approved jurisdictions.
D:The first proposal fits its assigned role because decision thresholds turn governance expectations into testable escalation rules, while the second proposal serves the different purpose to decide between streaming and offline processing for a time-sensitive support assistant instead of the assigned second role because a measurable response-time objective constrains interaction design and infrastructure choices; their respective acceptance criteria are to require manual signoff when an AI-produced recommendation exceeds a financial threshold and to ensure protected records are processed only in approved jurisdictions.
Question 553
A conversation design solution has parallel requirements with separate owners. Workstream one must prevent a specialist's exhaustive document scan from contaminating the coordinator's working context; workstream two must prevent outdated user preferences from being treated as current task instructions. Which combination meets both?
- First component: Use scoped subagent contexts. Second component: Reserve space for the model's output.
- First component: Compact completed task history. Second component: Separate long-term memory from active scratchpad.
- First component: Reserve space for the model's output. Second component: Compact completed task history.
- First component: Use scoped subagent contexts. Second component: Separate long-term memory from active scratchpad.
Explanation
Correct Answer
D:The first proposal fits its assigned role because isolated workers return concise findings while retaining intermediate detail within their own window, while the second proposal fits its assigned role because explicit storage and freshness rules govern what is retained and when it is reintroduced; their respective acceptance criteria are to prevent a specialist's exhaustive document scan from contaminating the coordinator's working context and to prevent outdated user preferences from being treated as current task instructions.
Incorrect Answers
A:The first proposal fits its assigned role because isolated workers return concise findings while retaining intermediate detail within their own window, while the second proposal serves the different purpose to avoid using the entire context budget on retrieved input before generating a response instead of the assigned second role because input assembly must leave room for the requested completion and any needed reasoning; their respective acceptance criteria are to prevent a specialist's exhaustive document scan from contaminating the coordinator's working context and to prevent outdated user preferences from being treated as current task instructions.
B:The first proposal serves the different purpose to let an assistant continue a long incident investigation without losing decisions instead of the assigned first role because a structured summary preserves established facts, pending work, and unresolved assumptions in fewer tokens, while the second proposal fits its assigned role because explicit storage and freshness rules govern what is retained and when it is reintroduced; their respective acceptance criteria are to prevent a specialist's exhaustive document scan from contaminating the coordinator's working context and to prevent outdated user preferences from being treated as current task instructions.
C:The first proposal serves the different purpose to avoid using the entire context budget on retrieved input before generating a response instead of the assigned first role because input assembly must leave room for the requested completion and any needed reasoning, while the second proposal serves the different purpose to let an assistant continue a long incident investigation without losing decisions instead of the assigned second role because a structured summary preserves established facts, pending work, and unresolved assumptions in fewer tokens; their respective acceptance criteria are to prevent a specialist's exhaustive document scan from contaminating the coordinator's working context and to prevent outdated user preferences from being treated as current task instructions.
Question 554
The owner of a workflow automation integration wants to explain why an agent modified a configuration during a failed automated release. Which proposal provides the required mechanism?
- Delegate narrow subtasks with a separate context
- Use event logs for tool actions
- Use a graceful fallback path
- Use an independent verifier step
Explanation
Correct Answer
B:Structured traces connect tool intent, arguments, results, and subsequent decisions for audit and replay; this behavior directly supports the need to explain why an agent modified a configuration during a failed automated release. A final chat summary omits the exact causal sequence.
Incorrect Answers
A:Each subagent can work in a bounded context and return a concise, verified artifact; despite being useful when a service must protect a coordinator's window from huge specialist tool outputs, it is not a solution to explain why an agent modified a configuration during a failed automated release; copying every intermediate trace into the parent inflates context and cost.
C:A bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; this applies to the different goal to keep a customer service application operating when an expensive specialist agent cannot complete, not the requirement to explain why an agent modified a configuration during a failed automated release; unbounded retries do not ensure eventual success.
D:When an application needs to detect mistakes in an agent-generated SQL migration before running it, a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors; the current capability must instead explain why an agent modified a configuration during a failed automated release, while asking the original agent whether it is correct is weaker than executable verification.
Question 555
A release plan for an agent governance platform has two acceptance checks: component one must reduce exposure of customer documents copied into application telemetry; component two must display generated customer notes safely in a browser. Which proposal passes both?
- First component: Apply retention limits to diagnostic logs. Second component: Use output escaping to prevent XSS.
- First component: Minimize personally identifiable information. Second component: Validate tool arguments server-side.
- First component: Apply retention limits to diagnostic logs. Second component: Minimize personally identifiable information.
- First component: Validate tool arguments server-side. Second component: Use output escaping to prevent XSS.
Explanation
Correct Answer
A:The first proposal fits its assigned role because data minimization and controlled retention reduce the duration and audience of sensitive log content, while the second proposal fits its assigned role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript; their respective acceptance criteria are to reduce exposure of customer documents copied into application telemetry and to display generated customer notes safely in a browser.
Incorrect Answers
B:The first proposal serves the different purpose to avoid transmitting unnecessary customer identifiers with a summarization request instead of the assigned first role because redaction and selective fields reduce exposure before data enters model or logging paths, while the second proposal serves the different purpose to block a generated database query that targets another tenant's records instead of the assigned second role because backend authorization checks must bind the requested operation to the caller's entitlements; their respective acceptance criteria are to reduce exposure of customer documents copied into application telemetry and to display generated customer notes safely in a browser.
C:The first proposal fits its assigned role because data minimization and controlled retention reduce the duration and audience of sensitive log content, while the second proposal serves the different purpose to avoid transmitting unnecessary customer identifiers with a summarization request instead of the assigned second role because redaction and selective fields reduce exposure before data enters model or logging paths; their respective acceptance criteria are to reduce exposure of customer documents copied into application telemetry and to display generated customer notes safely in a browser.
D:The first proposal serves the different purpose to block a generated database query that targets another tenant's records instead of the assigned first role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal fits its assigned role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript; their respective acceptance criteria are to reduce exposure of customer documents copied into application telemetry and to display generated customer notes safely in a browser.
Question 556
An incident investigation review requires two independent, explicitly defined outcomes: the first workstream must fix an agent loop that repeatedly requests the same lookup without using the returned data; a second must compare application behavior before and after a prompt or SDK change. Which TWO actions directly provide these capabilities? Choose TWO.
- Trace a missing tool_result
- Investigate a 400 invalid_request error
- Investigate a 401 authentication failure
- Replay a failing case with a fixed fixture
- Interpret max_tokens as a truncation cause
Explanation
Correct Answers
A:Inspecting message history and tool IDs reveals whether execution output reached the next model turn; this directly supports task 1 to fix an agent loop that repeatedly requests the same lookup without using the returned data, not the separate task or tasks to compare application behavior before and after a prompt or SDK change; blaming model reasoning first overlooks an integration-layer omission.
D:Recorded inputs and tool mocks isolate regressions from variable live data; this directly supports task 2 to compare application behavior before and after a prompt or SDK change, not the separate task or tasks to fix an agent loop that repeatedly requests the same lookup without using the returned data; an uncontrolled production retry can hide intermittent errors.
Incorrect Answers
B:Validation failures point to malformed inputs or unsupported parameters that must be corrected; this implements the different outcome to diagnose a request that fails consistently before generating any model output rather than the required tasks to fix an agent loop that repeatedly requests the same lookup without using the returned data and to compare application behavior before and after a prompt or SDK change, and backoff does not fix a structurally invalid payload, so it is not a direct solution to any of the assigned workstreams.
C:Authentication errors require checking credential validity and configuration; this implements the different outcome to restore an integration after an API key is revoked rather than the required tasks to fix an agent loop that repeatedly requests the same lookup without using the returned data and to compare application behavior before and after a prompt or SDK change, and a larger output-token budget cannot authenticate the caller, so it is not a direct solution to any of the assigned workstreams.
E:The stop reason indicates the generation budget was exhausted rather than the task being completed; this implements the different outcome to explain why a generated answer ends before a required final field rather than the required tasks to fix an agent loop that repeatedly requests the same lookup without using the returned data and to compare application behavior before and after a prompt or SDK change, and a valid parse of the partial prefix does not make the report complete, so it is not a direct solution to any of the assigned workstreams.
Question 557
A developer is reviewing alternatives for a tool integration feature that must let multiple compatible clients request a controlled shipment lookup. Which option is a defensible fit?
- Expose an MCP resource for reference content
- Use stdio for a local MCP process
- Use a remote HTTP transport for shared MCP access
- Expose an MCP tool for an external action
- Expose an MCP prompt template
Explanation
Correct Answer
D:MCP tools advertise callable operations with named parameters and schemas across client integrations; this behavior directly supports the need to let multiple compatible clients request a controlled shipment lookup. A resource intended only for reading context does not perform arbitrary commands.
Incorrect Answers
A:Resources provide identifiable data that clients can fetch for model context; this applies to the different goal to make a versioned product catalog available for read-oriented context retrieval, not the requirement to let multiple compatible clients request a controlled shipment lookup; treating static content as a privileged executable tool unnecessarily expands authority.
B:When an application needs to connect a desktop development tool to a trusted local server process, standard input and output transport is suitable for a client-managed local subprocess; the current capability must instead let multiple compatible clients request a controlled shipment lookup, while it is not a remotely addressable network service by itself.
C:An HTTP-based endpoint supports remotely hosted servers with authentication and network controls; the supported outcome is to serve approved tools to multiple distributed client environments, whereas this scenario requires the ability to let multiple compatible clients request a controlled shipment lookup; a local-only subprocess transport does not provide central network access.
E:Prompts describe reusable message templates or workflows offered by the server; despite being useful when a service must share a repeatable analyst workflow across supported clients, it is not a solution to let multiple compatible clients request a controlled shipment lookup; a prompt template does not itself execute a database update.
Question 558
A document processing review requires two independent, explicitly defined outcomes: the first workstream must prevent a Claude assistant from inventing account balances when it lacks current ledger data; a second must build an intake service that accepts scanned documents as well as typed text. Which TWO actions directly provide these capabilities? Choose TWO.
- Define input modalities and size bounds
- Document functional acceptance criteria
- Identify authoritative source systems
- Calculate expected traffic and concurrency
- Define failure and recovery objectives
Explanation
Correct Answers
A:Format, resolution, size, and throughput requirements determine preprocessing and model-call strategy; this directly supports task 2 to build an intake service that accepts scanned documents as well as typed text, not the separate task or tasks to prevent a Claude assistant from inventing account balances when it lacks current ledger data; assuming every input is plain text will fail at the ingestion boundary.
C:Source-of-truth mapping identifies which verified systems must supply facts and what freshness guarantees apply; this directly supports task 1 to prevent a Claude assistant from inventing account balances when it lacks current ledger data, not the separate task or tasks to build an intake service that accepts scanned documents as well as typed text; model inference is not a substitute for a transactional database.
Incorrect Answers
B:Acceptance criteria specify inputs, outputs, and successful behavior that can be tested before release; this implements the different outcome to turn a vague request for an AI claims assistant into observable user actions and outputs rather than the required tasks to build an intake service that accepts scanned documents as well as typed text and to prevent a Claude assistant from inventing account balances when it lacks current ledger data, and choosing a model first does not define what the application must accomplish, so it is not a direct solution to any of the assigned workstreams.
D:Workload assumptions drive rate-limit planning, queue capacity, and retry strategy; this implements the different outcome to provision an interactive application for peak seasonal traffic rather than the required tasks to build an intake service that accepts scanned documents as well as typed text and to prevent a Claude assistant from inventing account balances when it lacks current ledger data, and average request volume alone hides burst behavior, so it is not a direct solution to any of the assigned workstreams.
E:Availability, recovery time, and fallback behavior must be specified as measurable operational needs; this implements the different outcome to keep a regulated triage service usable during an upstream API outage rather than the required tasks to build an intake service that accepts scanned documents as well as typed text and to prevent a Claude assistant from inventing account balances when it lacks current ledger data, and a happy-path prototype misses behavior under dependency failures, so it is not a direct solution to any of the assigned workstreams.
Question 559
Before a model platform release, three separately owned tasks must be covered: one service must deliver tokens to a browser without maintaining a bidirectional command channel; another must prevent a background processor from overwhelming the upstream API during bursts; and a third must keep integration behavior aligned with a supported request contract. Which THREE choices directly address the stated tasks? Choose THREE.
- Choose SSE for one-way streamed responses
- Choose WebSockets for bidirectional realtime exchange
- Use direct HTTP REST integration for unsupported runtimes
- Send the correct API authentication header
- Send an API version header where required
- Honor server rate-limit signals
Explanation
Correct Answers
A:Server-sent events provide ordered server-to-client updates over an HTTP stream; this directly supports task 1 to deliver tokens to a browser without maintaining a bidirectional command channel, not the separate task or tasks to prevent a background processor from overwhelming the upstream API during bursts and to keep integration behavior aligned with a supported request contract; a WebSocket is not required solely to push a response as it arrives.
E:Explicit protocol versioning makes the caller's expected API semantics unambiguous; this directly supports task 3 to keep integration behavior aligned with a supported request contract, not the separate task or tasks to deliver tokens to a browser without maintaining a bidirectional command channel and to prevent a background processor from overwhelming the upstream API during bursts; relying on an arbitrary undocumented default is fragile.
F:Throttling and backoff work with provider limits rather than assuming infinite request capacity; this directly supports task 2 to prevent a background processor from overwhelming the upstream API during bursts, not the separate task or tasks to deliver tokens to a browser without maintaining a bidirectional command channel and to keep integration behavior aligned with a supported request contract; parallelism beyond quota can reduce successful throughput.
Incorrect Answers
B:Persistent two-way channels fit interactive event exchange where the client also sends messages during a session; this implements the different outcome to implement an interactive collaboration channel requiring messages in both directions rather than the required tasks to keep integration behavior aligned with a supported request contract and to prevent a background processor from overwhelming the upstream API during bursts and to deliver tokens to a browser without maintaining a bidirectional command channel, and standard response streaming alone is not a general bidirectional messaging protocol, so it is not a direct solution to any of the assigned workstreams.
C:A standards-based HTTP client can send JSON requests with the correct headers and decode responses; this implements the different outcome to call the Messages endpoint from a language without a mature provider SDK rather than the required tasks to keep integration behavior aligned with a supported request contract and to prevent a background processor from overwhelming the upstream API during bursts and to deliver tokens to a browser without maintaining a bidirectional command channel, and a wrapper package is optional, not the underlying API transport, so it is not a direct solution to any of the assigned workstreams.
D:The API validates the provided credential before accepting a request; this implements the different outcome to avoid unauthenticated model requests from a backend worker rather than the required tasks to keep integration behavior aligned with a supported request contract and to prevent a background processor from overwhelming the upstream API during bursts and to deliver tokens to a browser without maintaining a bidirectional command channel, and embedding a secret in a user prompt does not authenticate an HTTP call, so it is not a direct solution to any of the assigned workstreams.
Question 560
Two features of an inference routing system are under review. One feature must spend high-capability tokens only when validation indicates complexity; the other must stop a single customer from consuming the entire API allowance during a runaway workflow. Which plan matches the respective needs?
- First component: Measure cache read tokens. Second component: Set budget alerts and tenant caps.
- First component: Use batch pricing where deadline permits. Second component: Measure cache read tokens.
- First component: Use model routing for simple versus hard cases. Second component: Use batch pricing where deadline permits.
- First component: Use model routing for simple versus hard cases. Second component: Set budget alerts and tenant caps.
Explanation
Correct Answer
D:The first proposal fits its assigned role because conditional routing improves blended cost without discarding an escalation path, while the second proposal fits its assigned role because accounting plus enforced limits bounds exposure to unexpected traffic and agent loops; their respective acceptance criteria are to spend high-capability tokens only when validation indicates complexity and to stop a single customer from consuming the entire API allowance during a runaway workflow.
Incorrect Answers
A:The first proposal serves the different purpose to verify that an optimization actually reuses an earlier prompt prefix instead of the assigned first role because usage fields show how much eligible cached input was read rather than recomputed, while the second proposal fits its assigned role because accounting plus enforced limits bounds exposure to unexpected traffic and agent loops; their respective acceptance criteria are to spend high-capability tokens only when validation indicates complexity and to stop a single customer from consuming the entire API allowance during a runaway workflow.
B:The first proposal serves the different purpose to lower spend for large scheduled classification jobs that do not need immediate responses instead of the assigned first role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal serves the different purpose to verify that an optimization actually reuses an earlier prompt prefix instead of the assigned second role because usage fields show how much eligible cached input was read rather than recomputed; their respective acceptance criteria are to spend high-capability tokens only when validation indicates complexity and to stop a single customer from consuming the entire API allowance during a runaway workflow.
C:The first proposal fits its assigned role because conditional routing improves blended cost without discarding an escalation path, while the second proposal serves the different purpose to lower spend for large scheduled classification jobs that do not need immediate responses instead of the assigned second role because asynchronous batch processing can offer a cost-effective throughput path under supported terms; their respective acceptance criteria are to spend high-capability tokens only when validation indicates complexity and to stop a single customer from consuming the entire API allowance during a runaway workflow.