Question 270
A release plan for a retrieval pipeline platform has two acceptance checks: component one must prevent a parser crash when the model returns no ordinary text; component two must preserve auditability when an extractor reformats a date or currency. Which proposal passes both?
- First component: Escape generated content in the UI. Second component: Keep raw and normalized values distinct.
- First component: Validate semantic business invariants. Second component: Escape generated content in the UI.
- First component: Handle refusal and empty content explicitly. Second component: Validate semantic business invariants.
- First component: Handle refusal and empty content explicitly. Second component: Keep raw and normalized values distinct.
Explanation
Correct Answer
D:The first proposal fits its assigned role because response handling must branch on stop reason and content block types before decoding data, while the second proposal fits its assigned role because storing the original evidence and validated normalized value supports later reconciliation; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to preserve auditability when an extractor reformats a date or currency.
Incorrect Answers
A:The first proposal serves the different purpose to show model-produced HTML snippets without allowing browser script injection instead of the assigned first role because output encoding or sanitization protects display contexts from untrusted markup, while the second proposal fits its assigned role because storing the original evidence and validated normalized value supports later reconciliation; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to preserve auditability when an extractor reformats a date or currency.
B:The first proposal serves the different purpose to prevent a negative invoice total from reaching a payment ledger instead of the assigned first role because domain rules check value ranges and cross-field relationships beyond syntactic shape, while the second proposal serves the different purpose to show model-produced HTML snippets without allowing browser script injection instead of the assigned second role because output encoding or sanitization protects display contexts from untrusted markup; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to preserve auditability when an extractor reformats a date or currency.
C:The first proposal fits its assigned role because response handling must branch on stop reason and content block types before decoding data, while the second proposal serves the different purpose to prevent a negative invoice total from reaching a payment ledger instead of the assigned second role because domain rules check value ranges and cross-field relationships beyond syntactic shape; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to preserve auditability when an extractor reformats a date or currency.
Question 271
The acceptance criteria for a tool integration change state that it must let Claude distinguish a read-only invoice lookup from an invoice update. Which implementation aligns with that criterion?
- Use idempotency for retried mutations
- Return structured tool errors
- Write task-specific tool descriptions
- Restrict tool network credentials
Explanation
Correct Answer
C:Clear capabilities and side effects guide tool selection without granting new authority; this behavior directly supports the need to let Claude distinguish a read-only invoice lookup from an invoice update. Vague overlapping descriptions increase erroneous calls.
Incorrect Answers
A:When an application needs to avoid creating duplicate tickets after a tool call times out, stable operation identifiers let downstream systems detect repeated submissions; the current capability must instead let Claude distinguish a read-only invoice lookup from an invoice update, while a transport timeout does not mean no write occurred.
B:Machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up; the supported outcome is to let an assistant recover from a missing order without inventing its details, whereas this scenario requires the ability to let Claude distinguish a read-only invoice lookup from an invoice update; pretending failure is an empty successful record hides operational meaning.
D:Minimal capabilities reduce risk when generated arguments or retrieved text are hostile; despite being useful when a service must stop a directory lookup function from also gaining unrestricted database write access, it is not a solution to let Claude distinguish a read-only invoice lookup from an invoice update; better prompt wording does not remove excess infrastructure permissions.
Question 272
During a conversation design rollout, two different failure paths need remediation. The first component must prevent a parser crash when the model returns no ordinary text; separately, the second must prevent the frontend from parsing an incomplete JSON chunk as a complete response. Which changes should be adopted?
- First component: Keep raw and normalized values distinct. Second component: Parse JSON with a real parser.
- First component: Handle refusal and empty content explicitly. Second component: Keep raw and normalized values distinct.
- First component: Handle refusal and empty content explicitly. Second component: Separate a partial streaming fragment from a finished object.
- First component: Parse JSON with a real parser. Second component: Separate a partial streaming fragment from a finished object.
Explanation
Correct Answer
C:The first proposal fits its assigned role because response handling must branch on stop reason and content block types before decoding data, while the second proposal fits its assigned role because stream consumers must buffer and recognize completion before strict object validation; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
Incorrect Answers
A:The first proposal serves the different purpose to preserve auditability when an extractor reformats a date or currency instead of the assigned first role because storing the original evidence and validated normalized value supports later reconciliation, while the second proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned second role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
B:The first proposal fits its assigned role because response handling must branch on stop reason and content block types before decoding data, while the second proposal serves the different purpose to preserve auditability when an extractor reformats a date or currency instead of the assigned second role because storing the original evidence and validated normalized value supports later reconciliation; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
D:The first proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned first role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds, while the second proposal fits its assigned role because stream consumers must buffer and recognize completion before strict object validation; their respective acceptance criteria are to prevent a parser crash when the model returns no ordinary text and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
Question 273
A developer is reviewing alternatives for a customer platform feature that must deliver model-generated records to a strict financial reporting API. Which option is a defensible fit?
- Set an explicit data residency constraint
- Document functional acceptance criteria
- Define failure and recovery objectives
- Agree on output contracts with downstream systems
Explanation
Correct Answer
D:Typed fields and required identifiers enable validators and consumers to reject malformed results; this behavior directly supports the need to deliver model-generated records to a strict financial reporting API. A free-form explanatory paragraph may be legible but not machine-consumable.
Incorrect Answers
A:When an application needs to ensure protected records are processed only in approved jurisdictions, documented residency requirements inform cloud placement, logging, storage, and vendor selection; the current capability must instead deliver model-generated records to a strict financial reporting API, while a statement about answer quality does not control geographic data handling.
B:Acceptance criteria specify inputs, outputs, and successful behavior that can be tested before release; the supported outcome is to turn a vague request for an AI claims assistant into observable user actions and outputs, whereas this scenario requires the ability to deliver model-generated records to a strict financial reporting API; choosing a model first does not define what the application must accomplish.
C:This approach serves the separate need to keep a regulated triage service usable during an upstream API outage because availability, recovery time, and fallback behavior must be specified as measurable operational needs; it does not establish the outcome to deliver model-generated records to a strict financial reporting API, and a happy-path prototype misses behavior under dependency failures.
Question 274
A Claude application team owns two independent components. The first must catch schema and policy failures after a model or tool update; the second must identify rising error rates and latency after launch. Which paired plan fulfills both?
- First component: Perform a threat review before go-live. Second component: Assign an owner to every integration.
- First component: Assign an owner to every integration. Second component: Instrument production observability.
- First component: Implement automated regression tests. Second component: Perform a threat review before go-live.
- First component: Use a proof of concept before production commitment. Second component: Perform a threat review before go-live.
- First component: Implement automated regression tests. Second component: Instrument production observability.
Explanation
Correct Answer
E:The first proposal fits its assigned role because repeatable cases compare changes against documented acceptance criteria, while the second proposal fits its assigned role because logs, metrics, traces, and alert thresholds reveal operational failures at the right layer; their respective acceptance criteria are to catch schema and policy failures after a model or tool update and to identify rising error rates and latency after launch.
Incorrect Answers
A:The first proposal serves the different purpose to uncover prompt-injection paths through retrieved webpages and connected tools instead of the assigned first role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss, while the second proposal serves the different purpose to prevent abandoned connectors from retaining access after an application is transferred instead of the assigned second role because ownership enables rotation, monitoring, change approval, and retirement decisions; their respective acceptance criteria are to catch schema and policy failures after a model or tool update and to identify rising error rates and latency after launch.
B:The first proposal serves the different purpose to prevent abandoned connectors from retaining access after an application is transferred instead of the assigned first role because ownership enables rotation, monitoring, change approval, and retirement decisions, while the second proposal fits its assigned role because logs, metrics, traces, and alert thresholds reveal operational failures at the right layer; their respective acceptance criteria are to catch schema and policy failures after a model or tool update and to identify rising error rates and latency after launch.
C:The first proposal fits its assigned role because repeatable cases compare changes against documented acceptance criteria, while the second proposal serves the different purpose to uncover prompt-injection paths through retrieved webpages and connected tools instead of the assigned second role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss; their respective acceptance criteria are to catch schema and policy failures after a model or tool update and to identify rising error rates and latency after launch.
D:The first proposal serves the different purpose to test whether document classification quality is viable on representative files instead of the assigned first role because a small pilot reduces feasibility risk before funding a complete integration, while the second proposal serves the different purpose to uncover prompt-injection paths through retrieved webpages and connected tools instead of the assigned second role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss; their respective acceptance criteria are to catch schema and policy failures after a model or tool update and to identify rising error rates and latency after launch.
Question 275
An architecture review of a Claude application product lists two distinct outcomes: the first subsystem must explain service limits or tool outages without leaking stack traces or secrets, and a second subsystem must prevent a malicious help article from ordering the model to reveal secrets. Which pair delivers these outcomes?
- First component: Keep user tasks in the user message. Second component: Treat retrieval results as untrusted data.
- First component: Return user-friendly error states. Second component: Treat retrieval results as untrusted data.
- First component: Return user-friendly error states. Second component: Create one session per user conversation.
- First component: Create one session per user conversation. Second component: Keep user tasks in the user message.
Explanation
Correct Answer
B:The first proposal fits its assigned role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs, while the second proposal fits its assigned role because retrieved content should be framed as evidence, never upgraded to new tool or system authority; their respective acceptance criteria are to explain service limits or tool outages without leaking stack traces or secrets and to prevent a malicious help article from ordering the model to reveal secrets.
Incorrect Answers
A:The first proposal serves the different purpose to separate an end user's request from the developer's stable operating instructions instead of the assigned first role because explicit message roles distinguish requested work from higher-priority operational framing, while the second proposal fits its assigned role because retrieved content should be framed as evidence, never upgraded to new tool or system authority; their respective acceptance criteria are to explain service limits or tool outages without leaking stack traces or secrets and to prevent a malicious help article from ordering the model to reveal secrets.
C:The first proposal fits its assigned role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs, while the second proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned second role because session scoping ensures history and tool results belong to the correct principal; their respective acceptance criteria are to explain service limits or tool outages without leaking stack traces or secrets and to prevent a malicious help article from ordering the model to reveal secrets.
D:The first proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned first role because session scoping ensures history and tool results belong to the correct principal, while the second proposal serves the different purpose to separate an end user's request from the developer's stable operating instructions instead of the assigned second role because explicit message roles distinguish requested work from higher-priority operational framing; their respective acceptance criteria are to explain service limits or tool outages without leaking stack traces or secrets and to prevent a malicious help article from ordering the model to reveal secrets.
Question 276
A model platform application is approaching release, but the team still needs to reduce repeated processing of identical tool definitions and system instructions. What is the most appropriate implementation?
- Use model routing for simple versus hard cases
- Keep volatile fields after reusable context
- Set maximum step counts for agents
- Cache a stable shared prefix
Explanation
Correct Answer
D:Prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match; this behavior directly supports the need to reduce repeated processing of identical tool definitions and system instructions. Caching does not turn every changed prompt into an automatic hit.
Incorrect Answers
A:When an application needs to spend high-capability tokens only when validation indicates complexity, conditional routing improves blended cost without discarding an escalation path; the current capability must instead reduce repeated processing of identical tool definitions and system instructions, while blindly downgrading every call can increase retries and review expenses.
B:Stable instruction and reference sections should precede changing per-request details for effective prefix reuse; the supported outcome is to prevent request timestamps from invalidating a costly static prefix, whereas this scenario requires the ability to reduce repeated processing of identical tool definitions and system instructions; placing a changing value before the cache boundary undermines matching.
C:This approach serves the separate need to contain cumulative token and tool cost across a recursive research session because a bound on iterations prevents repeated generation and calls from growing without limit; it does not establish the outcome to reduce repeated processing of identical tool definitions and system instructions, and a per-message output cap alone does not control total multi-step spend.
Question 277
During acceptance testing for a customer platform service, one requirement is to detect unsafe permissions and schema changes before merging an agent tool. What should the developer implement?
- Validate JSON before deserialization
- Refactor duplicated request orchestration
- Use asynchronous I/O for concurrent requests
- Use pull requests and focused code review
- Version APIs and response schemas
Explanation
Correct Answer
D:Peer review creates an explicit checkpoint for correctness, security, and maintainability; this behavior directly supports the need to detect unsafe permissions and schema changes before merging an agent tool. Running a linter alone cannot assess authorization intent.
Incorrect Answers
A:A parser and schema validator catch missing types and invalid syntax before side effects; the supported outcome is to reject a malformed tool argument payload before calling a payroll service, whereas this scenario requires the ability to detect unsafe permissions and schema changes before merging an agent tool; model-generated text is not trustworthy merely because it looks structured.
B:This approach serves the separate need to maintain multiple Claude entry points without drifting retry and logging behavior because a shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes; it does not establish the outcome to detect unsafe permissions and schema changes before merging an agent tool, and copying the same networking code into every route magnifies defects.
C:Async execution overlaps I/O-bound tasks while maintaining control over concurrency; despite being useful when a service must serve independent API calls without blocking a worker thread for each network wait, it is not a solution to detect unsafe permissions and schema changes before merging an agent tool; it does not by itself make CPU-bound model processing faster.
E:Compatibility-aware contracts and versioned behavior protect consumers from surprise breaking changes; this applies to the different goal to allow older application clients to keep working while a new extraction field is introduced, not the requirement to detect unsafe permissions and schema changes before merging an agent tool; silently removing required fields can fail deployments that were not upgraded.
Question 278
In a Claude application project, acceptance test A checks whether a component can avoid assuming a Claude Code repository setting automatically affects a direct Messages API call. Acceptance test B checks whether a different component can compute discounts through verified business code rather than generated arithmetic alone. Which plan satisfies both tests?
- First component: Test interface-specific instruction behavior. Second component: Separate model reasoning from authoritative calculations.
- First component: Place durable behavior instructions in the system parameter. Second component: Handle empty and partial model responses.
- First component: Handle empty and partial model responses. Second component: Separate model reasoning from authoritative calculations.
- First component: Test interface-specific instruction behavior. Second component: Place durable behavior instructions in the system parameter.
Explanation
Correct Answer
A:The first proposal fits its assigned role because different Claude surfaces have different configuration and context mechanisms; an integration must supply its own instructions, while the second proposal fits its assigned role because deterministic services can enforce exact formulas and rounding before the model explains the result; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to compute discounts through verified business code rather than generated arithmetic alone.
Incorrect Answers
B:The first proposal serves the different purpose to ensure an API assistant consistently uses a defined support role across requests instead of the assigned first role because system-level guidance supplies application-wide instruction context, separate from each user's task content, while the second proposal serves the different purpose to keep a downstream parser from crashing when a request returns no usable text block instead of the assigned second role because content-aware response handling checks block types, stop reasons, and required values before proceeding; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to compute discounts through verified business code rather than generated arithmetic alone.
C:The first proposal serves the different purpose to keep a downstream parser from crashing when a request returns no usable text block instead of the assigned first role because content-aware response handling checks block types, stop reasons, and required values before proceeding, while the second proposal fits its assigned role because deterministic services can enforce exact formulas and rounding before the model explains the result; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to compute discounts through verified business code rather than generated arithmetic alone.
D:The first proposal fits its assigned role because different Claude surfaces have different configuration and context mechanisms; an integration must supply its own instructions, while the second proposal serves the different purpose to ensure an API assistant consistently uses a defined support role across requests instead of the assigned second role because system-level guidance supplies application-wide instruction context, separate from each user's task content; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to compute discounts through verified business code rather than generated arithmetic alone.
Question 279
A document processing team owns two independent components. The first must display a long report as it is generated rather than waiting for the full completion; the second must continue the agent loop when Claude is waiting for external observations. Which paired plan fulfills both?
- First component: Use SSE streaming for partial response delivery. Second component: Handle the tool_use stop_reason.
- First component: Handle a refusal stop_reason safely. Second component: Handle message_stop and final usage events.
- First component: Handle message_stop and final usage events. Second component: Reconcile batch responses by custom_id.
- First component: Reconcile batch responses by custom_id. Second component: Handle the tool_use stop_reason.
- First component: Use SSE streaming for partial response delivery. Second component: Handle message_stop and final usage events.
Explanation
Correct Answer
A:The first proposal fits its assigned role because streaming yields ordered events and content deltas that the client assembles into the final response, while the second proposal fits its assigned role because this stop reason means tool calls need to be executed and their results returned before synthesis; their respective acceptance criteria are to display a long report as it is generated rather than waiting for the full completion and to continue the agent loop when Claude is waiting for external observations.
Incorrect Answers
B:The first proposal serves the different purpose to avoid parsing safety refusals as valid JSON business records instead of the assigned first role because a refusal is a deliberate non-completion path that requires a defined application response, while the second proposal serves the different purpose to record complete streamed output and token usage accurately instead of the assigned second role because the final stream events signal completion and deliver accumulated metadata beyond individual text fragments; their respective acceptance criteria are to display a long report as it is generated rather than waiting for the full completion and to continue the agent loop when Claude is waiting for external observations.
C:The first proposal serves the different purpose to record complete streamed output and token usage accurately instead of the assigned first role because the final stream events signal completion and deliver accumulated metadata beyond individual text fragments, while the second proposal serves the different purpose to match returned batch results to the right source documents despite varying completion order instead of the assigned second role because a caller-assigned identifier links each result to the original request independently of result ordering; their respective acceptance criteria are to display a long report as it is generated rather than waiting for the full completion and to continue the agent loop when Claude is waiting for external observations.
D:The first proposal serves the different purpose to match returned batch results to the right source documents despite varying completion order instead of the assigned first role because a caller-assigned identifier links each result to the original request independently of result ordering, while the second proposal fits its assigned role because this stop reason means tool calls need to be executed and their results returned before synthesis; their respective acceptance criteria are to display a long report as it is generated rather than waiting for the full completion and to continue the agent loop when Claude is waiting for external observations.
E:The first proposal fits its assigned role because streaming yields ordered events and content deltas that the client assembles into the final response, while the second proposal serves the different purpose to record complete streamed output and token usage accurately instead of the assigned second role because the final stream events signal completion and deliver accumulated metadata beyond individual text fragments; their respective acceptance criteria are to display a long report as it is generated rather than waiting for the full completion and to continue the agent loop when Claude is waiting for external observations.
Question 280
Two separate tickets in a retrieval pipeline backlog require different controls. One needs to reject a response that omits a mandated account identifier; the other needs to detect plausible dates or amounts that are absent from the provided document. Which implementation pair is correct?
- First component: Handle refusal and empty content explicitly. Second component: Parse JSON with a real parser.
- First component: Validate required schema fields. Second component: Handle refusal and empty content explicitly.
- First component: Validate required schema fields. Second component: Check evidence alignment after extraction.
- First component: Parse JSON with a real parser. Second component: Check evidence alignment after extraction.
Explanation
Correct Answer
C:The first proposal fits its assigned role because schema checks enforce field presence, types, and enumerations before the result enters a database, while the second proposal fits its assigned role because semantic verification compares fields to authoritative source spans; their respective acceptance criteria are to reject a response that omits a mandated account identifier and to detect plausible dates or amounts that are absent from the provided document.
Incorrect Answers
A:The first proposal serves the different purpose to prevent a parser crash when the model returns no ordinary text instead of the assigned first role because response handling must branch on stop reason and content block types before decoding data, while the second proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned second role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds; their respective acceptance criteria are to reject a response that omits a mandated account identifier and to detect plausible dates or amounts that are absent from the provided document.
B:The first proposal fits its assigned role because schema checks enforce field presence, types, and enumerations before the result enters a database, while the second proposal serves the different purpose to prevent a parser crash when the model returns no ordinary text instead of the assigned second role because response handling must branch on stop reason and content block types before decoding data; their respective acceptance criteria are to reject a response that omits a mandated account identifier and to detect plausible dates or amounts that are absent from the provided document.
D:The first proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned first role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds, while the second proposal fits its assigned role because semantic verification compares fields to authoritative source spans; their respective acceptance criteria are to reject a response that omits a mandated account identifier and to detect plausible dates or amounts that are absent from the provided document.