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

Question 340

The acceptance criteria for a token economics change state that it must forecast cost for an application that sends long documents but returns brief classifications. Which implementation aligns with that criterion?

  1. Estimate output length before scaling
  2. Track input and output usage separately
  3. Set maximum step counts for agents
  4. Use batch pricing where deadline permits
  5. Set budget alerts and tenant caps

Explanation

Correct Answer

B:

Metering by token category reveals the main cost driver and supports realistic forecasts; this behavior directly supports the need to forecast cost for an application that sends long documents but returns brief classifications. Counting only request totals hides prompt-size variability.

Incorrect Answers

A:

Cost models should include the generated token volume and task-specific variance; this applies to the different goal to avoid underbudgeting a report-writing feature whose completions are much longer than inputs, not the requirement to forecast cost for an application that sends long documents but returns brief classifications; input-only estimates miss potentially dominant completion expense.

C:

A bound on iterations prevents repeated generation and calls from growing without limit; the supported outcome is to contain cumulative token and tool cost across a recursive research session, whereas this scenario requires the ability to forecast cost for an application that sends long documents but returns brief classifications; a per-message output cap alone does not control total multi-step spend.

D:

This approach serves the separate need to lower spend for large scheduled classification jobs that do not need immediate responses because asynchronous batch processing can offer a cost-effective throughput path under supported terms; it does not establish the outcome to forecast cost for an application that sends long documents but returns brief classifications, and a night job should not be optimized with live streaming unless its users need it.

E:

Accounting plus enforced limits bounds exposure to unexpected traffic and agent loops; despite being useful when a service must stop a single customer from consuming the entire API allowance during a runaway workflow, it is not a solution to forecast cost for an application that sends long documents but returns brief classifications; usage dashboards alone only report overspend after the fact.

Question 341

A prompt engineering build contains an upstream function and a separate downstream function. The upstream work must let an assistant continue a long incident investigation without losing decisions; the downstream work must enable a reviewer to reconstruct evidence after context has been compacted. Which configuration pair covers both?

  1. First component: Compact completed task history. Second component: Refresh stale evidence before reuse.
  2. First component: Separate long-term memory from active scratchpad. Second component: Refresh stale evidence before reuse.
  3. First component: Compact completed task history. Second component: Anchor summaries to source identifiers.
  4. First component: Preserve instruction and evidence boundaries. Second component: Anchor summaries to source identifiers.
  5. First component: Refresh stale evidence before reuse. Second component: Preserve instruction and evidence boundaries.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because a structured summary preserves established facts, pending work, and unresolved assumptions in fewer tokens, while the second proposal fits its assigned role because stable document IDs and passage references preserve provenance beyond the shortened working memory; their respective acceptance criteria are to let an assistant continue a long incident investigation without losing decisions and to enable a reviewer to reconstruct evidence after context has been compacted.

Incorrect Answers

A:

The first proposal fits its assigned role because a structured summary preserves established facts, pending work, and unresolved assumptions in fewer tokens, while the second proposal serves the different purpose to avoid answering a pricing question from last month's retrieved cache instead of the assigned second role because freshness checks determine whether a saved passage remains authoritative for a dynamic fact; their respective acceptance criteria are to let an assistant continue a long incident investigation without losing decisions and to enable a reviewer to reconstruct evidence after context has been compacted.

B:

The first proposal serves the different purpose to prevent outdated user preferences from being treated as current task instructions instead of the assigned first role because explicit storage and freshness rules govern what is retained and when it is reintroduced, while the second proposal serves the different purpose to avoid answering a pricing question from last month's retrieved cache instead of the assigned second role because freshness checks determine whether a saved passage remains authoritative for a dynamic fact; their respective acceptance criteria are to let an assistant continue a long incident investigation without losing decisions and to enable a reviewer to reconstruct evidence after context has been compacted.

D:

The first proposal serves the different purpose to keep an embedded webpage instruction from becoming higher-priority application policy instead of the assigned first role because context assembly must label external text as data and avoid granting it authority over tool use, while the second proposal fits its assigned role because stable document IDs and passage references preserve provenance beyond the shortened working memory; their respective acceptance criteria are to let an assistant continue a long incident investigation without losing decisions and to enable a reviewer to reconstruct evidence after context has been compacted.

E:

The first proposal serves the different purpose to avoid answering a pricing question from last month's retrieved cache instead of the assigned first role because freshness checks determine whether a saved passage remains authoritative for a dynamic fact, while the second proposal serves the different purpose to keep an embedded webpage instruction from becoming higher-priority application policy instead of the assigned second role because context assembly must label external text as data and avoid granting it authority over tool use; their respective acceptance criteria are to let an assistant continue a long incident investigation without losing decisions and to enable a reviewer to reconstruct evidence after context has been compacted.

Question 342

A release plan for a Claude application platform has two acceptance checks: component one must maintain multiple Claude entry points without drifting retry and logging behavior; component two must recover from transient 429 responses without synchronized retry storms. Which proposal passes both?

  1. First component: Enforce concurrency limits. Second component: Use exponential backoff with jitter.
  2. First component: Refactor duplicated request orchestration. Second component: Use exponential backoff with jitter.
  3. First component: Pin dependencies with lockfiles. Second component: Enforce concurrency limits.
  4. First component: Refactor duplicated request orchestration. Second component: Pin dependencies with lockfiles.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because a shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes, 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 maintain multiple Claude entry points without drifting retry and logging behavior and to recover from transient 429 responses without synchronized retry storms.

Incorrect Answers

A:

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 fits its assigned role because increasing randomized delays reduce contention and respect service throttling signals; their respective acceptance criteria are to maintain multiple Claude entry points without drifting retry and logging behavior and to recover from transient 429 responses without synchronized retry storms.

C:

The first proposal serves the different purpose to reproduce a working SDK installation across staging and production instead of the assigned first role because locked versions and hashes constrain drift between build environments, 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 maintain multiple Claude entry points without drifting retry and logging behavior and to recover from transient 429 responses without synchronized retry storms.

D:

The first proposal fits its assigned role because a shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes, while the second proposal serves the different purpose to reproduce a working SDK installation across staging and production instead of the assigned second role because locked versions and hashes constrain drift between build environments; their respective acceptance criteria are to maintain multiple Claude entry points without drifting retry and logging behavior and to recover from transient 429 responses without synchronized retry storms.

Question 343

Two separate tickets in an engineering workstation backlog require different controls. One needs to share coding conventions with every collaborator entering the same repository; the other needs to provide a consistent shortcut for a common repository maintenance task. Which implementation pair is correct?

  1. First component: Use headless invocation for automation. Second component: Define a custom slash command workflow.
  2. First component: Connect an MCP server to Claude Code. Second component: Use headless invocation for automation.
  3. First component: Use a project-level CLAUDE.md file. Second component: Connect an MCP server to Claude Code.
  4. First component: Use a project-level CLAUDE.md file. Second component: Define a custom slash command workflow.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because a checked-in memory file supplies persistent project context across relevant coding sessions, while the second proposal fits its assigned role because command-based workflows supply repeatable user-invoked instructions and arguments; their respective acceptance criteria are to share coding conventions with every collaborator entering the same repository and to provide a consistent shortcut for a common repository maintenance task.

Incorrect Answers

A:

The first proposal serves the different purpose to run Claude Code inside a CI job and capture its output without interactive prompts instead of the assigned first role because noninteractive execution lets scripts integrate agent work into existing pipelines with controlled formats, while the second proposal fits its assigned role because command-based workflows supply repeatable user-invoked instructions and arguments; their respective acceptance criteria are to share coding conventions with every collaborator entering the same repository and to provide a consistent shortcut for a common repository maintenance task.

B:

The first proposal serves the different purpose to expose approved project-specific actions without copying credentials into prompts instead of the assigned first role because an MCP integration declares external capabilities and their transport while access remains controlled by the server, while the second proposal serves the different purpose to run Claude Code inside a CI job and capture its output without interactive prompts instead of the assigned second role because noninteractive execution lets scripts integrate agent work into existing pipelines with controlled formats; their respective acceptance criteria are to share coding conventions with every collaborator entering the same repository and to provide a consistent shortcut for a common repository maintenance task.

C:

The first proposal fits its assigned role because a checked-in memory file supplies persistent project context across relevant coding sessions, while the second proposal serves the different purpose to expose approved project-specific actions without copying credentials into prompts instead of the assigned second role because an MCP integration declares external capabilities and their transport while access remains controlled by the server; their respective acceptance criteria are to share coding conventions with every collaborator entering the same repository and to provide a consistent shortcut for a common repository maintenance task.

Question 344

A design review identifies a missing capability in a customer platform project: it must prevent a supposedly read-only status lookup from changing a server-side record. Which change meets that goal?

  1. Use feature flags for risky behavior changes
  2. Use exponential backoff with jitter
  3. Use explicit HTTP method semantics
  4. Apply dependency injection for external clients

Explanation

Correct Answer

C:

GET should retrieve resources while state changes use appropriate mutation methods and authorization checks; this behavior directly supports the need to prevent a supposedly read-only status lookup from changing a server-side record. Putting write behavior behind a read endpoint undermines predictable retry and caching semantics.

Incorrect Answers

A:

When an application needs to activate a new tool execution path for only internal testers, runtime controls can segment rollout and permit quick disabling without a code rebuild; the current capability must instead prevent a supposedly read-only status lookup from changing a server-side record, while hard-coded unconditional activation exposes every tenant simultaneously.

B:

Increasing randomized delays reduce contention and respect service throttling signals; the supported outcome is to recover from transient 429 responses without synchronized retry storms, whereas this scenario requires the ability to prevent a supposedly read-only status lookup from changing a server-side record; immediate identical retries can extend an overload event.

D:

Injected interfaces allow deterministic stubs and reduce coupling to vendors; despite being useful when a service must test application logic without issuing real model calls or payments, it is not a solution to prevent a supposedly read-only status lookup from changing a server-side record; hard-coded global clients make behavior harder to isolate and simulate.

Question 345

During acceptance testing for an MCP interoperability service, one requirement is to use an already supported capability without hosting a duplicate custom service. What should the developer implement?

  1. Use system or repository instructions for stable behavior
  2. Use subagents for independent expertise
  3. Create a custom client-side tool
  4. Choose a built-in provider tool
  5. Use hooks for enforceable safety checks

Explanation

Correct Answer

D:

Provider-managed execution can reduce implementation work when its scope matches the requirement; this behavior directly supports the need to use an already supported capability without hosting a duplicate custom service. Built-in tools may not expose a proprietary enterprise data source.

Incorrect Answers

A:

Instructions shape model behavior and task framing without executing external operations; this applies to the different goal to make a coding or API assistant follow organization-wide conventions, not the requirement to use an already supported capability without hosting a duplicate custom service; descriptive rules do not replace programmatic validation or IAM.

B:

When an application needs to delegate a security analysis while keeping the main coordinator's context concise, specialist contexts reduce tool-output contamination and support focused parallel work; the current capability must instead use an already supported capability without hosting a duplicate custom service, while a reusable Skill alone does not create an independent worker with separate state.

C:

Local execution gives the developer direct control over authentication, validation, and side effects; the supported outcome is to call a protected internal pricing API under the application's own credentials, whereas this scenario requires the ability to use an already supported capability without hosting a duplicate custom service; a hosted generic search feature cannot access private endpoints automatically.

E:

Runtime interception can apply deterministic policies to proposed actions; despite being useful when a service must deny destructive filesystem operations before a coding agent executes them, it is not a solution to use an already supported capability without hosting a duplicate custom service; a skill that asks for caution does not guarantee prevention.

Question 346

After pilot feedback, a token economics group needs two independent improvements. The first is to allocate more deliberate computation to a hard multi-step planning problem; the second is to explain why a plausible answer can still contain an unsupported factual claim. Which engineering proposal handles both?

  1. First component: Use low-temperature generation for repeatable extraction. Second component: Reduce reasoning effort on trivial routing.
  2. First component: Reduce reasoning effort on trivial routing. Second component: Recognize next-token generation.
  3. First component: Enable supported extended or adaptive reasoning. Second component: Recognize next-token generation.
  4. First component: Enable supported extended or adaptive reasoning. Second component: Use low-temperature generation for repeatable extraction.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because thinking controls can improve complex reasoning at the expense of latency or token usage depending on the model, while the second proposal fits its assigned role because the model predicts likely continuations conditioned on context rather than querying an authoritative truth database by default; their respective acceptance criteria are to allocate more deliberate computation to a hard multi-step planning problem and to explain why a plausible answer can still contain an unsupported factual claim.

Incorrect Answers

A:

The first proposal serves the different purpose to reduce variation when a service maps documents into consistent categories instead of the assigned first role because lower randomness often improves consistency for narrow, constrained tasks, while the second proposal serves the different purpose to shorten latency and spend on tasks that need only basic categorization instead of the assigned second role because lower effort can suit predictable work where deeper reasoning adds little measurable quality; their respective acceptance criteria are to allocate more deliberate computation to a hard multi-step planning problem and to explain why a plausible answer can still contain an unsupported factual claim.

B:

The first proposal serves the different purpose to shorten latency and spend on tasks that need only basic categorization instead of the assigned first role because lower effort can suit predictable work where deeper reasoning adds little measurable quality, while the second proposal fits its assigned role because the model predicts likely continuations conditioned on context rather than querying an authoritative truth database by default; their respective acceptance criteria are to allocate more deliberate computation to a hard multi-step planning problem and to explain why a plausible answer can still contain an unsupported factual claim.

D:

The first proposal fits its assigned role because thinking controls can improve complex reasoning at the expense of latency or token usage depending on the model, while the second proposal serves the different purpose to reduce variation when a service maps documents into consistent categories instead of the assigned second role because lower randomness often improves consistency for narrow, constrained tasks; their respective acceptance criteria are to allocate more deliberate computation to a hard multi-step planning problem and to explain why a plausible answer can still contain an unsupported factual claim.

Question 347

An MCP interoperability review requires two independent, explicitly defined outcomes: the first workstream must let an assistant recover from a missing order without inventing its details; a second must stop a directory lookup function from also gaining unrestricted database write access. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Define narrow tool input schemas
  2. Return structured tool errors
  3. Restrict tool network credentials
  4. Map tool_use IDs to results
  5. Capture tool latency and failure metrics

Explanation

Correct Answers

B:

Machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up; this directly supports task 1 to let an assistant recover from a missing order without inventing its details, not the separate task or tasks to stop a directory lookup function from also gaining unrestricted database write access; pretending failure is an empty successful record hides operational meaning.

C:

Minimal capabilities reduce risk when generated arguments or retrieved text are hostile; this directly supports task 2 to stop a directory lookup function from also gaining unrestricted database write access, not the separate task or tasks to let an assistant recover from a missing order without inventing its details; better prompt wording does not remove excess infrastructure permissions.

Incorrect Answers

A:

Typed parameter definitions constrain requests and enable strict validation before execution; this implements the different outcome to prevent ambiguous generated arguments from reaching an inventory service rather than the required tasks to let an assistant recover from a missing order without inventing its details and to stop a directory lookup function from also gaining unrestricted database write access, and a prose-only command description cannot validate required field types, so it is not a direct solution to any of the assigned workstreams.

D:

Correlation IDs connect each observation to the exact invocation that requested it; this implements the different outcome to support multiple simultaneous lookups without mixing their responses rather than the required tasks to let an assistant recover from a missing order without inventing its details and to stop a directory lookup function from also gaining unrestricted database write access, and pairing results by arrival order is unsafe under concurrency, so it is not a direct solution to any of the assigned workstreams.

E:

Per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; this implements the different outcome to identify whether slow agent replies come from a payment gateway rather than the model rather than the required tasks to let an assistant recover from a missing order without inventing its details and to stop a directory lookup function from also gaining unrestricted database write access, and aggregate response time alone cannot identify the responsible connector, so it is not a direct solution to any of the assigned workstreams.

Question 348

Two separate tickets in an MCP interoperability backlog require different controls. One needs to serve approved tools to multiple distributed client environments; the other needs to verify that tools and resources are discoverable before integrating an agent. Which implementation pair is correct?

  1. First component: Expose an MCP tool for an external action. Second component: Test protocol behavior with a compliant inspector.
  2. First component: Expose an MCP resource for reference content. Second component: Expose an MCP tool for an external action.
  3. First component: Use a remote HTTP transport for shared MCP access. Second component: Test protocol behavior with a compliant inspector.
  4. First component: Use a remote HTTP transport for shared MCP access. Second component: Expose an MCP resource for reference content.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because an HTTP-based endpoint supports remotely hosted servers with authentication and network controls, while the second proposal fits its assigned role because a protocol test client exposes handshake, capability, and schema problems independently of model behavior; their respective acceptance criteria are to serve approved tools to multiple distributed client environments and to verify that tools and resources are discoverable before integrating an agent.

Incorrect Answers

A:

The first proposal serves the different purpose to let multiple compatible clients request a controlled shipment lookup instead of the assigned first role because MCP tools advertise callable operations with named parameters and schemas across client integrations, while the second proposal fits its assigned role because a protocol test client exposes handshake, capability, and schema problems independently of model behavior; their respective acceptance criteria are to serve approved tools to multiple distributed client environments and to verify that tools and resources are discoverable before integrating an agent.

B:

The first proposal serves the different purpose to make a versioned product catalog available for read-oriented context retrieval instead of the assigned first role because resources provide identifiable data that clients can fetch for model context, while the second proposal serves the different purpose to let multiple compatible clients request a controlled shipment lookup instead of the assigned second role because MCP tools advertise callable operations with named parameters and schemas across client integrations; their respective acceptance criteria are to serve approved tools to multiple distributed client environments and to verify that tools and resources are discoverable before integrating an agent.

D:

The first proposal fits its assigned role because an HTTP-based endpoint supports remotely hosted servers with authentication and network controls, while the second proposal serves the different purpose to make a versioned product catalog available for read-oriented context retrieval instead of the assigned second role because resources provide identifiable data that clients can fetch for model context; their respective acceptance criteria are to serve approved tools to multiple distributed client environments and to verify that tools and resources are discoverable before integrating an agent.

Question 349

A production API team owns two independent components. The first must prevent a new user from inheriting another user's document excerpts; the second must separate an end user's request from the developer's stable operating instructions. Which paired plan fulfills both?

  1. First component: Handle empty and partial model responses. Second component: Return user-friendly error states.
  2. First component: Limit retained context to authorized history. Second component: Keep user tasks in the user message.
  3. First component: Create one session per user conversation. Second component: Handle empty and partial model responses.
  4. First component: Limit retained context to authorized history. Second component: Handle empty and partial model responses.
  5. First component: Return user-friendly error states. Second component: Keep user tasks in the user message.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because context assembly must apply access checks before adding prior turns or retrieved evidence, 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 new user from inheriting another user's document excerpts 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 keep a downstream parser from crashing when a request returns no usable text block instead of the assigned first 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 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 prevent a new user from inheriting another user's document excerpts and to separate an end user's request from the developer's stable operating instructions.

C:

The first proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned first role because session scoping ensures history and tool results belong to the correct principal, while the second proposal serves the different purpose to keep a downstream parser from crashing when a request returns no usable text block instead of the assigned second role because content-aware response handling checks block types, stop reasons, and required values before proceeding; their respective acceptance criteria are to prevent a new user from inheriting another user's document excerpts and to separate an end user's request from the developer's stable operating instructions.

D:

The first proposal fits its assigned role because context assembly must apply access checks before adding prior turns or retrieved evidence, while the second proposal serves the different purpose to keep a downstream parser from crashing when a request returns no usable text block instead of the assigned second role because content-aware response handling checks block types, stop reasons, and required values before proceeding; their respective acceptance criteria are to prevent a new user from inheriting another user's document excerpts and to separate an end user's request from the developer's stable operating instructions.

E:

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 explicit message roles distinguish requested work from higher-priority operational framing; their respective acceptance criteria are to prevent a new user from inheriting another user's document excerpts and to separate an end user's request from the developer's stable operating instructions.

Question 350

After pilot feedback, an external system access group needs two independent improvements. The first is to avoid creating duplicate tickets after a tool call times out; the second is to support multiple simultaneous lookups without mixing their responses. Which engineering proposal handles both?

  1. First component: Use idempotency for retried mutations. Second component: Map tool_use IDs to results.
  2. First component: Write task-specific tool descriptions. Second component: Map tool_use IDs to results.
  3. First component: Use idempotency for retried mutations. Second component: Return structured tool errors.
  4. First component: Return structured tool errors. Second component: Write task-specific tool descriptions.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because stable operation identifiers let downstream systems detect repeated submissions, while the second proposal fits its assigned role because correlation IDs connect each observation to the exact invocation that requested it; their respective acceptance criteria are to avoid creating duplicate tickets after a tool call times out and to support multiple simultaneous lookups without mixing their responses.

Incorrect Answers

B:

The first proposal serves the different purpose to let Claude distinguish a read-only invoice lookup from an invoice update instead of the assigned first role because clear capabilities and side effects guide tool selection without granting new authority, while the second proposal fits its assigned role because correlation IDs connect each observation to the exact invocation that requested it; their respective acceptance criteria are to avoid creating duplicate tickets after a tool call times out and to support multiple simultaneous lookups without mixing their responses.

C:

The first proposal fits its assigned role because stable operation identifiers let downstream systems detect repeated submissions, while the second proposal serves the different purpose to let an assistant recover from a missing order without inventing its details instead of the assigned second role because machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up; their respective acceptance criteria are to avoid creating duplicate tickets after a tool call times out and to support multiple simultaneous lookups without mixing their responses.

D:

The first proposal serves the different purpose to let an assistant recover from a missing order without inventing its details instead of the assigned first role because machine-readable failures distinguish not-found, permission denied, and transient errors for appropriate follow-up, while the second proposal serves the different purpose to let Claude distinguish a read-only invoice lookup from an invoice update instead of the assigned second role because clear capabilities and side effects guide tool selection without granting new authority; their respective acceptance criteria are to avoid creating duplicate tickets after a tool call times out and to support multiple simultaneous lookups without mixing their responses.

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