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

Question 500

A developer is reviewing alternatives for a credential management feature that must restore a safe service state after a new guardrail configuration causes widespread errors. Which option is a defensible fit?

  1. Deploy content moderation and escalation
  2. Rate-limit high-risk endpoints
  3. Require verified identity for privileged actions
  4. Build a documented rollback and incident process

Explanation

Correct Answer

D:

Versioned release artifacts and response runbooks support containment and recovery; this behavior directly supports the need to restore a safe service state after a new guardrail configuration causes widespread errors. Improvised rollback during an outage increases operational risk.

Incorrect Answers

A:

When an application needs to route borderline high-risk requests to a review process instead of automatic publication, a defined moderation workflow handles uncertain or sensitive material according to business policy; the current capability must instead restore a safe service state after a new guardrail configuration causes widespread errors, while blocking every ambiguous input may be unnecessarily disruptive.

B:

Per-identity quotas and anomaly monitoring make bulk misuse harder; the supported outcome is to reduce automated abuse of a model-backed export or search capability, whereas this scenario requires the ability to restore a safe service state after a new guardrail configuration causes widespread errors; a single global throughput cap may still let one actor consume all capacity.

C:

This approach serves the separate need to stop an unauthenticated user from invoking a dangerous account-management tool because authentication establishes the caller before authorization policies consider requested permissions; it does not establish the outcome to restore a safe service state after a new guardrail configuration causes widespread errors, and asking the model to remember a user's name is not identity verification.

Question 501

An agent extensibility review asks the team to close two unrelated gaps without merging their execution paths. Service A must let Claude distinguish a read-only invoice lookup from an invoice update; service B must identify whether slow agent replies come from a payment gateway rather than the model. Which paired remediation works?

  1. First component: Map tool_use IDs to results. Second component: Capture tool latency and failure metrics.
  2. First component: Define narrow tool input schemas. Second component: Map tool_use IDs to results.
  3. First component: Write task-specific tool descriptions. Second component: Capture tool latency and failure metrics.
  4. First component: Write task-specific tool descriptions. Second component: Define narrow tool input schemas.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because clear capabilities and side effects guide tool selection without granting new authority, while the second proposal fits its assigned role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to identify whether slow agent replies come from a payment gateway rather than the model.

Incorrect Answers

A:

The first proposal serves the different purpose to support multiple simultaneous lookups without mixing their responses instead of the assigned first role because correlation IDs connect each observation to the exact invocation that requested it, while the second proposal fits its assigned role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to identify whether slow agent replies come from a payment gateway rather than the model.

B:

The first proposal serves the different purpose to prevent ambiguous generated arguments from reaching an inventory service instead of the assigned first role because typed parameter definitions constrain requests and enable strict validation before execution, while the second proposal serves the different purpose to support multiple simultaneous lookups without mixing their responses instead of the assigned second role because correlation IDs connect each observation to the exact invocation that requested it; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to identify whether slow agent replies come from a payment gateway rather than the model.

D:

The first proposal fits its assigned role because clear capabilities and side effects guide tool selection without granting new authority, while the second proposal serves the different purpose to prevent ambiguous generated arguments from reaching an inventory service instead of the assigned second role because typed parameter definitions constrain requests and enable strict validation before execution; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to identify whether slow agent replies come from a payment gateway rather than the model.

Question 502

A production-readiness check for a backend integration component requires the service to reproduce a working SDK installation across staging and production. Which approach passes this check?

  1. Use asynchronous I/O for concurrent requests
  2. Refactor duplicated request orchestration
  3. Separate integration tests from unit tests
  4. Pin dependencies with lockfiles

Explanation

Correct Answer

D:

Locked versions and hashes constrain drift between build environments; this behavior directly supports the need to reproduce a working SDK installation across staging and production. Unbounded package updates can introduce new behavior during a routine rebuild.

Incorrect Answers

A:

When an application needs to serve independent API calls without blocking a worker thread for each network wait, async execution overlaps I/O-bound tasks while maintaining control over concurrency; the current capability must instead reproduce a working SDK installation across staging and production, while it does not by itself make CPU-bound model processing faster.

B:

A shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes; the supported outcome is to maintain multiple Claude entry points without drifting retry and logging behavior, whereas this scenario requires the ability to reproduce a working SDK installation across staging and production; copying the same networking code into every route magnifies defects.

C:

This approach serves the separate need to verify that a real staging tool and its API contract work together because integration tests exercise boundaries and serialization that isolated mocks may miss; it does not establish the outcome to reproduce a working SDK installation across staging and production, and unit tests can pass while authentication or payload mapping is broken.

Question 503

A retrieval pipeline review requires two independent, explicitly defined outcomes: the first workstream must avoid using the entire context budget on retrieved input before generating a response; a second must let an assistant continue a long incident investigation without losing decisions. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Prioritize high-signal retrieved passages
  2. Compact completed task history
  3. Refresh stale evidence before reuse
  4. Reserve space for the model's output
  5. Separate long-term memory from active scratchpad

Explanation

Correct Answers

B:

A structured summary preserves established facts, pending work, and unresolved assumptions in fewer tokens; this directly supports task 2 to let an assistant continue a long incident investigation without losing decisions, not the separate task or tasks to avoid using the entire context budget on retrieved input before generating a response; raw truncation may remove the reason an earlier decision was made.

D:

Input assembly must leave room for the requested completion and any needed reasoning; this directly supports task 1 to avoid using the entire context budget on retrieved input before generating a response, not the separate task or tasks to let an assistant continue a long incident investigation without losing decisions; a technically accepted long prompt can still prevent a useful-length answer.

Incorrect Answers

A:

Ranking by relevance and authority places the most useful evidence ahead of incidental matches; this implements the different outcome to fit a large knowledge base into the context of a customer answer rather than the required tasks to let an assistant continue a long incident investigation without losing decisions and to avoid using the entire context budget on retrieved input before generating a response, and dumping every document into the prompt can obscure the actual answer, so it is not a direct solution to any of the assigned workstreams.

C:

Freshness checks determine whether a saved passage remains authoritative for a dynamic fact; this implements the different outcome to avoid answering a pricing question from last month's retrieved cache rather than the required tasks to let an assistant continue a long incident investigation without losing decisions and to avoid using the entire context budget on retrieved input before generating a response, and high semantic similarity says nothing about timeliness, so it is not a direct solution to any of the assigned workstreams.

E:

Explicit storage and freshness rules govern what is retained and when it is reintroduced; this implements the different outcome to prevent outdated user preferences from being treated as current task instructions rather than the required tasks to let an assistant continue a long incident investigation without losing decisions and to avoid using the entire context budget on retrieved input before generating a response, and an unbounded persistent transcript can accumulate contradictory assumptions, so it is not a direct solution to any of the assigned workstreams.

Question 504

A production-readiness check for an engineering productivity component requires the service to let an agent run generated scripts without exposing production host files. Which approach passes this check?

  1. Use PreToolUse gating for dangerous operations
  2. Preserve assistant tool-use content in conversation history
  3. Choose isolated sandbox execution for untrusted code
  4. Keep user-specific state out of a shared agent process
  5. Add idempotency keys to side-effecting operations

Explanation

Correct Answer

C:

A restricted execution environment limits filesystem, network, and resource privileges; this behavior directly supports the need to let an agent run generated scripts without exposing production host files. Running code in the main application process expands the blast radius of a bad tool call.

Incorrect Answers

A:

A pre-execution hook can examine a proposed action and block it through a deterministic policy; the supported outcome is to reject a shell command that targets protected deployment secrets before execution, whereas this scenario requires the ability to let an agent run generated scripts without exposing production host files; post-execution logging cannot prevent a destructive command already run.

B:

This approach serves the separate need to maintain a valid transcript when the model requests multiple tools because the next request retains the assistant message containing tool_use blocks before providing their user-role tool_result blocks; it does not establish the outcome to let an agent run generated scripts without exposing production host files, and dropping that assistant turn loses the linkage required for continuation.

D:

For the alternate objective to serve many tenants without mixing their tool outputs or prior messages, per-request identity and session boundaries prevent cross-tenant context leakage; the feature here must let an agent run generated scripts without exposing production host files, and shared conversation histories can inadvertently expose unrelated customers' data.

E:

Application-generated operation identifiers allow the downstream service to recognize a repeated request; this applies to the different goal to avoid charging a customer twice after a worker retries a timed-out payment action, not the requirement to let an agent run generated scripts without exposing production host files; model-level instructions cannot guarantee exactly-once execution after a partial failure.

Question 505

Two features of an agent extensibility system are under review. One feature must let Claude distinguish a read-only invoice lookup from an invoice update; the other must stop a directory lookup function from also gaining unrestricted database write access. Which plan matches the respective needs?

  1. First component: Write task-specific tool descriptions. Second component: Restrict tool network credentials.
  2. First component: Write task-specific tool descriptions. Second component: Capture tool latency and failure metrics.
  3. First component: Capture tool latency and failure metrics. Second component: Return structured tool errors.
  4. First component: Return structured tool errors. Second component: Restrict tool network credentials.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because clear capabilities and side effects guide tool selection without granting new authority, while the second proposal fits its assigned role because minimal capabilities reduce risk when generated arguments or retrieved text are hostile; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to stop a directory lookup function from also gaining unrestricted database write access.

Incorrect Answers

B:

The first proposal fits its assigned role because clear capabilities and side effects guide tool selection without granting new authority, while the second proposal serves the different purpose to identify whether slow agent replies come from a payment gateway rather than the model instead of the assigned second role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to stop a directory lookup function from also gaining unrestricted database write access.

C:

The first proposal serves the different purpose to identify whether slow agent replies come from a payment gateway rather than the model instead of the assigned first role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies, 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 let Claude distinguish a read-only invoice lookup from an invoice update and to stop a directory lookup function from also gaining unrestricted database write access.

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 fits its assigned role because minimal capabilities reduce risk when generated arguments or retrieved text are hostile; their respective acceptance criteria are to let Claude distinguish a read-only invoice lookup from an invoice update and to stop a directory lookup function from also gaining unrestricted database write access.

Question 506

A design review identifies a missing capability in an application security project: it must inspect proposed scripts without granting them production host privileges. Which change meets that goal?

  1. Build a documented rollback and incident process
  2. Deploy content moderation and escalation
  3. Enforce least-privilege tool permissions
  4. Run adversarial prompt-injection tests
  5. Sandbox generated code execution

Explanation

Correct Answer

E:

Resource, filesystem, and network isolation contain failures and malicious effects; this behavior directly supports the need to inspect proposed scripts without granting them production host privileges. Relying on model intent does not constrain a subprocess.

Incorrect Answers

A:

Versioned release artifacts and response runbooks support containment and recovery; despite being useful when a service must restore a safe service state after a new guardrail configuration causes widespread errors, it is not a solution to inspect proposed scripts without granting them production host privileges; improvised rollback during an outage increases operational risk.

B:

For the alternate objective to route borderline high-risk requests to a review process instead of automatic publication, a defined moderation workflow handles uncertain or sensitive material according to business policy; the feature here must inspect proposed scripts without granting them production host privileges, and blocking every ambiguous input may be unnecessarily disruptive.

C:

Restricted scopes and read-only interfaces limit impact if a tool request is manipulated; this applies to the different goal to let a support assistant read shipment status without issuing refunds, not the requirement to inspect proposed scripts without granting them production host privileges; role language in the prompt cannot prevent an overprivileged API token from writing.

D:

When an application needs to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools, purposeful hostile test cases probe whether the trust boundary holds under manipulated evidence; the current capability must instead inspect proposed scripts without granting them production host privileges, while ordinary happy-path tests rarely exercise attacker instructions.

Question 507

An inference routing solution has parallel requirements with separate owners. Workstream one must shorten latency and spend on tasks that need only basic categorization; workstream two must classify a familiar support message where labels and criteria are already clear. Which combination meets both?

  1. First component: Use low-temperature generation for repeatable extraction. Second component: Use contrasting few-shot examples.
  2. First component: Reduce reasoning effort on trivial routing. Second component: Apply zero-shot instructions for a straightforward task.
  3. First component: Reduce reasoning effort on trivial routing. Second component: Use low-temperature generation for repeatable extraction.
  4. First component: Use contrasting few-shot examples. Second component: Apply zero-shot instructions for a straightforward task.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because lower effort can suit predictable work where deeper reasoning adds little measurable quality, while the second proposal fits its assigned role because direct instructions can be sufficient when the task is simple and well specified; their respective acceptance criteria are to shorten latency and spend on tasks that need only basic categorization and to classify a familiar support message where labels and criteria are already clear.

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 distinguish borderline policy labels with examples of both allowed and disallowed cases instead of the assigned second role because multiple representative cases help define a decision boundary and reduce ambiguity; their respective acceptance criteria are to shorten latency and spend on tasks that need only basic categorization and to classify a familiar support message where labels and criteria are already clear.

C:

The first proposal fits its assigned role because lower effort can suit predictable work where deeper reasoning adds little measurable quality, 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 shorten latency and spend on tasks that need only basic categorization and to classify a familiar support message where labels and criteria are already clear.

D:

The first proposal serves the different purpose to distinguish borderline policy labels with examples of both allowed and disallowed cases instead of the assigned first role because multiple representative cases help define a decision boundary and reduce ambiguity, while the second proposal fits its assigned role because direct instructions can be sufficient when the task is simple and well specified; their respective acceptance criteria are to shorten latency and spend on tasks that need only basic categorization and to classify a familiar support message where labels and criteria are already clear.

Question 508

A technical specification for a backend integration application assigns two jobs to separate modules: module A must exercise an agent's database tool without touching live customer records, and module B must catch schema and policy failures after a model or tool update. Which two-part solution is appropriate?

  1. First component: Separate development, staging, and production environments. Second component: Assign an owner to every integration.
  2. First component: Perform a threat review before go-live. Second component: Implement automated regression tests.
  3. First component: Assign an owner to every integration. Second component: Perform a threat review before go-live.
  4. First component: Separate development, staging, and production environments. Second component: Implement automated regression tests.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because environment boundaries keep credentials, data, and writes isolated during testing, while the second proposal fits its assigned role because repeatable cases compare changes against documented acceptance criteria; their respective acceptance criteria are to exercise an agent's database tool without touching live customer records and to catch schema and policy failures after a model or tool update.

Incorrect Answers

A:

The first proposal fits its assigned role because environment boundaries keep credentials, data, and writes isolated during testing, while the second proposal serves the different purpose to prevent abandoned connectors from retaining access after an application is transferred instead of the assigned second role because ownership enables rotation, monitoring, change approval, and retirement decisions; their respective acceptance criteria are to exercise an agent's database tool without touching live customer records and to catch schema and policy failures after a model or tool update.

B:

The first proposal serves the different purpose to uncover prompt-injection paths through retrieved webpages and connected tools instead of the assigned first role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss, while the second proposal fits its assigned role because repeatable cases compare changes against documented acceptance criteria; their respective acceptance criteria are to exercise an agent's database tool without touching live customer records and to catch schema and policy failures after a model or tool update.

C:

The first proposal serves the different purpose to prevent abandoned connectors from retaining access after an application is transferred instead of the assigned first role because ownership enables rotation, monitoring, change approval, and retirement decisions, while the second proposal serves the different purpose to uncover prompt-injection paths through retrieved webpages and connected tools instead of the assigned second role because reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss; their respective acceptance criteria are to exercise an agent's database tool without touching live customer records and to catch schema and policy failures after a model or tool update.

Question 509

A developer is reviewing alternatives for a backend integration feature that must reject forged callbacks from an external asynchronous job service. Which option is a defensible fit?

  1. Use feature flags for risky behavior changes
  2. Refactor duplicated request orchestration
  3. Use exponential backoff with jitter
  4. Keep secrets out of source control
  5. Validate webhook signatures

Explanation

Correct Answer

E:

Cryptographic verification checks the sender and payload integrity before processing the event; this behavior directly supports the need to reject forged callbacks from an external asynchronous job service. Accepting any POST with the expected JSON fields permits spoofing.

Incorrect Answers

A:

Runtime controls can segment rollout and permit quick disabling without a code rebuild; this applies to the different goal to activate a new tool execution path for only internal testers, not the requirement to reject forged callbacks from an external asynchronous job service; hard-coded unconditional activation exposes every tenant simultaneously.

B:

When an application needs to maintain multiple Claude entry points without drifting retry and logging behavior, a shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes; the current capability must instead reject forged callbacks from an external asynchronous job service, while copying the same networking code into every route magnifies defects.

C:

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 reject forged callbacks from an external asynchronous job service; immediate identical retries can extend an overload event.

D:

This approach serves the separate need to prevent API credentials from being exposed through shared repository history because secret stores or environment injection keep production tokens out of committed code; it does not establish the outcome to reject forged callbacks from an external asynchronous job service, and deleting a secret from the latest commit may not remove it from earlier revisions.

Question 510

Two separate tickets in a language-model integration backlog require different controls. One needs to call the Messages endpoint from a language without a mature provider SDK; the other needs to prevent a background processor from overwhelming the upstream API during bursts. Which implementation pair is correct?

  1. First component: Use the Messages count_tokens capability. Second component: Send the correct API authentication header.
  2. First component: Send the correct API authentication header. Second component: Honor server rate-limit signals.
  3. First component: Use direct HTTP REST integration for unsupported runtimes. Second component: Use the Messages count_tokens capability.
  4. First component: Use direct HTTP REST integration for unsupported runtimes. Second component: Honor server rate-limit signals.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because a standards-based HTTP client can send JSON requests with the correct headers and decode responses, while the second proposal fits its assigned role because throttling and backoff work with provider limits rather than assuming infinite request capacity; their respective acceptance criteria are to call the Messages endpoint from a language without a mature provider SDK and to prevent a background processor from overwhelming the upstream API during bursts.

Incorrect Answers

A:

The first proposal serves the different purpose to estimate model-token input demand before launching a large processing job instead of the assigned first role because token counting helps check input budgets before generation and cost planning, while the second proposal serves the different purpose to avoid unauthenticated model requests from a backend worker instead of the assigned second role because the API validates the provided credential before accepting a request; their respective acceptance criteria are to call the Messages endpoint from a language without a mature provider SDK and to prevent a background processor from overwhelming the upstream API during bursts.

B:

The first proposal serves the different purpose to avoid unauthenticated model requests from a backend worker instead of the assigned first role because the API validates the provided credential before accepting a request, while the second proposal fits its assigned role because throttling and backoff work with provider limits rather than assuming infinite request capacity; their respective acceptance criteria are to call the Messages endpoint from a language without a mature provider SDK and to prevent a background processor from overwhelming the upstream API during bursts.

C:

The first proposal fits its assigned role because a standards-based HTTP client can send JSON requests with the correct headers and decode responses, while the second proposal serves the different purpose to estimate model-token input demand before launching a large processing job instead of the assigned second role because token counting helps check input budgets before generation and cost planning; their respective acceptance criteria are to call the Messages endpoint from a language without a mature provider SDK and to prevent a background processor from overwhelming the upstream API during bursts.

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