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

Question 420

The acceptance criteria for an inference routing change state that it must reduce setup overhead when a service sends many short requests. Which implementation aligns with that criterion?

  1. Honor server rate-limit signals
  2. Send the correct API authentication header
  3. Use a queue for burst absorption
  4. Use connection pooling for repeated HTTP calls

Explanation

Correct Answer

D:

Reusable clients avoid unnecessary connection establishment under compatible networking conditions; this behavior directly supports the need to reduce setup overhead when a service sends many short requests. Creating a fresh client per request can increase latency and resource churn.

Incorrect Answers

A:

Throttling and backoff work with provider limits rather than assuming infinite request capacity; this applies to the different goal to prevent a background processor from overwhelming the upstream API during bursts, not the requirement to reduce setup overhead when a service sends many short requests; parallelism beyond quota can reduce successful throughput.

B:

When an application needs to avoid unauthenticated model requests from a backend worker, the API validates the provided credential before accepting a request; the current capability must instead reduce setup overhead when a service sends many short requests, while embedding a secret in a user prompt does not authenticate an HTTP call.

C:

Queueing decouples producers from consumer throughput and enables controlled retries; the supported outcome is to smooth sudden ingestion spikes before workers call a capacity-limited model API, whereas this scenario requires the ability to reduce setup overhead when a service sends many short requests; increasing frontend timeouts does not eliminate backend capacity limits.

Question 421

A document processing build contains an upstream function and a separate downstream function. The upstream work must keep a downstream parser from crashing when a request returns no usable text block; the downstream work must route uncertain medical-style recommendations to an authorized human instead of issuing final decisions. Which configuration pair covers both?

  1. First component: Handle empty and partial model responses. Second component: Design an explicit escalation path.
  2. First component: Handle empty and partial model responses. Second component: Add cancellation handling to streaming UI.
  3. First component: Keep user tasks in the user message. Second component: Design an explicit escalation path.
  4. First component: Add cancellation handling to streaming UI. Second component: Keep user tasks in the user message.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because content-aware response handling checks block types, stop reasons, and required values before proceeding, while the second proposal fits its assigned role because risk-based thresholds separate assistance from decisions reserved for accountable staff; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to route uncertain medical-style recommendations to an authorized human instead of issuing final decisions.

Incorrect Answers

B:

The first proposal fits its assigned role because content-aware response handling checks block types, stop reasons, and required values before proceeding, while the second proposal serves the different purpose to stop processing when a user cancels a long report and release resources cleanly instead of the assigned second role because cancellation signals should propagate through streams, queues, and workers where supported; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to route uncertain medical-style recommendations to an authorized human instead of issuing final decisions.

C:

The first proposal serves the different purpose to separate an end user's request from the developer's stable operating instructions instead of the assigned first role because explicit message roles distinguish requested work from higher-priority operational framing, while the second proposal fits its assigned role because risk-based thresholds separate assistance from decisions reserved for accountable staff; their respective acceptance criteria are to keep a downstream parser from crashing when a request returns no usable text block and to route uncertain medical-style recommendations to an authorized human instead of issuing final decisions.

D:

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

Question 422

A developer is reviewing alternatives for a latency optimization feature that must select the right model for an application with tool and network overhead. Which option is a defensible fit?

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

Explanation

Correct Answer

A:

Total response time includes queuing, input processing, generation, and downstream integration; this behavior directly supports the need to select the right model for an application with tool and network overhead. A high tokens-per-second figure alone can conceal slow first-token delivery.

Incorrect Answers

B:

Availability of context length, structured output, and modalities may depend on the selected model and version; the supported outcome is to avoid selecting a model that lacks a required document or tool feature, whereas this scenario requires the ability to select the right model for an application with tool and network overhead; family-level generalizations do not override specific compatibility documentation.

C:

This approach serves the separate need to serve a mixed coding and support assistant at moderate latency and cost because the balanced tier often offers a practical quality-throughput compromise, subject to task-level testing; it does not establish the outcome to select the right model for an application with tool and network overhead, and it should not be assumed to dominate every model on every benchmark.

D:

A tiered policy starts with a cheaper path and escalates on measurable uncertainty or validation failure; despite being useful when a service must control average spend while retaining quality on exceptional requests, it is not a solution to select the right model for an application with tool and network overhead; fixed use of the most costly model discards easy-case savings.

Question 423

A release plan for an engineering workstation platform has two acceptance checks: component one must make a specialised review procedure available as task-specific instructions and assets; component two must apply specialised rules only to a sensitive infrastructure folder. Which proposal passes both?

  1. First component: Create a reusable Skill. Second component: Use directory-scoped instructions.
  2. First component: Create a reusable Skill. Second component: Use headless invocation for automation.
  3. First component: Use headless invocation for automation. Second component: Run repository initialization to create project guidance.
  4. First component: Run repository initialization to create project guidance. Second component: Use directory-scoped instructions.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because a Skill packages a repeatable capability that Claude can load when relevant to the work, while the second proposal fits its assigned role because more local instruction files help scope guidance to the appropriate subtree; their respective acceptance criteria are to make a specialised review procedure available as task-specific instructions and assets and to apply specialised rules only to a sensitive infrastructure folder.

Incorrect Answers

B:

The first proposal fits its assigned role because a Skill packages a repeatable capability that Claude can load when relevant to the work, 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 make a specialised review procedure available as task-specific instructions and assets and to apply specialised rules only to a sensitive infrastructure folder.

C:

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 serves the different purpose to establish a discoverable set of build and test conventions for a new Claude Code workspace instead of the assigned second role because repository initialization can generate or prepare project instruction material that the team subsequently reviews; their respective acceptance criteria are to make a specialised review procedure available as task-specific instructions and assets and to apply specialised rules only to a sensitive infrastructure folder.

D:

The first proposal serves the different purpose to establish a discoverable set of build and test conventions for a new Claude Code workspace instead of the assigned first role because repository initialization can generate or prepare project instruction material that the team subsequently reviews, while the second proposal fits its assigned role because more local instruction files help scope guidance to the appropriate subtree; their respective acceptance criteria are to make a specialised review procedure available as task-specific instructions and assets and to apply specialised rules only to a sensitive infrastructure folder.

Question 424

An engineer extending an agent governance workflow has been asked to prevent a read-only support tool from modifying billing tables. Which choice addresses the request most precisely?

  1. Scope database credentials by tenant and operation
  2. Add an explicit export approval check
  3. Apply retention limits to diagnostic logs
  4. Validate tool arguments server-side

Explanation

Correct Answer

A:

Least-privilege identity limits the damage from a manipulated tool call; this behavior directly supports the need to prevent a read-only support tool from modifying billing tables. A broad administrator token bypasses application intent.

Incorrect Answers

B:

A separate authorization or human approval step can gate high-impact operations; this applies to the different goal to prevent unreviewed bulk downloads triggered by an agent's tool plan, not the requirement to prevent a read-only support tool from modifying billing tables; the model's confidence in its own plan does not grant export permission.

C:

When an application needs to reduce exposure of customer documents copied into application telemetry, data minimization and controlled retention reduce the duration and audience of sensitive log content; the current capability must instead prevent a read-only support tool from modifying billing tables, while an internal log is still a data store requiring access controls.

D:

Backend authorization checks must bind the requested operation to the caller's entitlements; the supported outcome is to block a generated database query that targets another tenant's records, whereas this scenario requires the ability to prevent a read-only support tool from modifying billing tables; well-formed arguments are not proof of permission.

Question 425

A developer is reviewing alternatives for an operations orchestration feature that must meet a requirement that proprietary repository contents remain within an approved execution environment. Which option is a defensible fit?

  1. Use PreToolUse gating for dangerous operations
  2. Preserve assistant tool-use content in conversation history
  3. Deploy agent workers close to controlled data sources
  4. Implement a custom Messages API tool loop
  5. Execute independent requested tools concurrently

Explanation

Correct Answer

C:

A self-hosted harness can enforce infrastructure, network, and retention controls for the surrounding tools; this behavior directly supports the need to meet a requirement that proprietary repository contents remain within an approved execution environment. Hosted orchestration does not automatically inherit a company's private-network policies.

Incorrect Answers

A:

A pre-execution hook can examine a proposed action and block it through a deterministic policy; this applies to the different goal to reject a shell command that targets protected deployment secrets before execution, not the requirement to meet a requirement that proprietary repository contents remain within an approved execution environment; post-execution logging cannot prevent a destructive command already run.

B:

When an application needs to maintain a valid transcript when the model requests multiple tools, the next request retains the assistant message containing tool_use blocks before providing their user-role tool_result blocks; the current capability must instead meet a requirement that proprietary repository contents remain within an approved execution environment, while dropping that assistant turn loses the linkage required for continuation.

D:

This approach serves the separate need to retain complete control over a small set of proprietary tool calls and their execution order because the application receives tool requests, validates inputs, executes authorized functions, and sends tool results back; it does not establish the outcome to meet a requirement that proprietary repository contents remain within an approved execution environment, and the Messages API does not automatically execute arbitrary client tools.

E:

Parallel execution is safe for independent operations while every result must still be matched to its call ID; despite being useful when a service must reduce turnaround when an agent asks for unrelated reads in the same response, it is not a solution to meet a requirement that proprietary repository contents remain within an approved execution environment; mutating tools with data dependencies should not be blindly parallelized.

Question 426

A design review identifies a missing capability in a model platform project: it must prevent request timestamps from invalidating a costly static prefix. Which change meets that goal?

  1. Set budget alerts and tenant caps
  2. Use model routing for simple versus hard cases
  3. Cache a stable shared prefix
  4. Keep volatile fields after reusable context

Explanation

Correct Answer

D:

Stable instruction and reference sections should precede changing per-request details for effective prefix reuse; this behavior directly supports the need to prevent request timestamps from invalidating a costly static prefix. Placing a changing value before the cache boundary undermines matching.

Incorrect Answers

A:

This approach serves the separate need to stop a single customer from consuming the entire API allowance during a runaway workflow because accounting plus enforced limits bounds exposure to unexpected traffic and agent loops; it does not establish the outcome to prevent request timestamps from invalidating a costly static prefix, and usage dashboards alone only report overspend after the fact.

B:

Conditional routing improves blended cost without discarding an escalation path; despite being useful when a service must spend high-capability tokens only when validation indicates complexity, it is not a solution to prevent request timestamps from invalidating a costly static prefix; blindly downgrading every call can increase retries and review expenses.

C:

For the alternate objective to reduce repeated processing of identical tool definitions and system instructions, prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match; the feature here must prevent request timestamps from invalidating a costly static prefix, and caching does not turn every changed prompt into an automatic hit.

Question 427

A design review identifies a missing capability in an integration quality project: it must keep a batch pipeline resilient when the upstream service briefly fails. Which change meets that goal?

  1. Diagnose a 5xx provider error
  2. Interpret max_tokens as a truncation cause
  3. Handle a 429 rate limit error
  4. Investigate a 403 authorization failure
  5. Investigate a 401 authentication failure

Explanation

Correct Answer

A:

Server-side failures may warrant bounded retries, jitter, and a fallback rather than request-shape changes; this behavior directly supports the need to keep a batch pipeline resilient when the upstream service briefly fails. Treating every provider outage as a malformed JSON prompt hides the real cause.

Incorrect Answers

B:

For the alternate objective to explain why a generated answer ends before a required final field, the stop reason indicates the generation budget was exhausted rather than the task being completed; the feature here must keep a batch pipeline resilient when the upstream service briefly fails, and a valid parse of the partial prefix does not make the report complete.

C:

A bounded retry policy and workload shaping address quota or rate throttling; this applies to the different goal to prevent a bursty job service from exceeding allowed request throughput, not the requirement to keep a batch pipeline resilient when the upstream service briefly fails; repeating the request immediately can intensify the limit.

D:

When an application needs to determine why a valid service identity is denied a protected capability, authorization failures concern permission or policy after identity is established; the current capability must instead keep a batch pipeline resilient when the upstream service briefly fails, while rotating an otherwise valid key will not necessarily grant missing access.

E:

Authentication errors require checking credential validity and configuration; the supported outcome is to restore an integration after an API key is revoked, whereas this scenario requires the ability to keep a batch pipeline resilient when the upstream service briefly fails; a larger output-token budget cannot authenticate the caller.

Question 428

A release plan for an external system access platform has two acceptance checks: component one must make one internal ticketing connector available to several agent clients; component two must make a coding or API assistant follow organization-wide conventions. Which proposal passes both?

  1. First component: Publish an MCP server for reusable integrations. Second component: Use system or repository instructions for stable behavior.
  2. First component: Use subagents for independent expertise. Second component: Package a Skill for reusable guidance.
  3. First component: Publish an MCP server for reusable integrations. Second component: Use subagents for independent expertise.
  4. First component: Package a Skill for reusable guidance. Second component: Use system or repository instructions for stable behavior.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because MCP standardizes tool and resource discovery across compatible applications, while the second proposal fits its assigned role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to make a coding or API assistant follow organization-wide conventions.

Incorrect Answers

B:

The first proposal serves the different purpose to delegate a security analysis while keeping the main coordinator's context concise instead of the assigned first role because specialist contexts reduce tool-output contamination and support focused parallel work, while the second proposal serves the different purpose to give a coding agent a consistent review playbook and supporting assets instead of the assigned second role because a Skill provides task procedures and resources that the agent can load when applicable; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to make a coding or API assistant follow organization-wide conventions.

C:

The first proposal fits its assigned role because MCP standardizes tool and resource discovery across compatible applications, while the second proposal serves the different purpose to delegate a security analysis while keeping the main coordinator's context concise instead of the assigned second role because specialist contexts reduce tool-output contamination and support focused parallel work; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to make a coding or API assistant follow organization-wide conventions.

D:

The first proposal serves the different purpose to give a coding agent a consistent review playbook and supporting assets instead of the assigned first role because a Skill provides task procedures and resources that the agent can load when applicable, while the second proposal fits its assigned role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to make one internal ticketing connector available to several agent clients and to make a coding or API assistant follow organization-wide conventions.

Question 429

A technical specification for a conversation design application assigns two jobs to separate modules: module A must save tokens when several retrieval chunks contain the same repeated policy section, and module B must stop stale log dumps from crowding out new evidence during an agent session. Which two-part solution is appropriate?

  1. First component: Refresh stale evidence before reuse. Second component: Prune obsolete tool outputs.
  2. First component: Deduplicate overlapping passages. Second component: Anchor summaries to source identifiers.
  3. First component: Anchor summaries to source identifiers. Second component: Refresh stale evidence before reuse.
  4. First component: Deduplicate overlapping passages. Second component: Prune obsolete tool outputs.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because overlap detection reduces redundant context without throwing away unique clauses, while the second proposal fits its assigned role because tool-result pruning removes redundant bulky observations after their findings are retained; their respective acceptance criteria are to save tokens when several retrieval chunks contain the same repeated policy section and to stop stale log dumps from crowding out new evidence during an agent session.

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 fits its assigned role because tool-result pruning removes redundant bulky observations after their findings are retained; their respective acceptance criteria are to save tokens when several retrieval chunks contain the same repeated policy section and to stop stale log dumps from crowding out new evidence during an agent session.

B:

The first proposal fits its assigned role because overlap detection reduces redundant context without throwing away unique clauses, 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 save tokens when several retrieval chunks contain the same repeated policy section and to stop stale log dumps from crowding out new evidence during an agent session.

C:

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 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 save tokens when several retrieval chunks contain the same repeated policy section and to stop stale log dumps from crowding out new evidence during an agent session.

Question 430

A design review identifies a missing capability in an inference routing project: it must smooth sudden ingestion spikes before workers call a capacity-limited model API. Which change meets that goal?

  1. Choose WebSockets for bidirectional realtime exchange
  2. Send the correct API authentication header
  3. Use a queue for burst absorption
  4. Send an API version header where required

Explanation

Correct Answer

C:

Queueing decouples producers from consumer throughput and enables controlled retries; this behavior directly supports the need to smooth sudden ingestion spikes before workers call a capacity-limited model API. Increasing frontend timeouts does not eliminate backend capacity limits.

Incorrect Answers

A:

This approach serves the separate need to implement an interactive collaboration channel requiring messages in both directions because persistent two-way channels fit interactive event exchange where the client also sends messages during a session; it does not establish the outcome to smooth sudden ingestion spikes before workers call a capacity-limited model API, and standard response streaming alone is not a general bidirectional messaging protocol.

B:

The API validates the provided credential before accepting a request; despite being useful when a service must avoid unauthenticated model requests from a backend worker, it is not a solution to smooth sudden ingestion spikes before workers call a capacity-limited model API; embedding a secret in a user prompt does not authenticate an HTTP call.

D:

Explicit protocol versioning makes the caller's expected API semantics unambiguous; this applies to the different goal to keep integration behavior aligned with a supported request contract, not the requirement to smooth sudden ingestion spikes before workers call a capacity-limited model API; relying on an arbitrary undocumented default is fragile.

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