Anthropic CCDV-F (Claude Certified Developer - Foundations) Practice Test 64

Question 630

The acceptance criteria for an inference routing change state that it must prevent a background processor from overwhelming the upstream API during bursts. Which implementation aligns with that criterion?

  1. Parse responses by content block type
  2. Use direct HTTP REST integration for unsupported runtimes
  3. Use JSON-safe types in request bodies
  4. Honor server rate-limit signals
  5. Separate transport failures from model refusals

Explanation

Correct Answer

D:

Throttling and backoff work with provider limits rather than assuming infinite request capacity; this behavior directly supports the need to prevent a background processor from overwhelming the upstream API during bursts. Parallelism beyond quota can reduce successful throughput.

Incorrect Answers

A:

Structured outputs can contain different block kinds that need type-aware handling; the supported outcome is to avoid treating a tool call or thinking block as user-visible answer text, whereas this scenario requires the ability to prevent a background processor from overwhelming the upstream API during bursts; concatenating arbitrary block payloads risks displaying internal control data.

B:

This approach serves the separate need to call the Messages endpoint from a language without a mature provider SDK because a standards-based HTTP client can send JSON requests with the correct headers and decode responses; it does not establish the outcome to prevent a background processor from overwhelming the upstream API during bursts, and a wrapper package is optional, not the underlying API transport.

C:

Structured request encoding enforces objects, arrays, strings, booleans, and numeric representations; despite being useful when a service must avoid rejecting tool schemas because serialized values are invalid, it is not a solution to prevent a background processor from overwhelming the upstream API during bursts; python object repr strings are not valid JSON contracts.

E:

A transport error occurs before a valid application-level completion; refusals are model outcomes; this applies to the different goal to surface network timeouts differently from a completed response that declines a task, not the requirement to prevent a background processor from overwhelming the upstream API during bursts; treating both as one generic retry condition can loop endlessly.

Question 631

During acceptance testing for an MCP interoperability service, one requirement is to verify that tools and resources are discoverable before integrating an agent. What should the developer implement?

  1. Apply authorization inside the MCP server
  2. Expose an MCP prompt template
  3. Validate MCP tool schemas and results
  4. Test protocol behavior with a compliant inspector

Explanation

Correct Answer

D:

A protocol test client exposes handshake, capability, and schema problems independently of model behavior; this behavior directly supports the need to verify that tools and resources are discoverable before integrating an agent. Debugging the assistant's prompt is ineffective when the server cannot negotiate correctly.

Incorrect Answers

A:

When an application needs to prevent a valid MCP client from reading another tenant's resources, the server must enforce caller identity and resource scope on each operation; the current capability must instead verify that tools and resources are discoverable before integrating an agent, while tool discovery is not proof that a user may invoke a capability on all records.

B:

Prompts describe reusable message templates or workflows offered by the server; the supported outcome is to share a repeatable analyst workflow across supported clients, whereas this scenario requires the ability to verify that tools and resources are discoverable before integrating an agent; a prompt template does not itself execute a database update.

C:

This approach serves the separate need to prevent a server update from returning incompatible payloads to clients because contract tests check declared capabilities, argument shapes, and expected response content; it does not establish the outcome to verify that tools and resources are discoverable before integrating an agent, and successful connection does not prove semantic correctness.

Question 632

After pilot feedback, a customer platform group needs two independent improvements. The first is to keep a downstream parser from crashing when a request returns no usable text block; the second is to separate an end user's request from the developer's stable operating instructions. Which engineering proposal handles both?

  1. First component: Treat retrieval results as untrusted data. Second component: Add cancellation handling to streaming UI.
  2. First component: Add cancellation handling to streaming UI. Second component: Keep user tasks in the user message.
  3. First component: Handle empty and partial model responses. Second component: Keep user tasks in the user message.
  4. First component: Handle empty and partial model responses. Second component: Treat retrieval results as untrusted data.

Explanation

Correct Answer

C:

The first proposal fits its assigned 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 explicit message roles distinguish requested work from higher-priority operational framing; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to separate an end user's request from the developer's stable operating instructions.

Incorrect Answers

A:

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 serves the different purpose to stop processing when a user cancels a long report and release resources cleanly instead of the assigned second role because cancellation signals should propagate through streams, queues, and workers where supported; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to separate an end user's request from the developer's stable operating instructions.

B:

The first proposal serves the different purpose to stop processing when a user cancels a long report and release resources cleanly instead of the assigned first role because cancellation signals should propagate through streams, queues, and workers where supported, while the second proposal fits its assigned role because explicit message roles distinguish requested work from higher-priority operational framing; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to separate an end user's request from the developer's stable operating instructions.

D:

The first proposal fits its assigned role because content-aware response handling checks block types, stop reasons, and required values before proceeding, 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 keep a downstream parser from crashing when a request returns no usable text block and to separate an end user's request from the developer's stable operating instructions.

Question 633

Two features of a backend integration system are under review. One feature must analyze a photographed shipping label with the supported multimodal Messages input; the other must let Claude request a read-only inventory lookup with typed arguments. Which plan matches the respective needs?

  1. First component: Send tool_result content back to Claude. Second component: Call the Messages API with explicit model and max_tokens.
  2. First component: Include an image content block. Second component: Send tool_result content back to Claude.
  3. First component: Call the Messages API with explicit model and max_tokens. Second component: Supply a tool definition with input schema.
  4. First component: Include an image content block. Second component: Supply a tool definition with input schema.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because image inputs are supplied as typed content with appropriate source data or references, while the second proposal fits its assigned role because a declared tool name, description, and schema constrain the interface offered to the model; their respective acceptance criteria are to analyze a photographed shipping label with the supported multimodal Messages input and to let Claude request a read-only inventory lookup with typed arguments.

Incorrect Answers

A:

The first proposal serves the different purpose to produce a user-facing answer after a successful inventory lookup instead of the assigned first role because a result block tied to the tool call returns the external observation to the model for synthesis, while the second proposal serves the different purpose to return an answer to a short user request through a backend service instead of the assigned second role because a message request identifies the target model, a message list, and an output-token ceiling; their respective acceptance criteria are to analyze a photographed shipping label with the supported multimodal Messages input and to let Claude request a read-only inventory lookup with typed arguments.

B:

The first proposal fits its assigned role because image inputs are supplied as typed content with appropriate source data or references, while the second proposal serves the different purpose to produce a user-facing answer after a successful inventory lookup instead of the assigned second role because a result block tied to the tool call returns the external observation to the model for synthesis; their respective acceptance criteria are to analyze a photographed shipping label with the supported multimodal Messages input and to let Claude request a read-only inventory lookup with typed arguments.

C:

The first proposal serves the different purpose to return an answer to a short user request through a backend service instead of the assigned first role because a message request identifies the target model, a message list, and an output-token ceiling, while the second proposal fits its assigned role because a declared tool name, description, and schema constrain the interface offered to the model; their respective acceptance criteria are to analyze a photographed shipping label with the supported multimodal Messages input and to let Claude request a read-only inventory lookup with typed arguments.

Question 634

An inference routing solution has parallel requirements with separate owners. Workstream one must reduce token spend without losing facts needed for the current request; workstream two must prevent request timestamps from invalidating a costly static prefix. Which combination meets both?

  1. First component: Use batch pricing where deadline permits. Second component: Keep volatile fields after reusable context.
  2. First component: Shorten irrelevant conversation history. Second component: Keep volatile fields after reusable context.
  3. First component: Cache a stable shared prefix. Second component: Use batch pricing where deadline permits.
  4. First component: Shorten irrelevant conversation history. Second component: Cache a stable shared prefix.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because selective context assembly preserves active constraints while removing obsolete turns, while the second proposal fits its assigned role because stable instruction and reference sections should precede changing per-request details for effective prefix reuse; their respective acceptance criteria are to reduce token spend without losing facts needed for the current request and to prevent request timestamps from invalidating a costly static prefix.

Incorrect Answers

A:

The first proposal serves the different purpose to lower spend for large scheduled classification jobs that do not need immediate responses instead of the assigned first role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal fits its assigned role because stable instruction and reference sections should precede changing per-request details for effective prefix reuse; their respective acceptance criteria are to reduce token spend without losing facts needed for the current request and to prevent request timestamps from invalidating a costly static prefix.

C:

The first proposal serves the different purpose to reduce repeated processing of identical tool definitions and system instructions instead of the assigned first role because prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match, while the second proposal serves the different purpose to lower spend for large scheduled classification jobs that do not need immediate responses instead of the assigned second role because asynchronous batch processing can offer a cost-effective throughput path under supported terms; their respective acceptance criteria are to reduce token spend without losing facts needed for the current request and to prevent request timestamps from invalidating a costly static prefix.

D:

The first proposal fits its assigned role because selective context assembly preserves active constraints while removing obsolete turns, while the second proposal serves the different purpose to reduce repeated processing of identical tool definitions and system instructions instead of the assigned second role because prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match; their respective acceptance criteria are to reduce token spend without losing facts needed for the current request and to prevent request timestamps from invalidating a costly static prefix.

Question 635

A data pipeline build contains an upstream function and a separate downstream function. The upstream work must uncover prompt-injection paths through retrieved webpages and connected tools; the downstream work must identify rising error rates and latency after launch. Which configuration pair covers both?

  1. First component: Implement automated regression tests. Second component: Instrument production observability.
  2. First component: Perform a threat review before go-live. Second component: Set a maintenance and deprecation plan.
  3. First component: Assign an owner to every integration. Second component: Set a maintenance and deprecation plan.
  4. First component: Perform a threat review before go-live. Second component: Instrument production observability.
  5. First component: Set a maintenance and deprecation plan. Second component: Implement automated regression tests.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss, 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 uncover prompt-injection paths through retrieved webpages and connected tools and to identify rising error rates and latency after launch.

Incorrect Answers

A:

The first proposal serves the different purpose to catch schema and policy failures after a model or tool update instead of the assigned first 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 uncover prompt-injection paths through retrieved webpages and connected tools and to identify rising error rates and latency after launch.

B:

The first proposal fits its assigned 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 keep an integration functional when a pinned model version approaches retirement instead of the assigned second role because a dependency inventory and upgrade schedule create time for evaluation and migration; their respective acceptance criteria are to uncover prompt-injection paths through retrieved webpages and connected tools and to identify rising error rates and latency after launch.

C:

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 serves the different purpose to keep an integration functional when a pinned model version approaches retirement instead of the assigned second role because a dependency inventory and upgrade schedule create time for evaluation and migration; their respective acceptance criteria are to uncover prompt-injection paths through retrieved webpages and connected tools and to identify rising error rates and latency after launch.

E:

The first proposal serves the different purpose to keep an integration functional when a pinned model version approaches retirement instead of the assigned first role because a dependency inventory and upgrade schedule create time for evaluation and migration, while the second proposal serves the different purpose to catch schema and policy failures after a model or tool update instead of the assigned second role because repeatable cases compare changes against documented acceptance criteria; their respective acceptance criteria are to uncover prompt-injection paths through retrieved webpages and connected tools and to identify rising error rates and latency after launch.

Question 636

A release plan for an engineering productivity platform has two acceptance checks: component one must reject a shell command that targets protected deployment secrets before execution; component two must retain complete control over a small set of proprietary tool calls and their execution order. Which proposal passes both?

  1. First component: Use PreToolUse gating for dangerous operations. Second component: Implement a custom Messages API tool loop.
  2. First component: Keep user-specific state out of a shared agent process. Second component: Implement a custom Messages API tool loop.
  3. First component: Use PreToolUse gating for dangerous operations. Second component: Choose isolated sandbox execution for untrusted code.
  4. First component: Choose isolated sandbox execution for untrusted code. Second component: Keep user-specific state out of a shared agent process.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because a pre-execution hook can examine a proposed action and block it through a deterministic policy, while the second proposal fits its assigned role because the application receives tool requests, validates inputs, executes authorized functions, and sends tool results back; their respective acceptance criteria are to reject a shell command that targets protected deployment secrets before execution and to retain complete control over a small set of proprietary tool calls and their execution order.

Incorrect Answers

B:

The first proposal serves the different purpose to serve many tenants without mixing their tool outputs or prior messages instead of the assigned first role because per-request identity and session boundaries prevent cross-tenant context leakage, while the second proposal fits its assigned role because the application receives tool requests, validates inputs, executes authorized functions, and sends tool results back; their respective acceptance criteria are to reject a shell command that targets protected deployment secrets before execution and to retain complete control over a small set of proprietary tool calls and their execution order.

C:

The first proposal fits its assigned role because a pre-execution hook can examine a proposed action and block it through a deterministic policy, while the second proposal serves the different purpose to let an agent run generated scripts without exposing production host files instead of the assigned second role because a restricted execution environment limits filesystem, network, and resource privileges; their respective acceptance criteria are to reject a shell command that targets protected deployment secrets before execution and to retain complete control over a small set of proprietary tool calls and their execution order.

D:

The first proposal serves the different purpose to let an agent run generated scripts without exposing production host files instead of the assigned first role because a restricted execution environment limits filesystem, network, and resource privileges, while the second proposal serves the different purpose to serve many tenants without mixing their tool outputs or prior messages instead of the assigned second role because per-request identity and session boundaries prevent cross-tenant context leakage; their respective acceptance criteria are to reject a shell command that targets protected deployment secrets before execution and to retain complete control over a small set of proprietary tool calls and their execution order.

Question 637

Two separate tickets in an MCP interoperability backlog require different controls. One needs to call a protected internal pricing API under the application's own credentials; the other needs to delegate a security analysis while keeping the main coordinator's context concise. Which implementation pair is correct?

  1. First component: Use a deterministic workflow for fixed stages. Second component: Use subagents for independent expertise.
  2. First component: Use system or repository instructions for stable behavior. Second component: Use a deterministic workflow for fixed stages.
  3. First component: Create a custom client-side tool. Second component: Use subagents for independent expertise.
  4. First component: Create a custom client-side tool. Second component: Use system or repository instructions for stable behavior.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because local execution gives the developer direct control over authentication, validation, and side effects, while the second proposal fits its assigned role because specialist contexts reduce tool-output contamination and support focused parallel work; their respective acceptance criteria are to call a protected internal pricing API under the application's own credentials and to delegate a security analysis while keeping the main coordinator's context concise.

Incorrect Answers

A:

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 fits its assigned role because specialist contexts reduce tool-output contamination and support focused parallel work; their respective acceptance criteria are to call a protected internal pricing API under the application's own credentials and to delegate a security analysis while keeping the main coordinator's context concise.

B:

The first proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned first role because instructions shape model behavior and task framing without executing external operations, 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 call a protected internal pricing API under the application's own credentials and to delegate a security analysis while keeping the main coordinator's context concise.

D:

The first proposal fits its assigned role because local execution gives the developer direct control over authentication, validation, and side effects, while the second proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned second role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to call a protected internal pricing API under the application's own credentials and to delegate a security analysis while keeping the main coordinator's context concise.

Question 638

A technical lead requests a solution that can avoid exposing raw production database credentials directly to an agent within a customer platform project. Which design should be chosen?

  1. Isolate tools behind a service layer
  2. Separate model reasoning from authoritative calculations
  3. Create one session per user conversation
  4. Deduplicate application events

Explanation

Correct Answer

A:

A mediation service validates identity, arguments, authorization, and audit logs for each requested action; this behavior directly supports the need to avoid exposing raw production database credentials directly to an agent. A natural-language tool description is not an access-control boundary.

Incorrect Answers

B:

Deterministic services can enforce exact formulas and rounding before the model explains the result; the supported outcome is to compute discounts through verified business code rather than generated arithmetic alone, whereas this scenario requires the ability to avoid exposing raw production database credentials directly to an agent; a plausible model narrative is not a reliable financial ledger.

C:

This approach serves the separate need to keep follow-up requests linked without exposing another tenant's messages because session scoping ensures history and tool results belong to the correct principal; it does not establish the outcome to avoid exposing raw production database credentials directly to an agent, and a global conversation list risks mixing private records.

D:

An idempotent job key lets the server recognize duplicates at its request boundary; despite being useful when a service must avoid starting two extraction jobs for the same uploaded document after repeated browser submissions, it is not a solution to avoid exposing raw production database credentials directly to an agent; model prompting cannot identify all retries arriving from outside the conversation.

Question 639

Two separate tickets in a backend integration backlog require different controls. One needs to keep an interrupted invoice-creation request from generating duplicate invoices; the other needs to recover from transient 429 responses without synchronized retry storms. Which implementation pair is correct?

  1. First component: Keep secrets out of source control. Second component: Validate webhook signatures.
  2. First component: Use explicit HTTP method semantics. Second component: Keep secrets out of source control.
  3. First component: Avoid retrying non-idempotent writes blindly. Second component: Use exponential backoff with jitter.
  4. First component: Validate webhook signatures. Second component: Use exponential backoff with jitter.
  5. First component: Avoid retrying non-idempotent writes blindly. Second component: Keep secrets out of source control.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because retries of side-effecting actions need idempotency keys or transaction reconciliation, while the second proposal fits its assigned role because increasing randomized delays reduce contention and respect service throttling signals; their respective acceptance criteria are to keep an interrupted invoice-creation request from generating duplicate invoices and to recover from transient 429 responses without synchronized retry storms.

Incorrect Answers

A:

The first proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned first role because secret stores or environment injection keep production tokens out of committed code, while the second proposal serves the different purpose to reject forged callbacks from an external asynchronous job service instead of the assigned second role because cryptographic verification checks the sender and payload integrity before processing the event; their respective acceptance criteria are to keep an interrupted invoice-creation request from generating duplicate invoices and to recover from transient 429 responses without synchronized retry storms.

B:

The first proposal serves the different purpose to prevent a supposedly read-only status lookup from changing a server-side record instead of the assigned first role because gET should retrieve resources while state changes use appropriate mutation methods and authorization checks, while the second proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned second role because secret stores or environment injection keep production tokens out of committed code; their respective acceptance criteria are to keep an interrupted invoice-creation request from generating duplicate invoices and to recover from transient 429 responses without synchronized retry storms.

D:

The first proposal serves the different purpose to reject forged callbacks from an external asynchronous job service instead of the assigned first role because cryptographic verification checks the sender and payload integrity before processing the event, while the second proposal fits its assigned role because increasing randomized delays reduce contention and respect service throttling signals; their respective acceptance criteria are to keep an interrupted invoice-creation request from generating duplicate invoices and to recover from transient 429 responses without synchronized retry storms.

E:

The first proposal fits its assigned role because retries of side-effecting actions need idempotency keys or transaction reconciliation, while the second proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned second role because secret stores or environment injection keep production tokens out of committed code; their respective acceptance criteria are to keep an interrupted invoice-creation request from generating duplicate invoices and to recover from transient 429 responses without synchronized retry storms.

Question 640

Engineers are splitting a tool integration service into two independently tested functions. Function A must use an already supported capability without hosting a duplicate custom service, while function B must enable a customer service agent to prepare but not autonomously approve account closures. Which plan is sound?

  1. First component: Use system or repository instructions for stable behavior. Second component: Combine tool access with human confirmation.
  2. First component: Choose a built-in provider tool. Second component: Combine tool access with human confirmation.
  3. First component: Choose a built-in provider tool. Second component: Create a custom client-side tool.
  4. First component: Create a custom client-side tool. Second component: Use system or repository instructions for stable behavior.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because provider-managed execution can reduce implementation work when its scope matches the requirement, while the second proposal fits its assigned role because tools supply actionable capabilities while a separate approval step governs sensitive execution; their respective acceptance criteria are to use an already supported capability without hosting a duplicate custom service and to enable a customer service agent to prepare but not autonomously approve account closures.

Incorrect Answers

A:

The first proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned first role because instructions shape model behavior and task framing without executing external operations, while the second proposal fits its assigned role because tools supply actionable capabilities while a separate approval step governs sensitive execution; their respective acceptance criteria are to use an already supported capability without hosting a duplicate custom service and to enable a customer service agent to prepare but not autonomously approve account closures.

C:

The first proposal fits its assigned role because provider-managed execution can reduce implementation work when its scope matches the requirement, while the second proposal serves the different purpose to call a protected internal pricing API under the application's own credentials instead of the assigned second role because local execution gives the developer direct control over authentication, validation, and side effects; their respective acceptance criteria are to use an already supported capability without hosting a duplicate custom service and to enable a customer service agent to prepare but not autonomously approve account closures.

D:

The first proposal serves the different purpose to call a protected internal pricing API under the application's own credentials instead of the assigned first role because local execution gives the developer direct control over authentication, validation, and side effects, while the second proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned second role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to use an already supported capability without hosting a duplicate custom service and to enable a customer service agent to prepare but not autonomously approve account closures.

Claude Certified Developer - Foundations (CCDV-F) Practice Tests