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

Question 360

The current design of an external system access pipeline does not adequately make one internal ticketing connector available to several agent clients. Which improvement resolves the gap?

  1. Use an autonomous agent for exploratory work
  2. Use subagents for independent expertise
  3. Publish an MCP server for reusable integrations
  4. Use system or repository instructions for stable behavior

Explanation

Correct Answer

C:

MCP standardizes tool and resource discovery across compatible applications; this behavior directly supports the need to make one internal ticketing connector available to several agent clients. Duplicated per-client wrappers increase maintenance across a growing ecosystem.

Incorrect Answers

A:

Model-directed planning supports adaptive sequences when the next action is not known in advance; the supported outcome is to perform open-ended troubleshooting where tool selection changes after each observation, whereas this scenario requires the ability to make one internal ticketing connector available to several agent clients; a rigid workflow struggles with unforeseen branches without extensive coding.

B:

This approach serves the separate need to delegate a security analysis while keeping the main coordinator's context concise because specialist contexts reduce tool-output contamination and support focused parallel work; it does not establish the outcome to make one internal ticketing connector available to several agent clients, and a reusable Skill alone does not create an independent worker with separate state.

D:

For the alternate objective to make a coding or API assistant follow organization-wide conventions, instructions shape model behavior and task framing without executing external operations; the feature here must make one internal ticketing connector available to several agent clients, and descriptive rules do not replace programmatic validation or IAM.

Question 361

A tool integration group is preparing a production change intended to make a versioned product catalog available for read-oriented context retrieval. Which technique matches that intent?

  1. Expose an MCP tool for an external action
  2. Expose an MCP resource for reference content
  3. Expose an MCP prompt template
  4. Test protocol behavior with a compliant inspector

Explanation

Correct Answer

B:

Resources provide identifiable data that clients can fetch for model context; this behavior directly supports the need to make a versioned product catalog available for read-oriented context retrieval. Treating static content as a privileged executable tool unnecessarily expands authority.

Incorrect Answers

A:

When an application needs to let multiple compatible clients request a controlled shipment lookup, MCP tools advertise callable operations with named parameters and schemas across client integrations; the current capability must instead make a versioned product catalog available for read-oriented context retrieval, while a resource intended only for reading context does not perform arbitrary commands.

C:

This approach serves the separate need to share a repeatable analyst workflow across supported clients because prompts describe reusable message templates or workflows offered by the server; it does not establish the outcome to make a versioned product catalog available for read-oriented context retrieval, and a prompt template does not itself execute a database update.

D:

A protocol test client exposes handshake, capability, and schema problems independently of model behavior; despite being useful when a service must verify that tools and resources are discoverable before integrating an agent, it is not a solution to make a versioned product catalog available for read-oriented context retrieval; debugging the assistant's prompt is ineffective when the server cannot negotiate correctly.

Question 362

An architecture review of an operations orchestration product lists two distinct outcomes: the first subsystem must keep a customer service application operating when an expensive specialist agent cannot complete, and a second subsystem must preserve customer preferences across permitted sessions while distinguishing facts from assumptions. Which pair delivers these outcomes?

  1. First component: Use a graceful fallback path. Second component: Use a graph with conditional edges.
  2. First component: Use a graceful fallback path. Second component: Use bounded memory with explicit provenance.
  3. First component: Use a graph with conditional edges. Second component: Delegate narrow subtasks with a separate context.
  4. First component: Delegate narrow subtasks with a separate context. Second component: Use bounded memory with explicit provenance.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely, while the second proposal fits its assigned role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to keep a customer service application operating when an expensive specialist agent cannot complete and to preserve customer preferences across permitted sessions while distinguishing facts from assumptions.

Incorrect Answers

A:

The first proposal fits its assigned role because a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely, while the second proposal serves the different purpose to branch between remediation and escalation based on the result of a security scan instead of the assigned second role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes; their respective acceptance criteria are to keep a customer service application operating when an expensive specialist agent cannot complete and to preserve customer preferences across permitted sessions while distinguishing facts from assumptions.

C:

The first proposal serves the different purpose to branch between remediation and escalation based on the result of a security scan instead of the assigned first role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal serves the different purpose to protect a coordinator's window from huge specialist tool outputs instead of the assigned second role because each subagent can work in a bounded context and return a concise, verified artifact; their respective acceptance criteria are to keep a customer service application operating when an expensive specialist agent cannot complete and to preserve customer preferences across permitted sessions while distinguishing facts from assumptions.

D:

The first proposal serves the different purpose to protect a coordinator's window from huge specialist tool outputs instead of the assigned first role because each subagent can work in a bounded context and return a concise, verified artifact, while the second proposal fits its assigned role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to keep a customer service application operating when an expensive specialist agent cannot complete and to preserve customer preferences across permitted sessions while distinguishing facts from assumptions.

Question 363

An engineer extending a customer platform workflow has been asked to display a long report as it is generated rather than waiting for the full completion. Which choice addresses the request most precisely?

  1. Submit a Message Batch for offline jobs
  2. Call the Messages API with explicit model and max_tokens
  3. Use supported document or PDF input
  4. Use SSE streaming for partial response delivery

Explanation

Correct Answer

D:

Streaming yields ordered events and content deltas that the client assembles into the final response; this behavior directly supports the need to display a long report as it is generated rather than waiting for the full completion. Treating each delta as an independent complete answer can corrupt the UI.

Incorrect Answers

A:

Batches suit asynchronous throughput-oriented workloads, with results retrieved after processing; the supported outcome is to process thousands of nightly documents without interactive deadlines, whereas this scenario requires the ability to display a long report as it is generated rather than waiting for the full completion; a batch submission does not provide an immediate response for a live chat.

B:

This approach serves the separate need to return an answer to a short user request through a backend service because a message request identifies the target model, a message list, and an output-token ceiling; it does not establish the outcome to display a long report as it is generated rather than waiting for the full completion, and the API is not a stateful chat session unless prior turns are supplied.

C:

Document-aware input lets a capable model consider page content and graphics when supported; despite being useful when a service must extract claims from a document while retaining its visual layout, it is not a solution to display a long report as it is generated rather than waiting for the full completion; pasting only extracted text can discard useful visual context.

Question 364

Engineers are splitting a customer platform service into two independently tested functions. Function A must let reviewers trace each summary claim to its authoritative document version, while function B must let an operator approve a proposed customer-address change before submission. Which plan is sound?

  1. First component: Add cancellation handling to streaming UI. Second component: Return user-friendly error states.
  2. First component: Add explicit provenance to retrieved evidence. Second component: Expose a review screen before tool-based writes.
  3. First component: Return user-friendly error states. Second component: Expose a review screen before tool-based writes.
  4. First component: Add explicit provenance to retrieved evidence. Second component: Add cancellation handling to streaming UI.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because source identifiers, timestamps, and passage boundaries make citations and later audits possible, while the second proposal fits its assigned role because a confirmation UI converts a model suggestion into a separately authorized human action; their respective acceptance criteria are to let reviewers trace each summary claim to its authoritative document version and to let an operator approve a proposed customer-address change before submission.

Incorrect Answers

A:

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 serves the different purpose to explain service limits or tool outages without leaking stack traces or secrets instead of the assigned second role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs; their respective acceptance criteria are to let reviewers trace each summary claim to its authoritative document version and to let an operator approve a proposed customer-address change before submission.

C:

The first proposal serves the different purpose to explain service limits or tool outages without leaking stack traces or secrets instead of the assigned first role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs, while the second proposal fits its assigned role because a confirmation UI converts a model suggestion into a separately authorized human action; their respective acceptance criteria are to let reviewers trace each summary claim to its authoritative document version and to let an operator approve a proposed customer-address change before submission.

D:

The first proposal fits its assigned role because source identifiers, timestamps, and passage boundaries make citations and later audits possible, 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 let reviewers trace each summary claim to its authoritative document version and to let an operator approve a proposed customer-address change before submission.

Question 365

After pilot feedback, a backend integration group needs two independent improvements. The first is to deploy a prompt change without exposing every customer to an untested regression; the second is to test whether document classification quality is viable on representative files. Which engineering proposal handles both?

  1. First component: Implement automated regression tests. Second component: Instrument production observability.
  2. First component: Instrument production observability. Second component: Use a proof of concept before production commitment.
  3. First component: Define a staged release with rollback. Second component: Use a proof of concept before production commitment.
  4. First component: Define a staged release with rollback. Second component: Implement automated regression tests.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because gradual rollout and versioned rollback allow metrics to be compared while limiting impact, while the second proposal fits its assigned role because a small pilot reduces feasibility risk before funding a complete integration; their respective acceptance criteria are to deploy a prompt change without exposing every customer to an untested regression and to test whether document classification quality is viable on representative files.

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 serves the different purpose to identify rising error rates and latency after launch instead of the assigned second role because logs, metrics, traces, and alert thresholds reveal operational failures at the right layer; their respective acceptance criteria are to deploy a prompt change without exposing every customer to an untested regression and to test whether document classification quality is viable on representative files.

B:

The first proposal serves the different purpose to identify rising error rates and latency after launch instead of the assigned first role because logs, metrics, traces, and alert thresholds reveal operational failures at the right layer, while the second proposal fits its assigned role because a small pilot reduces feasibility risk before funding a complete integration; their respective acceptance criteria are to deploy a prompt change without exposing every customer to an untested regression and to test whether document classification quality is viable on representative files.

D:

The first proposal fits its assigned role because gradual rollout and versioned rollback allow metrics to be compared while limiting impact, 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 deploy a prompt change without exposing every customer to an untested regression and to test whether document classification quality is viable on representative files.

Question 366

Two separate tickets in a Claude application backlog require different controls. One needs to prevent a malicious help article from ordering the model to reveal secrets; the other needs to separate an end user's request from the developer's stable operating instructions. Which implementation pair is correct?

  1. First component: Limit retained context to authorized history. Second component: Use bounded retrieval results.
  2. First component: Treat retrieval results as untrusted data. Second component: Limit retained context to authorized history.
  3. First component: Treat retrieval results as untrusted data. Second component: Keep user tasks in the user message.
  4. First component: Place durable behavior instructions in the system parameter. Second component: Limit retained context to authorized history.
  5. First component: Use bounded retrieval results. Second component: Keep user tasks in the user message.

Explanation

Correct Answer

C:

The first proposal fits its assigned 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 explicit message roles distinguish requested work from higher-priority operational framing; their respective acceptance criteria are to prevent a malicious help article from ordering the model to reveal secrets 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 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 avoid burying the relevant contract clause beneath hundreds of low-value passages instead of the assigned second role because ranking and a context budget prioritize high-quality evidence while controlling input tokens; their respective acceptance criteria are to prevent a malicious help article from ordering the model to reveal secrets and to separate an end user's request from the developer's stable operating instructions.

B:

The first proposal fits its assigned 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 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 prevent a malicious help article from ordering the model to reveal secrets and to separate an end user's request from the developer's stable operating instructions.

D:

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 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 prevent a malicious help article from ordering the model to reveal secrets and to separate an end user's request from the developer's stable operating instructions.

E:

The first proposal serves the different purpose to avoid burying the relevant contract clause beneath hundreds of low-value passages instead of the assigned first role because ranking and a context budget prioritize high-quality evidence while controlling input tokens, 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 prevent a malicious help article from ordering the model to reveal secrets and to separate an end user's request from the developer's stable operating instructions.

Question 367

A developer is reviewing alternatives for an incident response feature that must reject a shell command that targets protected deployment secrets before execution. Which option is a defensible fit?

  1. Use a durable session store
  2. Add idempotency keys to side-effecting operations
  3. Use PreToolUse gating for dangerous operations
  4. Use the Claude Agent SDK for an integrated tool-driven agent

Explanation

Correct Answer

C:

A pre-execution hook can examine a proposed action and block it through a deterministic policy; this behavior directly supports the need to reject a shell command that targets protected deployment secrets before execution. Post-execution logging cannot prevent a destructive command already run.

Incorrect Answers

A:

External persistence holds the conversation and workflow metadata needed to resume safely; despite being useful when a service must recover agent state when a container restarts during a lengthy customer case, it is not a solution to reject a shell command that targets protected deployment secrets before execution; process-local variables disappear with the worker.

B:

For the alternate objective to avoid charging a customer twice after a worker retries a timed-out payment action, application-generated operation identifiers allow the downstream service to recognize a repeated request; the feature here must reject a shell command that targets protected deployment secrets before execution, and model-level instructions cannot guarantee exactly-once execution after a partial failure.

D:

When an application needs to build a coding agent that needs managed tool execution, sessions, and event handling, the SDK provides agent-loop primitives and integrations that remove much of the custom harness work; the current capability must instead reject a shell command that targets protected deployment secrets before execution, while it still requires explicit permissions, safety policies, and operational boundaries.

Question 368

Engineers are splitting an output validation service into two independently tested functions. Function A must show model-produced HTML snippets without allowing browser script injection, while function B must recover malformed data without entering an infinite prompt-retry loop. Which plan is sound?

  1. First component: Escape generated content in the UI. Second component: Use bounded repair or regeneration.
  2. First component: Separate a partial streaming fragment from a finished object. Second component: Use bounded repair or regeneration.
  3. First component: Escape generated content in the UI. Second component: Check evidence alignment after extraction.
  4. First component: Check evidence alignment after extraction. Second component: Separate a partial streaming fragment from a finished object.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because output encoding or sanitization protects display contexts from untrusted markup, while the second proposal fits its assigned role because a limited correction attempt can use validation errors as feedback before escalating; their respective acceptance criteria are to show model-produced HTML snippets without allowing browser script injection and to recover malformed data without entering an infinite prompt-retry loop.

Incorrect Answers

B:

The first proposal serves the different purpose to prevent the frontend from parsing an incomplete JSON chunk as a complete response instead of the assigned first role because stream consumers must buffer and recognize completion before strict object validation, while the second proposal fits its assigned role because a limited correction attempt can use validation errors as feedback before escalating; their respective acceptance criteria are to show model-produced HTML snippets without allowing browser script injection and to recover malformed data without entering an infinite prompt-retry loop.

C:

The first proposal fits its assigned role because output encoding or sanitization protects display contexts from untrusted markup, while the second proposal serves the different purpose to detect plausible dates or amounts that are absent from the provided document instead of the assigned second role because semantic verification compares fields to authoritative source spans; their respective acceptance criteria are to show model-produced HTML snippets without allowing browser script injection and to recover malformed data without entering an infinite prompt-retry loop.

D:

The first proposal serves the different purpose to detect plausible dates or amounts that are absent from the provided document instead of the assigned first role because semantic verification compares fields to authoritative source spans, while the second proposal serves the different purpose to prevent the frontend from parsing an incomplete JSON chunk as a complete response instead of the assigned second role because stream consumers must buffer and recognize completion before strict object validation; their respective acceptance criteria are to show model-produced HTML snippets without allowing browser script injection and to recover malformed data without entering an infinite prompt-retry loop.

Question 369

Two features of an API reliability system are under review. One feature must prevent a bursty job service from exceeding allowed request throughput; the other must keep a batch pipeline resilient when the upstream service briefly fails. Which plan matches the respective needs?

  1. First component: Handle a 429 rate limit error. Second component: Investigate a 400 invalid_request error.
  2. First component: Investigate a 400 invalid_request error. Second component: Trace a missing tool_result.
  3. First component: Handle a 429 rate limit error. Second component: Diagnose a 5xx provider error.
  4. First component: Trace a missing tool_result. Second component: Diagnose a 5xx provider error.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because a bounded retry policy and workload shaping address quota or rate throttling, while the second proposal fits its assigned role because server-side failures may warrant bounded retries, jitter, and a fallback rather than request-shape changes; their respective acceptance criteria are to prevent a bursty job service from exceeding allowed request throughput and to keep a batch pipeline resilient when the upstream service briefly fails.

Incorrect Answers

A:

The first proposal fits its assigned role because a bounded retry policy and workload shaping address quota or rate throttling, while the second proposal serves the different purpose to diagnose a request that fails consistently before generating any model output instead of the assigned second role because validation failures point to malformed inputs or unsupported parameters that must be corrected; their respective acceptance criteria are to prevent a bursty job service from exceeding allowed request throughput and to keep a batch pipeline resilient when the upstream service briefly fails.

B:

The first proposal serves the different purpose to diagnose a request that fails consistently before generating any model output instead of the assigned first role because validation failures point to malformed inputs or unsupported parameters that must be corrected, while the second proposal serves the different purpose to fix an agent loop that repeatedly requests the same lookup without using the returned data instead of the assigned second role because inspecting message history and tool IDs reveals whether execution output reached the next model turn; their respective acceptance criteria are to prevent a bursty job service from exceeding allowed request throughput and to keep a batch pipeline resilient when the upstream service briefly fails.

D:

The first proposal serves the different purpose to fix an agent loop that repeatedly requests the same lookup without using the returned data instead of the assigned first role because inspecting message history and tool IDs reveals whether execution output reached the next model turn, while the second proposal fits its assigned role because server-side failures may warrant bounded retries, jitter, and a fallback rather than request-shape changes; their respective acceptance criteria are to prevent a bursty job service from exceeding allowed request throughput and to keep a batch pipeline resilient when the upstream service briefly fails.

Question 370

The acceptance criteria for an agent platform change state that it must retain complete control over a small set of proprietary tool calls and their execution order. Which implementation aligns with that criterion?

  1. Execute independent requested tools concurrently
  2. Implement a custom Messages API tool loop
  3. Use the Claude Agent SDK for an integrated tool-driven agent
  4. Deploy agent workers close to controlled data sources

Explanation

Correct Answer

B:

The application receives tool requests, validates inputs, executes authorized functions, and sends tool results back; this behavior directly supports the need to retain complete control over a small set of proprietary tool calls and their execution order. The Messages API does not automatically execute arbitrary client tools.

Incorrect Answers

A:

When an application needs to reduce turnaround when an agent asks for unrelated reads in the same response, parallel execution is safe for independent operations while every result must still be matched to its call ID; the current capability must instead retain complete control over a small set of proprietary tool calls and their execution order, while mutating tools with data dependencies should not be blindly parallelized.

C:

This approach serves the separate need to build a coding agent that needs managed tool execution, sessions, and event handling because the SDK provides agent-loop primitives and integrations that remove much of the custom harness work; it does not establish the outcome to retain complete control over a small set of proprietary tool calls and their execution order, and it still requires explicit permissions, safety policies, and operational boundaries.

D:

A self-hosted harness can enforce infrastructure, network, and retention controls for the surrounding tools; despite being useful when a service must meet a requirement that proprietary repository contents remain within an approved execution environment, it is not a solution to retain complete control over a small set of proprietary tool calls and their execution order; hosted orchestration does not automatically inherit a company's private-network policies.

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