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

Question 120

Engineers are splitting a document processing service into two independently tested functions. Function A must keep deployment behavior stable while evaluating new model releases separately, while function B must constrain a repository coding assistant's allowed tools and execution behavior. Which plan is sound?

  1. First component: Pin a tested model identifier. Second component: Use settings.json for Claude Code permissions.
  2. First component: Pin a tested model identifier. Second component: Put repository guidance in CLAUDE.md.
  3. First component: Track MCP server versions and contracts. Second component: Use settings.json for Claude Code permissions.
  4. First component: Put repository guidance in CLAUDE.md. Second component: Track MCP server versions and contracts.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because explicit model versions support reproducibility and controlled migrations, while the second proposal fits its assigned role because permission settings define configurable controls for Claude Code rather than merely describing preferences; their respective acceptance criteria are to keep deployment behavior stable while evaluating new model releases separately and to constrain a repository coding assistant's allowed tools and execution behavior.

Incorrect Answers

B:

The first proposal fits its assigned role because explicit model versions support reproducibility and controlled migrations, while the second proposal serves the different purpose to give Claude Code the project's build, test, and architecture conventions instead of the assigned second role because repository memory files provide persistent instructional context to coding sessions; their respective acceptance criteria are to keep deployment behavior stable while evaluating new model releases separately and to constrain a repository coding assistant's allowed tools and execution behavior.

C:

The first proposal serves the different purpose to keep external tool connectors compatible after client upgrades instead of the assigned first role because declared versions and integration tests expose resource or schema changes before deployment, while the second proposal fits its assigned role because permission settings define configurable controls for Claude Code rather than merely describing preferences; their respective acceptance criteria are to keep deployment behavior stable while evaluating new model releases separately and to constrain a repository coding assistant's allowed tools and execution behavior.

D:

The first proposal serves the different purpose to give Claude Code the project's build, test, and architecture conventions instead of the assigned first role because repository memory files provide persistent instructional context to coding sessions, while the second proposal serves the different purpose to keep external tool connectors compatible after client upgrades instead of the assigned second role because declared versions and integration tests expose resource or schema changes before deployment; their respective acceptance criteria are to keep deployment behavior stable while evaluating new model releases separately and to constrain a repository coding assistant's allowed tools and execution behavior.

Question 121

A data pipeline delivery milestone depends on two separate capabilities. One module must record complete streamed output and token usage accurately; a second module must process thousands of nightly documents without interactive deadlines. Which implementation option is appropriate?

  1. First component: Handle message_stop and final usage events. Second component: Submit a Message Batch for offline jobs.
  2. First component: Handle a refusal stop_reason safely. Second component: Submit a Message Batch for offline jobs.
  3. First component: Reconcile batch responses by custom_id. Second component: Handle a refusal stop_reason safely.
  4. First component: Handle message_stop and final usage events. Second component: Reconcile batch responses by custom_id.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because the final stream events signal completion and deliver accumulated metadata beyond individual text fragments, while the second proposal fits its assigned role because batches suit asynchronous throughput-oriented workloads, with results retrieved after processing; their respective acceptance criteria are to record complete streamed output and token usage accurately and to process thousands of nightly documents without interactive deadlines.

Incorrect Answers

B:

The first proposal serves the different purpose to avoid parsing safety refusals as valid JSON business records instead of the assigned first role because a refusal is a deliberate non-completion path that requires a defined application response, while the second proposal fits its assigned role because batches suit asynchronous throughput-oriented workloads, with results retrieved after processing; their respective acceptance criteria are to record complete streamed output and token usage accurately and to process thousands of nightly documents without interactive deadlines.

C:

The first proposal serves the different purpose to match returned batch results to the right source documents despite varying completion order instead of the assigned first role because a caller-assigned identifier links each result to the original request independently of result ordering, while the second proposal serves the different purpose to avoid parsing safety refusals as valid JSON business records instead of the assigned second role because a refusal is a deliberate non-completion path that requires a defined application response; their respective acceptance criteria are to record complete streamed output and token usage accurately and to process thousands of nightly documents without interactive deadlines.

D:

The first proposal fits its assigned role because the final stream events signal completion and deliver accumulated metadata beyond individual text fragments, while the second proposal serves the different purpose to match returned batch results to the right source documents despite varying completion order instead of the assigned second role because a caller-assigned identifier links each result to the original request independently of result ordering; their respective acceptance criteria are to record complete streamed output and token usage accurately and to process thousands of nightly documents without interactive deadlines.

Question 122

A technical lead requests a solution that can shorten latency and spend on tasks that need only basic categorization within a token economics project. Which design should be chosen?

  1. Use varied sampling only for ideation
  2. Use contrasting few-shot examples
  3. Use low-temperature generation for repeatable extraction
  4. Reduce reasoning effort on trivial routing

Explanation

Correct Answer

D:

Lower effort can suit predictable work where deeper reasoning adds little measurable quality; this behavior directly supports the need to shorten latency and spend on tasks that need only basic categorization. Using maximum effort for every request wastes resources.

Incorrect Answers

A:

This approach serves the separate need to brainstorm diverse naming candidates without demanding identical wording on every run because greater sampling diversity can produce a wider range of suggestions for exploratory work; it does not establish the outcome to shorten latency and spend on tasks that need only basic categorization, and it is not appropriate as the sole correctness control for structured production data.

B:

Multiple representative cases help define a decision boundary and reduce ambiguity; despite being useful when a service must distinguish borderline policy labels with examples of both allowed and disallowed cases, it is not a solution to shorten latency and spend on tasks that need only basic categorization; repeating near-identical samples does not cover edge cases.

C:

For the alternate objective to reduce variation when a service maps documents into consistent categories, lower randomness often improves consistency for narrow, constrained tasks; the feature here must shorten latency and spend on tasks that need only basic categorization, and it does not guarantee identical output or replace schema validation.

Question 123

Two separate tickets in a backend integration backlog require different controls. One needs to verify that a real staging tool and its API contract work together; the other needs to reproduce a working SDK installation across staging and production. Which implementation pair is correct?

  1. First component: Separate integration tests from unit tests. Second component: Pin dependencies with lockfiles.
  2. First component: Enforce concurrency limits. Second component: Use exponential backoff with jitter.
  3. First component: Use exponential backoff with jitter. Second component: Pin dependencies with lockfiles.
  4. First component: Separate integration tests from unit tests. Second component: Enforce concurrency limits.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal fits its assigned role because locked versions and hashes constrain drift between build environments; their respective acceptance criteria are to verify that a real staging tool and its API contract work together and to reproduce a working SDK installation across staging and production.

Incorrect Answers

B:

The first proposal serves the different purpose to prevent bursts of document jobs from overwhelming rate limits and memory instead of the assigned first role because a semaphore or bounded queue keeps in-flight work within measured capacity, while the second proposal serves the different purpose to recover from transient 429 responses without synchronized retry storms instead of the assigned second role because increasing randomized delays reduce contention and respect service throttling signals; their respective acceptance criteria are to verify that a real staging tool and its API contract work together and to reproduce a working SDK installation across staging and production.

C:

The first proposal serves the different purpose to recover from transient 429 responses without synchronized retry storms instead of the assigned first role because increasing randomized delays reduce contention and respect service throttling signals, while the second proposal fits its assigned role because locked versions and hashes constrain drift between build environments; their respective acceptance criteria are to verify that a real staging tool and its API contract work together and to reproduce a working SDK installation across staging and production.

D:

The first proposal fits its assigned role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal serves the different purpose to prevent bursts of document jobs from overwhelming rate limits and memory instead of the assigned second role because a semaphore or bounded queue keeps in-flight work within measured capacity; their respective acceptance criteria are to verify that a real staging tool and its API contract work together and to reproduce a working SDK installation across staging and production.

Question 124

An incident response review asks the team to close two unrelated gaps without merging their execution paths. Service A must preserve customer preferences across permitted sessions while distinguishing facts from assumptions; service B must protect a coordinator's window from huge specialist tool outputs. Which paired remediation works?

  1. First component: Use bounded memory with explicit provenance. Second component: Delegate narrow subtasks with a separate context.
  2. First component: Use a graceful fallback path. Second component: Delegate narrow subtasks with a separate context.
  3. First component: Use bounded memory with explicit provenance. Second component: Summarize long-running state with checkpoints.
  4. First component: Summarize long-running state with checkpoints. Second component: Use a graceful fallback path.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

The first proposal serves the different purpose to keep a customer service application operating when an expensive specialist agent cannot complete instead of the assigned first 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 each subagent can work in a bounded context and return a concise, verified artifact; their respective acceptance criteria are to preserve customer preferences across permitted sessions while distinguishing facts from assumptions and to protect a coordinator's window from huge specialist tool outputs.

C:

The first proposal fits its assigned role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions, while the second proposal serves the different purpose to continue a support investigation after many rounds of log inspection instead of the assigned second role because periodic compaction preserves decisions, open questions, and evidence references within the context budget; their respective acceptance criteria are to preserve customer preferences across permitted sessions while distinguishing facts from assumptions and to protect a coordinator's window from huge specialist tool outputs.

D:

The first proposal serves the different purpose to continue a support investigation after many rounds of log inspection instead of the assigned first role because periodic compaction preserves decisions, open questions, and evidence references within the context budget, while the second proposal serves the different purpose to keep a customer service application operating when an expensive specialist agent cannot complete instead of the assigned second role because a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; their respective acceptance criteria are to preserve customer preferences across permitted sessions while distinguishing facts from assumptions and to protect a coordinator's window from huge specialist tool outputs.

Question 125

The current design of a production API pipeline does not adequately ensure protected records are processed only in approved jurisdictions. Which improvement resolves the gap?

  1. Set an explicit data residency constraint
  2. Calculate expected traffic and concurrency
  3. Agree on output contracts with downstream systems
  4. Classify data sensitivity up front

Explanation

Correct Answer

A:

Documented residency requirements inform cloud placement, logging, storage, and vendor selection; this behavior directly supports the need to ensure protected records are processed only in approved jurisdictions. A statement about answer quality does not control geographic data handling.

Incorrect Answers

B:

This approach serves the separate need to provision an interactive application for peak seasonal traffic because workload assumptions drive rate-limit planning, queue capacity, and retry strategy; it does not establish the outcome to ensure protected records are processed only in approved jurisdictions, and average request volume alone hides burst behavior.

C:

Typed fields and required identifiers enable validators and consumers to reject malformed results; despite being useful when a service must deliver model-generated records to a strict financial reporting API, it is not a solution to ensure protected records are processed only in approved jurisdictions; a free-form explanatory paragraph may be legible but not machine-consumable.

D:

For the alternate objective to decide which customer fields must be redacted before model requests, data classification guides minimization, access controls, retention, and acceptable transfers; the feature here must ensure protected records are processed only in approved jurisdictions, and sanitizing only after a model has seen secret input is too late.

Question 126

Engineers are splitting a token economics service into two independently tested functions. Function A must control average spend while retaining quality on exceptional requests, while function B must compare two models where the cheaper call fails validation more often. Which plan is sound?

  1. First component: Route hard cases to a stronger fallback. Second component: Prefer a Sonnet-class model for balanced workloads.
  2. First component: Measure end-to-end latency, not just token speed. Second component: Balance quality against price per successful task.
  3. First component: Prefer a Sonnet-class model for balanced workloads. Second component: Measure end-to-end latency, not just token speed.
  4. First component: Route hard cases to a stronger fallback. Second component: Balance quality against price per successful task.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because a tiered policy starts with a cheaper path and escalates on measurable uncertainty or validation failure, while the second proposal fits its assigned role because retries, human review, and downstream error cost can outweigh nominal token-price savings; their respective acceptance criteria are to control average spend while retaining quality on exceptional requests and to compare two models where the cheaper call fails validation more often.

Incorrect Answers

A:

The first proposal fits its assigned role because a tiered policy starts with a cheaper path and escalates on measurable uncertainty or validation failure, while the second proposal serves the different purpose to serve a mixed coding and support assistant at moderate latency and cost instead of the assigned second role because the balanced tier often offers a practical quality-throughput compromise, subject to task-level testing; their respective acceptance criteria are to control average spend while retaining quality on exceptional requests and to compare two models where the cheaper call fails validation more often.

B:

The first proposal serves the different purpose to select the right model for an application with tool and network overhead instead of the assigned first role because total response time includes queuing, input processing, generation, and downstream integration, while the second proposal fits its assigned role because retries, human review, and downstream error cost can outweigh nominal token-price savings; their respective acceptance criteria are to control average spend while retaining quality on exceptional requests and to compare two models where the cheaper call fails validation more often.

C:

The first proposal serves the different purpose to serve a mixed coding and support assistant at moderate latency and cost instead of the assigned first role because the balanced tier often offers a practical quality-throughput compromise, subject to task-level testing, while the second proposal serves the different purpose to select the right model for an application with tool and network overhead instead of the assigned second role because total response time includes queuing, input processing, generation, and downstream integration; their respective acceptance criteria are to control average spend while retaining quality on exceptional requests and to compare two models where the cheaper call fails validation more often.

Question 127

The acceptance criteria for an agent extensibility change state that it must connect a desktop development tool to a trusted local server process. Which implementation aligns with that criterion?

  1. Expose an MCP tool for an external action
  2. Use stdio for a local MCP process
  3. Apply authorization inside the MCP server
  4. Validate MCP tool schemas and results

Explanation

Correct Answer

B:

Standard input and output transport is suitable for a client-managed local subprocess; this behavior directly supports the need to connect a desktop development tool to a trusted local server process. It is not a remotely addressable network service by itself.

Incorrect Answers

A:

This approach serves the separate need to let multiple compatible clients request a controlled shipment lookup because MCP tools advertise callable operations with named parameters and schemas across client integrations; it does not establish the outcome to connect a desktop development tool to a trusted local server process, and a resource intended only for reading context does not perform arbitrary commands.

C:

For the alternate objective 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 feature here must connect a desktop development tool to a trusted local server process, and tool discovery is not proof that a user may invoke a capability on all records.

D:

Contract tests check declared capabilities, argument shapes, and expected response content; this applies to the different goal to prevent a server update from returning incompatible payloads to clients, not the requirement to connect a desktop development tool to a trusted local server process; successful connection does not prove semantic correctness.

Question 128

An architecture review of a document processing product lists two distinct outcomes: the first subsystem must provision an interactive application for peak seasonal traffic, and a second subsystem must decide which customer fields must be redacted before model requests. Which pair delivers these outcomes?

  1. First component: Calculate expected traffic and concurrency. Second component: Classify data sensitivity up front.
  2. First component: Define input modalities and size bounds. Second component: Define failure and recovery objectives.
  3. First component: Calculate expected traffic and concurrency. Second component: Define input modalities and size bounds.
  4. First component: Define failure and recovery objectives. Second component: Classify data sensitivity up front.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because workload assumptions drive rate-limit planning, queue capacity, and retry strategy, while the second proposal fits its assigned role because data classification guides minimization, access controls, retention, and acceptable transfers; their respective acceptance criteria are to provision an interactive application for peak seasonal traffic and to decide which customer fields must be redacted before model requests.

Incorrect Answers

B:

The first proposal serves the different purpose to build an intake service that accepts scanned documents as well as typed text instead of the assigned first role because format, resolution, size, and throughput requirements determine preprocessing and model-call strategy, while the second proposal serves the different purpose to keep a regulated triage service usable during an upstream API outage instead of the assigned second role because availability, recovery time, and fallback behavior must be specified as measurable operational needs; their respective acceptance criteria are to provision an interactive application for peak seasonal traffic and to decide which customer fields must be redacted before model requests.

C:

The first proposal fits its assigned role because workload assumptions drive rate-limit planning, queue capacity, and retry strategy, while the second proposal serves the different purpose to build an intake service that accepts scanned documents as well as typed text instead of the assigned second role because format, resolution, size, and throughput requirements determine preprocessing and model-call strategy; their respective acceptance criteria are to provision an interactive application for peak seasonal traffic and to decide which customer fields must be redacted before model requests.

D:

The first proposal serves the different purpose to keep a regulated triage service usable during an upstream API outage instead of the assigned first role because availability, recovery time, and fallback behavior must be specified as measurable operational needs, while the second proposal fits its assigned role because data classification guides minimization, access controls, retention, and acceptable transfers; their respective acceptance criteria are to provision an interactive application for peak seasonal traffic and to decide which customer fields must be redacted before model requests.

Question 129

An architecture review of a credential management product lists two distinct outcomes: the first subsystem must inspect proposed scripts without granting them production host privileges, and a second subsystem must find vulnerabilities in a retrieval-augmented assistant before it accesses production tools. Which pair delivers these outcomes?

  1. First component: Enforce least-privilege tool permissions. Second component: Run adversarial prompt-injection tests.
  2. First component: Sandbox generated code execution. Second component: Run adversarial prompt-injection tests.
  3. First component: Rate-limit high-risk endpoints. Second component: Enforce least-privilege tool permissions.
  4. First component: Sandbox generated code execution. Second component: Rate-limit high-risk endpoints.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because resource, filesystem, and network isolation contain failures and malicious effects, while the second proposal fits its assigned role because purposeful hostile test cases probe whether the trust boundary holds under manipulated evidence; their respective acceptance criteria are to inspect proposed scripts without granting them production host privileges and to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools.

Incorrect Answers

A:

The first proposal serves the different purpose to let a support assistant read shipment status without issuing refunds instead of the assigned first role because restricted scopes and read-only interfaces limit impact if a tool request is manipulated, while the second proposal fits its assigned role because purposeful hostile test cases probe whether the trust boundary holds under manipulated evidence; their respective acceptance criteria are to inspect proposed scripts without granting them production host privileges and to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools.

C:

The first proposal serves the different purpose to reduce automated abuse of a model-backed export or search capability instead of the assigned first role because per-identity quotas and anomaly monitoring make bulk misuse harder, while the second proposal serves the different purpose to let a support assistant read shipment status without issuing refunds instead of the assigned second role because restricted scopes and read-only interfaces limit impact if a tool request is manipulated; their respective acceptance criteria are to inspect proposed scripts without granting them production host privileges and to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools.

D:

The first proposal fits its assigned role because resource, filesystem, and network isolation contain failures and malicious effects, while the second proposal serves the different purpose to reduce automated abuse of a model-backed export or search capability instead of the assigned second role because per-identity quotas and anomaly monitoring make bulk misuse harder; their respective acceptance criteria are to inspect proposed scripts without granting them production host privileges and to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools.

Question 130

An external system access review requires two independent, explicitly defined outcomes: the first workstream must enable a customer service agent to prepare but not autonomously approve account closures; a second must call a protected internal pricing API under the application's own credentials. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Combine tool access with human confirmation
  2. Choose a built-in provider tool
  3. Create a custom client-side tool
  4. Use system or repository instructions for stable behavior
  5. Use an autonomous agent for exploratory work

Explanation

Correct Answers

A:

Tools supply actionable capabilities while a separate approval step governs sensitive execution; this directly supports task 1 to enable a customer service agent to prepare but not autonomously approve account closures, not the separate task or tasks to call a protected internal pricing API under the application's own credentials; access to a function does not imply authority to invoke it without review.

C:

Local execution gives the developer direct control over authentication, validation, and side effects; this directly supports task 2 to call a protected internal pricing API under the application's own credentials, not the separate task or tasks to enable a customer service agent to prepare but not autonomously approve account closures; a hosted generic search feature cannot access private endpoints automatically.

Incorrect Answers

B:

Provider-managed execution can reduce implementation work when its scope matches the requirement; this implements the different outcome to use an already supported capability without hosting a duplicate custom service rather than the required tasks to call a protected internal pricing API under the application's own credentials and to enable a customer service agent to prepare but not autonomously approve account closures, and built-in tools may not expose a proprietary enterprise data source, so it is not a direct solution to any of the assigned workstreams.

D:

Instructions shape model behavior and task framing without executing external operations; this implements the different outcome to make a coding or API assistant follow organization-wide conventions rather than the required tasks to call a protected internal pricing API under the application's own credentials and to enable a customer service agent to prepare but not autonomously approve account closures, and descriptive rules do not replace programmatic validation or IAM, so it is not a direct solution to any of the assigned workstreams.

E:

Model-directed planning supports adaptive sequences when the next action is not known in advance; this implements the different outcome to perform open-ended troubleshooting where tool selection changes after each observation rather than the required tasks to call a protected internal pricing API under the application's own credentials and to enable a customer service agent to prepare but not autonomously approve account closures, and a rigid workflow struggles with unforeseen branches without extensive coding, so it is not a direct solution to any of the assigned workstreams.

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