Question 460
A technical specification for a Claude application application assigns two jobs to separate modules: module A must detect unsafe permissions and schema changes before merging an agent tool, and module B must reject a malformed tool argument payload before calling a payroll service. Which two-part solution is appropriate?
- First component: Separate integration tests from unit tests. Second component: Validate JSON before deserialization.
- First component: Use pull requests and focused code review. Second component: Use feature flags for risky behavior changes.
- First component: Use feature flags for risky behavior changes. Second component: Separate integration tests from unit tests.
- First component: Use pull requests and focused code review. Second component: Validate JSON before deserialization.
Explanation
Correct Answer
D:The first proposal fits its assigned role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reject a malformed tool argument payload before calling a payroll service.
Incorrect Answers
A: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 fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reject a malformed tool argument payload before calling a payroll service.
B:The first proposal fits its assigned role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal serves the different purpose to activate a new tool execution path for only internal testers instead of the assigned second role because runtime controls can segment rollout and permit quick disabling without a code rebuild; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reject a malformed tool argument payload before calling a payroll service.
C:The first proposal serves the different purpose to activate a new tool execution path for only internal testers instead of the assigned first role because runtime controls can segment rollout and permit quick disabling without a code rebuild, 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 detect unsafe permissions and schema changes before merging an agent tool and to reject a malformed tool argument payload before calling a payroll service.
Question 461
A team maintaining an agent extensibility needs to support multiple simultaneous lookups without mixing their responses. Which implementation most directly satisfies the requirement?
- Write task-specific tool descriptions
- Map tool_use IDs to results
- Handle parallel tool requests carefully
- Separate read tools from write tools
- Add an approval boundary before sensitive writes
Explanation
Correct Answer
B:Correlation IDs connect each observation to the exact invocation that requested it; this behavior directly supports the need to support multiple simultaneous lookups without mixing their responses. Pairing results by arrival order is unsafe under concurrency.
Incorrect Answers
A:Clear capabilities and side effects guide tool selection without granting new authority; despite being useful when a service must let Claude distinguish a read-only invoice lookup from an invoice update, it is not a solution to support multiple simultaneous lookups without mixing their responses; vague overlapping descriptions increase erroneous calls.
C:Independent reads can run concurrently but dependent mutations need ordering or transactions; this applies to the different goal to speed up independent product lookups without racing dependent account updates, not the requirement to support multiple simultaneous lookups without mixing their responses; unconditional parallel dispatch can violate business invariants.
D:When an application needs to require stricter approval for actions that change customer data, distinct interfaces simplify least-privilege grants and side-effect controls; the current capability must instead support multiple simultaneous lookups without mixing their responses, while a generic execute-anything function makes authorization difficult to enforce.
E:Authorization by a user or operator can be enforced before the executor commits changes; the supported outcome is to prevent a helpful assistant from issuing refunds automatically, whereas this scenario requires the ability to support multiple simultaneous lookups without mixing their responses; a note in the model's prompt is not a transaction approval.
Question 462
During an operations orchestration rollout, two different failure paths need remediation. The first component must recover agent state when a container restarts during a lengthy customer case; separately, the second must let an agent run generated scripts without exposing production host files. Which changes should be adopted?
- First component: Use a durable session store. Second component: Choose isolated sandbox execution for untrusted code.
- First component: Return a structured tool error to the model. Second component: Choose isolated sandbox execution for untrusted code.
- First component: Use a durable session store. Second component: Set a tool execution timeout.
- First component: Set a tool execution timeout. Second component: Return a structured tool error to the model.
Explanation
Correct Answer
A:The first proposal fits its assigned role because external persistence holds the conversation and workflow metadata needed to resume safely, while the second proposal fits its assigned role because a restricted execution environment limits filesystem, network, and resource privileges; their respective acceptance criteria are to recover agent state when a container restarts during a lengthy customer case and to let an agent run generated scripts without exposing production host files.
Incorrect Answers
B:The first proposal serves the different purpose to recover from a failed search while preserving the agent's chance to choose another path instead of the assigned first role because tool-result errors surface the failure without impersonating a successful action, while the second proposal fits its assigned role because a restricted execution environment limits filesystem, network, and resource privileges; their respective acceptance criteria are to recover agent state when a container restarts during a lengthy customer case and to let an agent run generated scripts without exposing production host files.
C:The first proposal fits its assigned role because external persistence holds the conversation and workflow metadata needed to resume safely, while the second proposal serves the different purpose to prevent a slow external inventory service from blocking an agent indefinitely instead of the assigned second role because deadlines bound latency and convert stalled calls into explicit recoverable failures; their respective acceptance criteria are to recover agent state when a container restarts during a lengthy customer case and to let an agent run generated scripts without exposing production host files.
D:The first proposal serves the different purpose to prevent a slow external inventory service from blocking an agent indefinitely instead of the assigned first role because deadlines bound latency and convert stalled calls into explicit recoverable failures, while the second proposal serves the different purpose to recover from a failed search while preserving the agent's chance to choose another path instead of the assigned second role because tool-result errors surface the failure without impersonating a successful action; their respective acceptance criteria are to recover agent state when a container restarts during a lengthy customer case and to let an agent run generated scripts without exposing production host files.
Question 463
Engineers are splitting an engineering workstation service into two independently tested functions. Function A must deny destructive commands regardless of what a generated plan proposes, while function B must block edits to a protected deployment file before a tool writes them. Which plan is sound?
- First component: Connect an MCP server to Claude Code. Second component: Use a pre-execution hook for deterministic checks.
- First component: Configure permissions in Claude Code settings. Second component: Use a pre-execution hook for deterministic checks.
- First component: Configure permissions in Claude Code settings. Second component: Run repository initialization to create project guidance.
- First component: Run repository initialization to create project guidance. Second component: Connect an MCP server to Claude Code.
Explanation
Correct Answer
B:The first proposal fits its assigned role because explicit allow and deny rules establish executable tool policy rather than advisory prose, while the second proposal fits its assigned role because tool lifecycle hooks enforce programmable validation at defined execution points; their respective acceptance criteria are to deny destructive commands regardless of what a generated plan proposes and to block edits to a protected deployment file before a tool writes them.
Incorrect Answers
A:The first proposal serves the different purpose to expose approved project-specific actions without copying credentials into prompts instead of the assigned first role because an MCP integration declares external capabilities and their transport while access remains controlled by the server, while the second proposal fits its assigned role because tool lifecycle hooks enforce programmable validation at defined execution points; their respective acceptance criteria are to deny destructive commands regardless of what a generated plan proposes and to block edits to a protected deployment file before a tool writes them.
C:The first proposal fits its assigned role because explicit allow and deny rules establish executable tool policy rather than advisory prose, while the second proposal serves the different purpose to establish a discoverable set of build and test conventions for a new Claude Code workspace instead of the assigned second role because repository initialization can generate or prepare project instruction material that the team subsequently reviews; their respective acceptance criteria are to deny destructive commands regardless of what a generated plan proposes and to block edits to a protected deployment file before a tool writes them.
D:The first proposal serves the different purpose to establish a discoverable set of build and test conventions for a new Claude Code workspace instead of the assigned first role because repository initialization can generate or prepare project instruction material that the team subsequently reviews, while the second proposal serves the different purpose to expose approved project-specific actions without copying credentials into prompts instead of the assigned second role because an MCP integration declares external capabilities and their transport while access remains controlled by the server; their respective acceptance criteria are to deny destructive commands regardless of what a generated plan proposes and to block edits to a protected deployment file before a tool writes them.
Question 464
The acceptance criteria for a prompt engineering change state that it must save tokens when several retrieval chunks contain the same repeated policy section. Which implementation aligns with that criterion?
- Deduplicate overlapping passages
- Separate long-term memory from active scratchpad
- Prioritize high-signal retrieved passages
- Reserve space for the model's output
Explanation
Correct Answer
A:Overlap detection reduces redundant context without throwing away unique clauses; this behavior directly supports the need to save tokens when several retrieval chunks contain the same repeated policy section. Simply increasing retrieval count may provide many copies of the same material.
Incorrect Answers
B:Explicit storage and freshness rules govern what is retained and when it is reintroduced; the supported outcome is to prevent outdated user preferences from being treated as current task instructions, whereas this scenario requires the ability to save tokens when several retrieval chunks contain the same repeated policy section; an unbounded persistent transcript can accumulate contradictory assumptions.
C:This approach serves the separate need to fit a large knowledge base into the context of a customer answer because ranking by relevance and authority places the most useful evidence ahead of incidental matches; it does not establish the outcome to save tokens when several retrieval chunks contain the same repeated policy section, and dumping every document into the prompt can obscure the actual answer.
D:Input assembly must leave room for the requested completion and any needed reasoning; despite being useful when a service must avoid using the entire context budget on retrieved input before generating a response, it is not a solution to save tokens when several retrieval chunks contain the same repeated policy section; a technically accepted long prompt can still prevent a useful-length answer.
Question 465
A release plan for a document processing platform has two acceptance checks: component one must avoid starting two extraction jobs for the same uploaded document after repeated browser submissions; component two must avoid burying the relevant contract clause beneath hundreds of low-value passages. Which proposal passes both?
- First component: Deduplicate application events. Second component: Place durable behavior instructions in the system parameter.
- First component: Place durable behavior instructions in the system parameter. Second component: Treat retrieval results as untrusted data.
- First component: Deduplicate application events. Second component: Use bounded retrieval results.
- First component: Treat retrieval results as untrusted data. Second component: Use bounded retrieval results.
Explanation
Correct Answer
C:The first proposal fits its assigned role because an idempotent job key lets the server recognize duplicates at its request boundary, while the second proposal fits its assigned role because ranking and a context budget prioritize high-quality evidence while controlling input tokens; their respective acceptance criteria are to avoid starting two extraction jobs for the same uploaded document after repeated browser submissions and to avoid burying the relevant contract clause beneath hundreds of low-value passages.
Incorrect Answers
A:The first proposal fits its assigned role because an idempotent job key lets the server recognize duplicates at its request boundary, 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 starting two extraction jobs for the same uploaded document after repeated browser submissions and to avoid burying the relevant contract clause beneath hundreds of low-value passages.
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 prevent a malicious help article from ordering the model to reveal secrets instead of the assigned second role because retrieved content should be framed as evidence, never upgraded to new tool or system authority; their respective acceptance criteria are to avoid starting two extraction jobs for the same uploaded document after repeated browser submissions and to avoid burying the relevant contract clause beneath hundreds of low-value passages.
D:The first proposal serves the different purpose to prevent a malicious help article from ordering the model to reveal secrets instead of the assigned first role because retrieved content should be framed as evidence, never upgraded to new tool or system authority, while the second proposal fits its assigned role because ranking and a context budget prioritize high-quality evidence while controlling input tokens; their respective acceptance criteria are to avoid starting two extraction jobs for the same uploaded document after repeated browser submissions and to avoid burying the relevant contract clause beneath hundreds of low-value passages.
Question 466
Two separate tickets in an agent platform backlog require different controls. One needs to answer questions from changing internal documentation with traceable source excerpts; the other needs to protect a coordinator's window from huge specialist tool outputs. Which implementation pair is correct?
- First component: Use a plan-execute-review loop. Second component: Use an independent verifier step.
- First component: Use retrieval before generation. Second component: Delegate narrow subtasks with a separate context.
- First component: Use retrieval before generation. Second component: Use a plan-execute-review loop.
- First component: Use an independent verifier step. Second component: Delegate narrow subtasks with a separate context.
Explanation
Correct Answer
B:The first proposal fits its assigned role because retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current, while the second proposal fits its assigned role because each subagent can work in a bounded context and return a concise, verified artifact; their respective acceptance criteria are to answer questions from changing internal documentation with traceable source excerpts and to protect a coordinator's window from huge specialist tool outputs.
Incorrect Answers
A:The first proposal serves the different purpose to manage a complex migration that requires checkpoints after several tool actions instead of the assigned first role because separating plan, execution, and review makes deviations visible before a final outcome is accepted, while the second proposal serves the different purpose to detect mistakes in an agent-generated SQL migration before running it instead of the assigned second role because a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors; their respective acceptance criteria are to answer questions from changing internal documentation with traceable source excerpts and to protect a coordinator's window from huge specialist tool outputs.
C:The first proposal fits its assigned role because retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current, while the second proposal serves the different purpose to manage a complex migration that requires checkpoints after several tool actions instead of the assigned second role because separating plan, execution, and review makes deviations visible before a final outcome is accepted; their respective acceptance criteria are to answer questions from changing internal documentation with traceable source excerpts and to protect a coordinator's window from huge specialist tool outputs.
D:The first proposal serves the different purpose to detect mistakes in an agent-generated SQL migration before running it instead of the assigned first role because a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors, while the second proposal fits its assigned role because each subagent can work in a bounded context and return a concise, verified artifact; their respective acceptance criteria are to answer questions from changing internal documentation with traceable source excerpts and to protect a coordinator's window from huge specialist tool outputs.
Question 467
In an inference routing project, acceptance test A checks whether a component can keep a web request from hanging indefinitely if a network path stalls. Acceptance test B checks whether a different component can avoid unauthenticated model requests from a backend worker. Which plan satisfies both tests?
- First component: Specify request deadlines in the caller. Second component: Use the official SDK for standard requests.
- First component: Specify request deadlines in the caller. Second component: Send the correct API authentication header.
- First component: Use the official SDK for standard requests. Second component: Honor server rate-limit signals.
- First component: Honor server rate-limit signals. Second component: Send the correct API authentication header.
Explanation
Correct Answer
B:The first proposal fits its assigned role because a client timeout bounds waiting for transport and response completion, while the second proposal fits its assigned role because the API validates the provided credential before accepting a request; their respective acceptance criteria are to keep a web request from hanging indefinitely if a network path stalls and to avoid unauthenticated model requests from a backend worker.
Incorrect Answers
A:The first proposal fits its assigned role because a client timeout bounds waiting for transport and response completion, while the second proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned second role because maintained client libraries wrap the HTTP API and expose structured response objects; their respective acceptance criteria are to keep a web request from hanging indefinitely if a network path stalls and to avoid unauthenticated model requests from a backend worker.
C:The first proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned first role because maintained client libraries wrap the HTTP API and expose structured response objects, while the second proposal serves the different purpose to prevent a background processor from overwhelming the upstream API during bursts instead of the assigned second role because throttling and backoff work with provider limits rather than assuming infinite request capacity; their respective acceptance criteria are to keep a web request from hanging indefinitely if a network path stalls and to avoid unauthenticated model requests from a backend worker.
D:The first proposal serves the different purpose to prevent a background processor from overwhelming the upstream API during bursts instead of the assigned first role because throttling and backoff work with provider limits rather than assuming infinite request capacity, while the second proposal fits its assigned role because the API validates the provided credential before accepting a request; their respective acceptance criteria are to keep a web request from hanging indefinitely if a network path stalls and to avoid unauthenticated model requests from a backend worker.
Question 468
The owner of a document processing integration wants to ensure an API assistant consistently uses a defined support role across requests. Which proposal provides the required mechanism?
- Handle empty and partial model responses
- Build a typed output envelope
- Isolate tools behind a service layer
- Place durable behavior instructions in the system parameter
- Treat retrieval results as untrusted data
Explanation
Correct Answer
D:System-level guidance supplies application-wide instruction context, separate from each user's task content; this behavior directly supports the need to ensure an API assistant consistently uses a defined support role across requests. A string placed in retrieved documents has no authority to redefine the application policy.
Incorrect Answers
A:Content-aware response handling checks block types, stop reasons, and required values before proceeding; this applies to the different goal to keep a downstream parser from crashing when a request returns no usable text block, not the requirement to ensure an API assistant consistently uses a defined support role across requests; assuming every message contains a single complete text string is unsafe.
B:When an application needs to send extracted contract fields into a database that rejects unexpected shapes, an explicit schema with required fields, types, and allowed values makes integration errors detectable; the current capability must instead ensure an API assistant consistently uses a defined support role across requests, while free-form natural language is difficult to validate automatically.
C:A mediation service validates identity, arguments, authorization, and audit logs for each requested action; the supported outcome is to avoid exposing raw production database credentials directly to an agent, whereas this scenario requires the ability to ensure an API assistant consistently uses a defined support role across requests; a natural-language tool description is not an access-control boundary.
E:Retrieved content should be framed as evidence, never upgraded to new tool or system authority; despite being useful when a service must prevent a malicious help article from ordering the model to reveal secrets, it is not a solution to ensure an API assistant consistently uses a defined support role across requests; a trustworthy source URL does not make embedded commands authorized.
Question 469
A source-control workflow solution has parallel requirements with separate owners. Workstream one must provide a consistent shortcut for a common repository maintenance task; workstream two must make a specialised review procedure available as task-specific instructions and assets. Which combination meets both?
- First component: Define a custom slash command workflow. Second component: Create a reusable Skill.
- First component: Use directory-scoped instructions. Second component: Review and resume a saved session.
- First component: Define a custom slash command workflow. Second component: Use directory-scoped instructions.
- First component: Review and resume a saved session. Second component: Create a reusable Skill.
Explanation
Correct Answer
A:The first proposal fits its assigned role because command-based workflows supply repeatable user-invoked instructions and arguments, while the second proposal fits its assigned role because a Skill packages a repeatable capability that Claude can load when relevant to the work; their respective acceptance criteria are to provide a consistent shortcut for a common repository maintenance task and to make a specialised review procedure available as task-specific instructions and assets.
Incorrect Answers
B:The first proposal serves the different purpose to apply specialised rules only to a sensitive infrastructure folder instead of the assigned first role because more local instruction files help scope guidance to the appropriate subtree, while the second proposal serves the different purpose to continue an interrupted refactor while retaining relevant prior decisions instead of the assigned second role because session continuation can reestablish conversational state without restarting the task from scratch; their respective acceptance criteria are to provide a consistent shortcut for a common repository maintenance task and to make a specialised review procedure available as task-specific instructions and assets.
C:The first proposal fits its assigned role because command-based workflows supply repeatable user-invoked instructions and arguments, while the second proposal serves the different purpose to apply specialised rules only to a sensitive infrastructure folder instead of the assigned second role because more local instruction files help scope guidance to the appropriate subtree; their respective acceptance criteria are to provide a consistent shortcut for a common repository maintenance task and to make a specialised review procedure available as task-specific instructions and assets.
D:The first proposal serves the different purpose to continue an interrupted refactor while retaining relevant prior decisions instead of the assigned first role because session continuation can reestablish conversational state without restarting the task from scratch, while the second proposal fits its assigned role because a Skill packages a repeatable capability that Claude can load when relevant to the work; their respective acceptance criteria are to provide a consistent shortcut for a common repository maintenance task and to make a specialised review procedure available as task-specific instructions and assets.
Question 470
A backend integration build contains an upstream function and a separate downstream function. The upstream work must deploy the same application build to staging and production with distinct endpoints; the downstream work must prevent an untested tool-allowlist edit from reaching all developers immediately. Which configuration pair covers both?
- First component: Put repository guidance in CLAUDE.md. Second component: Roll out configuration through reviewed changes.
- First component: Keep environment-specific settings external. Second component: Roll out configuration through reviewed changes.
- First component: Track MCP server versions and contracts. Second component: Put repository guidance in CLAUDE.md.
- First component: Keep environment-specific settings external. Second component: Track MCP server versions and contracts.
- First component: Use separate permission profiles by environment. Second component: Track MCP server versions and contracts.
Explanation
Correct Answer
B:The first proposal fits its assigned role because configuration injection separates environment differences from immutable application artifacts, while the second proposal fits its assigned role because change review and versioning provide accountability and a tested rollback path; their respective acceptance criteria are to deploy the same application build to staging and production with distinct endpoints and to prevent an untested tool-allowlist edit from reaching all developers immediately.
Incorrect Answers
A:The first proposal serves the different purpose to give Claude Code the project's build, test, and architecture conventions instead of the assigned first role because repository memory files provide persistent instructional context to coding sessions, while the second proposal fits its assigned role because change review and versioning provide accountability and a tested rollback path; their respective acceptance criteria are to deploy the same application build to staging and production with distinct endpoints and to prevent an untested tool-allowlist edit from reaching all developers immediately.
C:The first proposal serves the different purpose to keep external tool connectors compatible after client upgrades instead of the assigned first role because declared versions and integration tests expose resource or schema changes before deployment, while the second proposal serves the different purpose to give Claude Code the project's build, test, and architecture conventions instead of the assigned second role because repository memory files provide persistent instructional context to coding sessions; their respective acceptance criteria are to deploy the same application build to staging and production with distinct endpoints and to prevent an untested tool-allowlist edit from reaching all developers immediately.
D:The first proposal fits its assigned role because configuration injection separates environment differences from immutable application artifacts, while the second proposal serves the different purpose to keep external tool connectors compatible after client upgrades instead of the assigned second role because declared versions and integration tests expose resource or schema changes before deployment; their respective acceptance criteria are to deploy the same application build to staging and production with distinct endpoints and to prevent an untested tool-allowlist edit from reaching all developers immediately.
E:The first proposal serves the different purpose to allow broad exploratory tools in a sandbox but only approved reads in production instead of the assigned first role because environment-scoped policy avoids inheriting development privileges in a live setting, while the second proposal serves the different purpose to keep external tool connectors compatible after client upgrades instead of the assigned second role because declared versions and integration tests expose resource or schema changes before deployment; their respective acceptance criteria are to deploy the same application build to staging and production with distinct endpoints and to prevent an untested tool-allowlist edit from reaching all developers immediately.