Question 60
An MCP interoperability solution has parallel requirements with separate owners. Workstream one must make one internal ticketing connector available to several agent clients; workstream two must give a coding agent a consistent review playbook and supporting assets. Which combination meets both?
- First component: Use hooks for enforceable safety checks. Second component: Package a Skill for reusable guidance.
- First component: Use a deterministic workflow for fixed stages. Second component: Use hooks for enforceable safety checks.
- First component: Publish an MCP server for reusable integrations. Second component: Use a deterministic workflow for fixed stages.
- First component: Publish an MCP server for reusable integrations. Second component: Package a Skill for reusable guidance.
Explanation
Correct Answer
D:The first proposal fits its assigned role because MCP standardizes tool and resource discovery across compatible applications, while the second proposal fits its assigned role because a Skill provides task procedures and resources that the agent can load when applicable; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to give a coding agent a consistent review playbook and supporting assets.
Incorrect Answers
A:The first proposal serves the different purpose to deny destructive filesystem operations before a coding agent executes them instead of the assigned first role because runtime interception can apply deterministic policies to proposed actions, while the second proposal fits its assigned role because a Skill provides task procedures and resources that the agent can load when applicable; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to give a coding agent a consistent review playbook and supporting assets.
B:The first proposal serves the different purpose to automate the same classify-review-export path across predictable submissions instead of the assigned first role because explicit application control makes each transition testable and easier to audit, while the second proposal serves the different purpose to deny destructive filesystem operations before a coding agent executes them instead of the assigned second role because runtime interception can apply deterministic policies to proposed actions; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to give a coding agent a consistent review playbook and supporting assets.
C:The first proposal fits its assigned role because MCP standardizes tool and resource discovery across compatible applications, while the second proposal serves the different purpose to automate the same classify-review-export path across predictable submissions instead of the assigned second role because explicit application control makes each transition testable and easier to audit; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to give a coding agent a consistent review playbook and supporting assets.
Question 61
A production-readiness check for a production API component requires the service to deploy the same application build to staging and production with distinct endpoints. Which approach passes this check?
- Keep environment-specific settings external
- Use separate permission profiles by environment
- Put repository guidance in CLAUDE.md
- Roll out configuration through reviewed changes
Explanation
Correct Answer
A:Configuration injection separates environment differences from immutable application artifacts; this behavior directly supports the need to deploy the same application build to staging and production with distinct endpoints. Hard-coded URLs require risky code changes for promotion.
Incorrect Answers
B:This approach serves the separate need to allow broad exploratory tools in a sandbox but only approved reads in production because environment-scoped policy avoids inheriting development privileges in a live setting; it does not establish the outcome to deploy the same application build to staging and production with distinct endpoints, and one permissive configuration applied everywhere erases the staging boundary.
C:Repository memory files provide persistent instructional context to coding sessions; despite being useful when a service must give Claude Code the project's build, test, and architecture conventions, it is not a solution to deploy the same application build to staging and production with distinct endpoints; they are not an application secrets manager or the API's global system prompt.
D:For the alternate objective to prevent an untested tool-allowlist edit from reaching all developers immediately, change review and versioning provide accountability and a tested rollback path; the feature here must deploy the same application build to staging and production with distinct endpoints, and undocumented local overrides create configuration drift.
Question 62
A design meeting for a workflow automation platform concludes that two isolated services require different behavior: one must execute an unchanged sequence of extraction, validation, and publishing steps, and another must preserve evidence and data lineage when one agent delegates a subtask to another. Which arrangement meets the specification?
- First component: Use parallel fan-out and a reconciliation step. Second component: Use an explicit completion condition and step budget.
- First component: Use a deterministic workflow. Second component: Pass structured handoff artifacts between workers.
- First component: Use a deterministic workflow. Second component: Use parallel fan-out and a reconciliation step.
- First component: Use an explicit completion condition and step budget. Second component: Pass structured handoff artifacts between workers.
Explanation
Correct Answer
B:The first proposal fits its assigned role because a fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit, while the second proposal fits its assigned role because defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff; their respective acceptance criteria are to execute an unchanged sequence of extraction, validation, and publishing steps and to preserve evidence and data lineage when one agent delegates a subtask to another.
Incorrect Answers
A:The first proposal serves the different purpose to analyze several independent document sections concurrently and combine the results instead of the assigned first role because parallel tasks reduce critical-path latency when they do not depend on one another; a join step resolves conflicting findings, while the second proposal serves the different purpose to bound the runtime of an agent that repeatedly searches without converging instead of the assigned second role because a maximum iteration or cost budget plus a clear success criterion stops runaway tool loops; their respective acceptance criteria are to execute an unchanged sequence of extraction, validation, and publishing steps and to preserve evidence and data lineage when one agent delegates a subtask to another.
C:The first proposal fits its assigned role because a fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit, while the second proposal serves the different purpose to analyze several independent document sections concurrently and combine the results instead of the assigned second role because parallel tasks reduce critical-path latency when they do not depend on one another; a join step resolves conflicting findings; their respective acceptance criteria are to execute an unchanged sequence of extraction, validation, and publishing steps and to preserve evidence and data lineage when one agent delegates a subtask to another.
D:The first proposal serves the different purpose to bound the runtime of an agent that repeatedly searches without converging instead of the assigned first role because a maximum iteration or cost budget plus a clear success criterion stops runaway tool loops, while the second proposal fits its assigned role because defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff; their respective acceptance criteria are to execute an unchanged sequence of extraction, validation, and publishing steps and to preserve evidence and data lineage when one agent delegates a subtask to another.
Question 63
Two features of a data pipeline system are under review. One feature must turn a vague request for an AI claims assistant into observable user actions and outputs; the other must prevent a Claude assistant from inventing account balances when it lacks current ledger data. Which plan matches the respective needs?
- First component: Record nonfunctional latency targets. Second component: Set an explicit data residency constraint.
- First component: Document functional acceptance criteria. Second component: Record nonfunctional latency targets.
- First component: Document functional acceptance criteria. Second component: Identify authoritative source systems.
- First component: Set an explicit data residency constraint. Second component: Identify authoritative source systems.
Explanation
Correct Answer
C:The first proposal fits its assigned 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 source-of-truth mapping identifies which verified systems must supply facts and what freshness guarantees apply; their respective acceptance criteria are to turn a vague request for an AI claims assistant into observable user actions and outputs and to prevent a Claude assistant from inventing account balances when it lacks current ledger data.
Incorrect Answers
A: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 ensure protected records are processed only in approved jurisdictions instead of the assigned second role because documented residency requirements inform cloud placement, logging, storage, and vendor selection; their respective acceptance criteria are to turn a vague request for an AI claims assistant into observable user actions and outputs and to prevent a Claude assistant from inventing account balances when it lacks current ledger data.
B:The first proposal fits its assigned role because acceptance criteria specify inputs, outputs, and successful behavior that can be tested before release, 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 turn a vague request for an AI claims assistant into observable user actions and outputs and to prevent a Claude assistant from inventing account balances when it lacks current ledger data.
D:The first proposal serves the different purpose to ensure protected records are processed only in approved jurisdictions instead of the assigned first role because documented residency requirements inform cloud placement, logging, storage, and vendor selection, while the second proposal fits its assigned role because source-of-truth mapping identifies which verified systems must supply facts and what freshness guarantees apply; their respective acceptance criteria are to turn a vague request for an AI claims assistant into observable user actions and outputs and to prevent a Claude assistant from inventing account balances when it lacks current ledger data.
Question 64
A tool integration solution has parallel requirements with separate owners. Workstream one must prevent a helpful assistant from issuing refunds automatically; workstream two must prevent malformed or unauthorized input from executing a customer data query. Which combination meets both?
- First component: Add an approval boundary before sensitive writes. Second component: Return structured tool errors.
- First component: Return structured tool errors. Second component: Separate read tools from write tools.
- First component: Separate read tools from write tools. Second component: Validate generated arguments in application code.
- First component: Add an approval boundary before sensitive writes. Second component: Validate generated arguments in application code.
Explanation
Correct Answer
D:The first proposal fits its assigned role because authorization by a user or operator can be enforced before the executor commits changes, while the second proposal fits its assigned role because the executor must check types, ranges, identity, and scope independently of the model; their respective acceptance criteria are to prevent a helpful assistant from issuing refunds automatically and to prevent malformed or unauthorized input from executing a customer data query.
Incorrect Answers
A:The first proposal fits its assigned role because authorization by a user or operator can be enforced before the executor commits changes, while the second proposal serves the different purpose to let an assistant recover from a missing order without inventing its details instead of the assigned second role because machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up; their respective acceptance criteria are to prevent a helpful assistant from issuing refunds automatically and to prevent malformed or unauthorized input from executing a customer data query.
B:The first proposal serves the different purpose to let an assistant recover from a missing order without inventing its details instead of the assigned first role because machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up, while the second proposal serves the different purpose to require stricter approval for actions that change customer data instead of the assigned second role because distinct interfaces simplify least-privilege grants and side-effect controls; their respective acceptance criteria are to prevent a helpful assistant from issuing refunds automatically and to prevent malformed or unauthorized input from executing a customer data query.
C:The first proposal serves the different purpose to require stricter approval for actions that change customer data instead of the assigned first role because distinct interfaces simplify least-privilege grants and side-effect controls, while the second proposal fits its assigned role because the executor must check types, ranges, identity, and scope independently of the model; their respective acceptance criteria are to prevent a helpful assistant from issuing refunds automatically and to prevent malformed or unauthorized input from executing a customer data query.
Question 65
During acceptance testing for a latency optimization service, one requirement is to avoid rejecting tool schemas because serialized values are invalid. What should the developer implement?
- Use the Messages count_tokens capability
- Use JSON-safe types in request bodies
- Send the correct API authentication header
- Use a queue for burst absorption
- Send an API version header where required
Explanation
Correct Answer
B:Structured request encoding enforces objects, arrays, strings, booleans, and numeric representations; this behavior directly supports the need to avoid rejecting tool schemas because serialized values are invalid. Python object repr strings are not valid JSON contracts.
Incorrect Answers
A:Token counting helps check input budgets before generation and cost planning; despite being useful when a service must estimate model-token input demand before launching a large processing job, it is not a solution to avoid rejecting tool schemas because serialized values are invalid; word or byte count is not a reliable substitute across diverse content.
C:The API validates the provided credential before accepting a request; this applies to the different goal to avoid unauthenticated model requests from a backend worker, not the requirement to avoid rejecting tool schemas because serialized values are invalid; embedding a secret in a user prompt does not authenticate an HTTP call.
D:When an application needs to smooth sudden ingestion spikes before workers call a capacity-limited model API, queueing decouples producers from consumer throughput and enables controlled retries; the current capability must instead avoid rejecting tool schemas because serialized values are invalid, while increasing frontend timeouts does not eliminate backend capacity limits.
E:Explicit protocol versioning makes the caller's expected API semantics unambiguous; the supported outcome is to keep integration behavior aligned with a supported request contract, whereas this scenario requires the ability to avoid rejecting tool schemas because serialized values are invalid; relying on an arbitrary undocumented default is fragile.
Question 66
A team maintaining a Claude application needs to keep external tool connectors compatible after client upgrades. Which implementation most directly satisfies the requirement?
- Track MCP server versions and contracts
- Put repository guidance in CLAUDE.md
- Roll out configuration through reviewed changes
- Validate configuration at startup
Explanation
Correct Answer
A:Declared versions and integration tests expose resource or schema changes before deployment; this behavior directly supports the need to keep external tool connectors compatible after client upgrades. Automatically using the newest connector can alter behavior unexpectedly.
Incorrect Answers
B:Repository memory files provide persistent instructional context to coding sessions; this applies to the different goal to give Claude Code the project's build, test, and architecture conventions, not the requirement to keep external tool connectors compatible after client upgrades; they are not an application secrets manager or the API's global system prompt.
C:When an application needs to prevent an untested tool-allowlist edit from reaching all developers immediately, change review and versioning provide accountability and a tested rollback path; the current capability must instead keep external tool connectors compatible after client upgrades, while undocumented local overrides create configuration drift.
D:Startup checks surface missing required values before user traffic reaches a broken path; the supported outcome is to fail fast if a model ID or tool endpoint is absent in production, whereas this scenario requires the ability to keep external tool connectors compatible after client upgrades; a late runtime exception spreads one configuration defect across many requests.
Question 67
A design meeting for a customer platform platform concludes that two isolated services require different behavior: one must explain service limits or tool outages without leaking stack traces or secrets, and another must keep follow-up requests linked without exposing another tenant's messages. Which arrangement meets the specification?
- First component: Limit retained context to authorized history. Second component: Keep user tasks in the user message.
- First component: Keep user tasks in the user message. Second component: Create one session per user conversation.
- First component: Return user-friendly error states. Second component: Limit retained context to authorized history.
- First component: Return user-friendly error states. Second component: Create one session per user conversation.
Explanation
Correct Answer
D: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 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 keep follow-up requests linked without exposing another tenant's messages.
Incorrect Answers
A:The first proposal serves the different purpose to prevent a new user from inheriting another user's document excerpts instead of the assigned first role because context assembly must apply access checks before adding prior turns or retrieved evidence, 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 keep follow-up requests linked without exposing another tenant's messages.
B: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 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 keep follow-up requests linked without exposing another tenant's messages.
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 prevent a new user from inheriting another user's document excerpts instead of the assigned second role because context assembly must apply access checks before adding prior turns or retrieved evidence; their respective acceptance criteria are to explain service limits or tool outages without leaking stack traces or secrets and to keep follow-up requests linked without exposing another tenant's messages.
Question 68
A team maintaining a retrieval pipeline needs to reduce unsupported claims in answers about internal procedures. Which implementation most directly satisfies the requirement?
- Request evidence before conclusions
- State one measurable outcome per instruction
- Use a stepwise decomposition
- Separate system policy from user content
Explanation
Correct Answer
A:Asking for citations to provided excerpts promotes inspectable grounding and makes verification possible; this behavior directly supports the need to reduce unsupported claims in answers about internal procedures. A fabricated citation can still look plausible without source checking.
Incorrect Answers
B:Clear task goals and acceptance criteria reduce competing interpretations; this applies to the different goal to stop a summarizer from producing unrelated analysis instead of required action items, not the requirement to reduce unsupported claims in answers about internal procedures; a vague request for a good summary provides no testable target.
C:When an application needs to solve a complex migration comparison that requires several distinct checks, breaking the work into verifiable stages lets the application check intermediate artifacts; the current capability must instead reduce unsupported claims in answers about internal procedures, while simply increasing prompt length can make dependencies less clear.
D:Stable higher-priority instructions should be represented in the designated instruction channel; the supported outcome is to prevent a customer message from overriding the application's escalation rules, whereas this scenario requires the ability to reduce unsupported claims in answers about internal procedures; user text is the task data, not a privileged configuration surface.
Question 69
An engineering productivity team owns two independent components. The first must reduce turnaround when an agent asks for unrelated reads in the same response; the second must prevent a slow external inventory service from blocking an agent indefinitely. Which paired plan fulfills both?
- First component: Use the Claude Agent SDK for an integrated tool-driven agent. Second component: Set a tool execution timeout.
- First component: Preserve assistant tool-use content in conversation history. Second component: Use the Claude Agent SDK for an integrated tool-driven agent.
- First component: Execute independent requested tools concurrently. Second component: Preserve assistant tool-use content in conversation history.
- First component: Execute independent requested tools concurrently. Second component: Set a tool execution timeout.
Explanation
Correct Answer
D:The first proposal fits its assigned role because parallel execution is safe for independent operations while every result must still be matched to its call ID, while the second proposal fits its assigned role because deadlines bound latency and convert stalled calls into explicit recoverable failures; their respective acceptance criteria are to reduce turnaround when an agent asks for unrelated reads in the same response and to prevent a slow external inventory service from blocking an agent indefinitely.
Incorrect Answers
A:The first proposal serves the different purpose to build a coding agent that needs managed tool execution, sessions, and event handling instead of the assigned first role because the SDK provides agent-loop primitives and integrations that remove much of the custom harness work, while the second proposal fits its assigned role because deadlines bound latency and convert stalled calls into explicit recoverable failures; their respective acceptance criteria are to reduce turnaround when an agent asks for unrelated reads in the same response and to prevent a slow external inventory service from blocking an agent indefinitely.
B:The first proposal serves the different purpose to maintain a valid transcript when the model requests multiple tools instead of the assigned first role because the next request retains the assistant message containing tool_use blocks before providing their user-role tool_result blocks, while the second proposal serves the different purpose to build a coding agent that needs managed tool execution, sessions, and event handling instead of the assigned second role because the SDK provides agent-loop primitives and integrations that remove much of the custom harness work; their respective acceptance criteria are to reduce turnaround when an agent asks for unrelated reads in the same response and to prevent a slow external inventory service from blocking an agent indefinitely.
C:The first proposal fits its assigned role because parallel execution is safe for independent operations while every result must still be matched to its call ID, while the second proposal serves the different purpose to maintain a valid transcript when the model requests multiple tools instead of the assigned second role because the next request retains the assistant message containing tool_use blocks before providing their user-role tool_result blocks; their respective acceptance criteria are to reduce turnaround when an agent asks for unrelated reads in the same response and to prevent a slow external inventory service from blocking an agent indefinitely.
Question 70
An architecture review of a production API product lists two distinct outcomes: the first subsystem must extract claims from a document while retaining its visual layout, and a second subsystem must distinguish an invalid request from a temporary provider or rate-limit failure. Which pair delivers these outcomes?
- First component: Supply a tool definition with input schema. Second component: Read the HTTP error status before retrying.
- First component: Include an image content block. Second component: Supply a tool definition with input schema.
- First component: Use supported document or PDF input. Second component: Include an image content block.
- First component: Use supported document or PDF input. Second component: Read the HTTP error status before retrying.
Explanation
Correct Answer
D:The first proposal fits its assigned role because document-aware input lets a capable model consider page content and graphics when supported, while the second proposal fits its assigned role because status codes and structured errors guide correction versus bounded retry; their respective acceptance criteria are to extract claims from a document while retaining its visual layout and to distinguish an invalid request from a temporary provider or rate-limit failure.
Incorrect Answers
A:The first proposal serves the different purpose to let Claude request a read-only inventory lookup with typed arguments instead of the assigned first role because a declared tool name, description, and schema constrain the interface offered to the model, while the second proposal fits its assigned role because status codes and structured errors guide correction versus bounded retry; their respective acceptance criteria are to extract claims from a document while retaining its visual layout and to distinguish an invalid request from a temporary provider or rate-limit failure.
B:The first proposal serves the different purpose to analyze a photographed shipping label with the supported multimodal Messages input instead of the assigned first role because image inputs are supplied as typed content with appropriate source data or references, while the second proposal serves the different purpose to let Claude request a read-only inventory lookup with typed arguments instead of the assigned second role because a declared tool name, description, and schema constrain the interface offered to the model; their respective acceptance criteria are to extract claims from a document while retaining its visual layout and to distinguish an invalid request from a temporary provider or rate-limit failure.
C:The first proposal fits its assigned role because document-aware input lets a capable model consider page content and graphics when supported, while the second proposal serves the different purpose to analyze a photographed shipping label with the supported multimodal Messages input instead of the assigned second role because image inputs are supplied as typed content with appropriate source data or references; their respective acceptance criteria are to extract claims from a document while retaining its visual layout and to distinguish an invalid request from a temporary provider or rate-limit failure.