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

Question 600

After pilot feedback, an agent platform group needs two independent improvements. The first is to branch between remediation and escalation based on the result of a security scan; the second is to coordinate multiple specialists working on interdependent evidence without losing changes. Which engineering proposal handles both?

  1. First component: Use a graph with conditional edges. Second component: Use bounded memory with explicit provenance.
  2. First component: Use bounded memory with explicit provenance. Second component: Prefer a finite state machine for regulated steps.
  3. First component: Use a graph with conditional edges. Second component: Adopt a blackboard of shared task state.
  4. First component: Prefer a finite state machine for regulated steps. Second component: Adopt a blackboard of shared task state.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal fits its assigned role because a controlled shared workspace holds versioned observations and ownership metadata for collaborators; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

Incorrect Answers

A:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned second role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

B:

The first proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned first role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions, while the second proposal serves the different purpose to enforce approval, execution, and confirmation order in a compliance workflow instead of the assigned second role because explicit states and transitions control who may advance a case independently of generated language; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

D:

The first proposal serves the different purpose to enforce approval, execution, and confirmation order in a compliance workflow instead of the assigned first role because explicit states and transitions control who may advance a case independently of generated language, while the second proposal fits its assigned role because a controlled shared workspace holds versioned observations and ownership metadata for collaborators; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

Question 601

The owner of a model platform integration wants to choose between releases using an actual organization's error and latency measurements. Which proposal provides the required mechanism?

  1. Check modality and feature support
  2. Prefer a Sonnet-class model for balanced workloads
  3. Run task-specific model evaluations
  4. Route hard cases to a stronger fallback
  5. Measure end-to-end latency, not just token speed

Explanation

Correct Answer

C:

Representative tests expose differences hidden by generic capability labels; this behavior directly supports the need to choose between releases using an actual organization's error and latency measurements. Marketing tier names cannot replace measured fit for purpose.

Incorrect Answers

A:

Availability of context length, structured output, and modalities may depend on the selected model and version; despite being useful when a service must avoid selecting a model that lacks a required document or tool feature, it is not a solution to choose between releases using an actual organization's error and latency measurements; family-level generalizations do not override specific compatibility documentation.

B:

For the alternate objective to serve a mixed coding and support assistant at moderate latency and cost, the balanced tier often offers a practical quality-throughput compromise, subject to task-level testing; the feature here must choose between releases using an actual organization's error and latency measurements, and it should not be assumed to dominate every model on every benchmark.

D:

When an application needs to control average spend while retaining quality on exceptional requests, a tiered policy starts with a cheaper path and escalates on measurable uncertainty or validation failure; the current capability must instead choose between releases using an actual organization's error and latency measurements, while fixed use of the most costly model discards easy-case savings.

E:

Total response time includes queuing, input processing, generation, and downstream integration; the supported outcome is to select the right model for an application with tool and network overhead, whereas this scenario requires the ability to choose between releases using an actual organization's error and latency measurements; a high tokens-per-second figure alone can conceal slow first-token delivery.

Question 602

A design review identifies a missing capability in a customer platform project: it must analyze a photographed shipping label with the supported multimodal Messages input. Which change meets that goal?

  1. Supply a tool definition with input schema
  2. Handle message_stop and final usage events
  3. Include an image content block
  4. Call the Messages API with explicit model and max_tokens

Explanation

Correct Answer

C:

Image inputs are supplied as typed content with appropriate source data or references; this behavior directly supports the need to analyze a photographed shipping label with the supported multimodal Messages input. Describing a local image pathname in ordinary text does not transmit its pixels.

Incorrect Answers

A:

A declared tool name, description, and schema constrain the interface offered to the model; this applies to the different goal to let Claude request a read-only inventory lookup with typed arguments, not the requirement to analyze a photographed shipping label with the supported multimodal Messages input; listing a function in a prompt does not create a callable tool contract.

B:

When an application needs to record complete streamed output and token usage accurately, the final stream events signal completion and deliver accumulated metadata beyond individual text fragments; the current capability must instead analyze a photographed shipping label with the supported multimodal Messages input, while stopping after the first content delta truncates responses.

D:

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 analyze a photographed shipping label with the supported multimodal Messages input, and the API is not a stateful chat session unless prior turns are supplied.

Question 603

The owner of an inference routing integration wants to classify many short messages where low latency and unit cost dominate. Which proposal provides the required mechanism?

  1. Run task-specific model evaluations
  2. Prefer a Haiku-class model for lightweight routing
  3. Measure end-to-end latency, not just token speed
  4. Route hard cases to a stronger fallback

Explanation

Correct Answer

B:

The lighter tier suits inexpensive, high-throughput tasks with modest reasoning demand; this behavior directly supports the need to classify many short messages where low latency and unit cost dominate. Complex planning may need escalation after an evaluated failure.

Incorrect Answers

A:

Representative tests expose differences hidden by generic capability labels; the supported outcome is to choose between releases using an actual organization's error and latency measurements, whereas this scenario requires the ability to classify many short messages where low latency and unit cost dominate; marketing tier names cannot replace measured fit for purpose.

C:

Total response time includes queuing, input processing, generation, and downstream integration; despite being useful when a service must select the right model for an application with tool and network overhead, it is not a solution to classify many short messages where low latency and unit cost dominate; a high tokens-per-second figure alone can conceal slow first-token delivery.

D:

For the alternate objective to control average spend while retaining quality on exceptional requests, a tiered policy starts with a cheaper path and escalates on measurable uncertainty or validation failure; the feature here must classify many short messages where low latency and unit cost dominate, and fixed use of the most costly model discards easy-case savings.

Question 604

During a retrieval pipeline rollout, two different failure paths need remediation. The first component must avoid using the entire context budget on retrieved input before generating a response; separately, the second must fit a large knowledge base into the context of a customer answer. Which changes should be adopted?

  1. First component: Refresh stale evidence before reuse. Second component: Anchor summaries to source identifiers.
  2. First component: Anchor summaries to source identifiers. Second component: Prioritize high-signal retrieved passages.
  3. First component: Reserve space for the model's output. Second component: Refresh stale evidence before reuse.
  4. First component: Reserve space for the model's output. Second component: Prioritize high-signal retrieved passages.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because input assembly must leave room for the requested completion and any needed reasoning, while the second proposal fits its assigned role because ranking by relevance and authority places the most useful evidence ahead of incidental matches; their respective acceptance criteria are to avoid using the entire context budget on retrieved input before generating a response and to fit a large knowledge base into the context of a customer answer.

Incorrect Answers

A:

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 enable a reviewer to reconstruct evidence after context has been compacted instead of the assigned second role because stable document IDs and passage references preserve provenance beyond the shortened working memory; their respective acceptance criteria are to avoid using the entire context budget on retrieved input before generating a response and to fit a large knowledge base into the context of a customer answer.

B:

The first proposal serves the different purpose to enable a reviewer to reconstruct evidence after context has been compacted instead of the assigned first role because stable document IDs and passage references preserve provenance beyond the shortened working memory, while the second proposal fits its assigned role because ranking by relevance and authority places the most useful evidence ahead of incidental matches; their respective acceptance criteria are to avoid using the entire context budget on retrieved input before generating a response and to fit a large knowledge base into the context of a customer answer.

C:

The first proposal fits its assigned role because input assembly must leave room for the requested completion and any needed reasoning, 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 avoid using the entire context budget on retrieved input before generating a response and to fit a large knowledge base into the context of a customer answer.

Question 605

An architecture review of a data pipeline product lists two distinct outcomes: the first subsystem must prevent API credentials from being exposed through shared repository history, and a second subsystem must reject forged callbacks from an external asynchronous job service. Which pair delivers these outcomes?

  1. First component: Keep secrets out of source control. Second component: Avoid retrying non-idempotent writes blindly.
  2. First component: Avoid retrying non-idempotent writes blindly. Second component: Validate JSON before deserialization.
  3. First component: Validate JSON before deserialization. Second component: Validate webhook signatures.
  4. First component: Keep secrets out of source control. Second component: Validate webhook signatures.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because secret stores or environment injection keep production tokens out of committed code, while the second proposal fits its assigned role because cryptographic verification checks the sender and payload integrity before processing the event; their respective acceptance criteria are to prevent API credentials from being exposed through shared repository history and to reject forged callbacks from an external asynchronous job service.

Incorrect Answers

A:

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

B:

The first proposal serves the different purpose to keep an interrupted invoice-creation request from generating duplicate invoices instead of the assigned first role because retries of side-effecting actions need idempotency keys or transaction reconciliation, while the second proposal serves the different purpose to reject a malformed tool argument payload before calling a payroll service instead of the assigned second role because a parser and schema validator catch missing types and invalid syntax before side effects; their respective acceptance criteria are to prevent API credentials from being exposed through shared repository history and to reject forged callbacks from an external asynchronous job service.

C:

The first proposal serves the different purpose to reject a malformed tool argument payload before calling a payroll service instead of the assigned first role because a parser and schema validator catch missing types and invalid syntax before side effects, while the second proposal fits its assigned role because cryptographic verification checks the sender and payload integrity before processing the event; their respective acceptance criteria are to prevent API credentials from being exposed through shared repository history and to reject forged callbacks from an external asynchronous job service.

Question 606

The current design of a data pipeline pipeline does not adequately preserve a customer's follow-up reference to an earlier case number. Which improvement resolves the gap?

  1. Supply previous turns on a new API request
  2. Process tool_use responses in the application
  3. Use supported document or PDF input
  4. Call the Messages API with explicit model and max_tokens

Explanation

Correct Answer

A:

Stateless requests need relevant history passed back in the messages sequence; this behavior directly supports the need to preserve a customer's follow-up reference to an earlier case number. A client connection alone does not give the model memory of previous calls.

Incorrect Answers

B:

Client tools execute in application code; the model emits structured requests but does not invoke external functions itself; the supported outcome is to actually retrieve a customer's order status requested by Claude, whereas this scenario requires the ability to preserve a customer's follow-up reference to an earlier case number; displaying the tool request as the final answer never performs the lookup.

C:

This approach serves the separate need to extract claims from a document while retaining its visual layout because document-aware input lets a capable model consider page content and graphics when supported; it does not establish the outcome to preserve a customer's follow-up reference to an earlier case number, and pasting only extracted text can discard useful visual context.

D:

A message request identifies the target model, a message list, and an output-token ceiling; despite being useful when a service must return an answer to a short user request through a backend service, it is not a solution to preserve a customer's follow-up reference to an earlier case number; the API is not a stateful chat session unless prior turns are supplied.

Question 607

A release plan for an operations orchestration platform has two acceptance checks: component one must branch between remediation and escalation based on the result of a security scan; component two must enforce approval, execution, and confirmation order in a compliance workflow. Which proposal passes both?

  1. First component: Use retrieval before generation. Second component: Use bounded memory with explicit provenance.
  2. First component: Use a graph with conditional edges. Second component: Prefer a finite state machine for regulated steps.
  3. First component: Use bounded memory with explicit provenance. Second component: Prefer a finite state machine for regulated steps.
  4. First component: Use a graph with conditional edges. Second component: Use retrieval before generation.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal fits its assigned role because explicit states and transitions control who may advance a case independently of generated language; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to enforce approval, execution, and confirmation order in a compliance workflow.

Incorrect Answers

A:

The first proposal serves the different purpose to answer questions from changing internal documentation with traceable source excerpts instead of the assigned first role because retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current, while the second proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned second role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to enforce approval, execution, and confirmation order in a compliance workflow.

C:

The first proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned first role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions, while the second proposal fits its assigned role because explicit states and transitions control who may advance a case independently of generated language; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to enforce approval, execution, and confirmation order in a compliance workflow.

D:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal serves the different purpose to answer questions from changing internal documentation with traceable source excerpts instead of the assigned second role because retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to enforce approval, execution, and confirmation order in a compliance workflow.

Question 608

A design review identifies a missing capability in a customer platform project: it must keep a regulated triage service usable during an upstream API outage. Which change meets that goal?

  1. Calculate expected traffic and concurrency
  2. Set an explicit data residency constraint
  3. Record nonfunctional latency targets
  4. Define failure and recovery objectives

Explanation

Correct Answer

D:

Availability, recovery time, and fallback behavior must be specified as measurable operational needs; this behavior directly supports the need to keep a regulated triage service usable during an upstream API outage. A happy-path prototype misses behavior under dependency failures.

Incorrect Answers

A:

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 keep a regulated triage service usable during an upstream API outage, and average request volume alone hides burst behavior.

B:

Documented residency requirements inform cloud placement, logging, storage, and vendor selection; despite being useful when a service must ensure protected records are processed only in approved jurisdictions, it is not a solution to keep a regulated triage service usable during an upstream API outage; a statement about answer quality does not control geographic data handling.

C:

For the alternate objective to decide between streaming and offline processing for a time-sensitive support assistant, a measurable response-time objective constrains interaction design and infrastructure choices; the feature here must keep a regulated triage service usable during an upstream API outage, and functional prompts alone cannot establish acceptable performance.

Question 609

Two features of a document processing system are under review. One feature must avoid assuming a Claude Code repository setting automatically affects a direct Messages API call; the other must ensure an API assistant consistently uses a defined support role across requests. Which plan matches the respective needs?

  1. First component: Test interface-specific instruction behavior. Second component: Place durable behavior instructions in the system parameter.
  2. First component: Use bounded retrieval results. Second component: Place durable behavior instructions in the system parameter.
  3. First component: Create one session per user conversation. Second component: Use bounded retrieval results.
  4. First component: Test interface-specific instruction behavior. Second component: Create one session per user conversation.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because different Claude surfaces have different configuration and context mechanisms; an integration must supply its own instructions, while the second proposal fits its assigned role because system-level guidance supplies application-wide instruction context, separate from each user's task content; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to ensure an API assistant consistently uses a defined support role across requests.

Incorrect Answers

B:

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 system-level guidance supplies application-wide instruction context, separate from each user's task content; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to ensure an API assistant consistently uses a defined support role across requests.

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 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 avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to ensure an API assistant consistently uses a defined support role across requests.

D:

The first proposal fits its assigned role because different Claude surfaces have different configuration and context mechanisms; an integration must supply its own instructions, while the second proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned second role because session scoping ensures history and tool results belong to the correct principal; their respective acceptance criteria are to avoid assuming a Claude Code repository setting automatically affects a direct Messages API call and to ensure an API assistant consistently uses a defined support role across requests.

Question 610

The current design of an inference routing pipeline does not adequately avoid treating a tool call or thinking block as user-visible answer text. Which improvement resolves the gap?

  1. Use the official SDK for standard requests
  2. Parse responses by content block type
  3. Use connection pooling for repeated HTTP calls
  4. Use JSON-safe types in request bodies

Explanation

Correct Answer

B:

Structured outputs can contain different block kinds that need type-aware handling; this behavior directly supports the need to avoid treating a tool call or thinking block as user-visible answer text. Concatenating arbitrary block payloads risks displaying internal control data.

Incorrect Answers

A:

When an application needs to simplify authentication, serialization, and response typing in a Python service, maintained client libraries wrap the HTTP API and expose structured response objects; the current capability must instead avoid treating a tool call or thinking block as user-visible answer text, while SDK convenience does not eliminate the need for correct retry and error handling.

C:

This approach serves the separate need to reduce setup overhead when a service sends many short requests because reusable clients avoid unnecessary connection establishment under compatible networking conditions; it does not establish the outcome to avoid treating a tool call or thinking block as user-visible answer text, and creating a fresh client per request can increase latency and resource churn.

D:

Structured request encoding enforces objects, arrays, strings, booleans, and numeric representations; despite being useful when a service must avoid rejecting tool schemas because serialized values are invalid, it is not a solution to avoid treating a tool call or thinking block as user-visible answer text; python object repr strings are not valid JSON contracts.

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