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

Question 400

A technical lead requests a solution that can cut off an exposed token discovered in CI logs within a credential management project. Which design should be chosen?

  1. Rotate a compromised API key promptly
  2. Use short-lived scoped credentials where supported
  3. Load keys from a managed secret service
  4. Authorize by requested resource and action

Explanation

Correct Answer

A:

Revocation plus replacement ends use of the leaked credential and requires checking for misuse; this behavior directly supports the need to cut off an exposed token discovered in CI logs. Merely deleting a log message leaves the old token valid.

Incorrect Answers

B:

Expiring identity grants reduce the time and permissions available to an attacker; the supported outcome is to limit the impact of a temporary worker credential being stolen, whereas this scenario requires the ability to cut off an exposed token discovered in CI logs; permanent shared administrator keys expand blast radius.

C:

This approach serves the separate need to avoid committing provider credentials inside a shared repository because secrets managers support controlled retrieval, rotation, and access logs; it does not establish the outcome to cut off an exposed token discovered in CI logs, and obscuring a literal string in source is not adequate key protection.

D:

Authorization checks must evaluate scope for each operation, not only whether a login exists; despite being useful when a service must deny access to a different customer's records even when the caller is authenticated, it is not a solution to cut off an exposed token discovered in CI logs; successful authentication is not equivalent to unrestricted data access.

Question 401

A retrieval pipeline group is preparing a production change intended to avoid using the entire context budget on retrieved input before generating a response. Which technique matches that intent?

  1. Preserve instruction and evidence boundaries
  2. Prioritize high-signal retrieved passages
  3. Anchor summaries to source identifiers
  4. Reserve space for the model's output

Explanation

Correct Answer

D:

Input assembly must leave room for the requested completion and any needed reasoning; this behavior directly supports the need to avoid using the entire context budget on retrieved input before generating a response. A technically accepted long prompt can still prevent a useful-length answer.

Incorrect Answers

A:

This approach serves the separate need to keep an embedded webpage instruction from becoming higher-priority application policy because context assembly must label external text as data and avoid granting it authority over tool use; it does not establish the outcome to avoid using the entire context budget on retrieved input before generating a response, and quotation formatting alone does not enforce sandboxing or authorization.

B:

Ranking by relevance and authority places the most useful evidence ahead of incidental matches; despite being useful when a service must fit a large knowledge base into the context of a customer answer, it is not a solution to avoid using the entire context budget on retrieved input before generating a response; dumping every document into the prompt can obscure the actual answer.

C:

For the alternate objective to enable a reviewer to reconstruct evidence after context has been compacted, stable document IDs and passage references preserve provenance beyond the shortened working memory; the feature here must avoid using the entire context budget on retrieved input before generating a response, and a bare compressed claim cannot show which source established it.

Question 402

A prompt engineering review requires two independent, explicitly defined outcomes: the first workstream must distinguish near-duplicate support intents that a broad rule routinely confuses; a second must obtain named fields in a consistent response layout for subsequent processing. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Use a stepwise decomposition
  2. Use few-shot boundary cases
  3. Specify output format in the prompt
  4. Separate system policy from user content
  5. Specify the handling of missing information

Explanation

Correct Answers

B:

Examples illustrating each side of a decision boundary communicate nuanced classification criteria; this directly supports task 1 to distinguish near-duplicate support intents that a broad rule routinely confuses, not the separate task or tasks to obtain named fields in a consistent response layout for subsequent processing; many unrelated demonstrations can make the rule harder to infer.

C:

Explicit field descriptions guide generation toward the consumer's expected structure; this directly supports task 2 to obtain named fields in a consistent response layout for subsequent processing, not the separate task or tasks to distinguish near-duplicate support intents that a broad rule routinely confuses; formatting guidance still requires machine validation at the boundary.

Incorrect Answers

A:

Breaking the work into verifiable stages lets the application check intermediate artifacts; this implements the different outcome to solve a complex migration comparison that requires several distinct checks rather than the required tasks to obtain named fields in a consistent response layout for subsequent processing and to distinguish near-duplicate support intents that a broad rule routinely confuses, and simply increasing prompt length can make dependencies less clear, so it is not a direct solution to any of the assigned workstreams.

D:

Stable higher-priority instructions should be represented in the designated instruction channel; this implements the different outcome to prevent a customer message from overriding the application's escalation rules rather than the required tasks to obtain named fields in a consistent response layout for subsequent processing and to distinguish near-duplicate support intents that a broad rule routinely confuses, and user text is the task data, not a privileged configuration surface, so it is not a direct solution to any of the assigned workstreams.

E:

An explicit unknown or null rule makes uncertainty visible in the requested output; this implements the different outcome to avoid invented contract dates when the uploaded document lacks them rather than the required tasks to obtain named fields in a consistent response layout for subsequent processing and to distinguish near-duplicate support intents that a broad rule routinely confuses, and a strict field list is not permission to fabricate absent values, so it is not a direct solution to any of the assigned workstreams.

Question 403

During acceptance testing for a data pipeline service, one requirement is to compute discounts through verified business code rather than generated arithmetic alone. What should the developer implement?

  1. Separate model reasoning from authoritative calculations
  2. Return user-friendly error states
  3. Limit retained context to authorized history
  4. Build a typed output envelope
  5. Place durable behavior instructions in the system parameter

Explanation

Correct Answer

A:

Deterministic services can enforce exact formulas and rounding before the model explains the result; this behavior directly supports the need to compute discounts through verified business code rather than generated arithmetic alone. A plausible model narrative is not a reliable financial ledger.

Incorrect Answers

B:

For the alternate objective to explain service limits or tool outages without leaking stack traces or secrets, structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs; the feature here must compute discounts through verified business code rather than generated arithmetic alone, and returning a raw exception can expose internal infrastructure details.

C:

Context assembly must apply access checks before adding prior turns or retrieved evidence; this applies to the different goal to prevent a new user from inheriting another user's document excerpts, not the requirement to compute discounts through verified business code rather than generated arithmetic alone; prompt-level instructions to respect privacy cannot repair a cross-tenant retrieval bug.

D:

When an application needs to send extracted contract fields into a database that rejects unexpected shapes, an explicit schema with required fields, types, and allowed values makes integration errors detectable; the current capability must instead compute discounts through verified business code rather than generated arithmetic alone, while free-form natural language is difficult to validate automatically.

E:

System-level guidance supplies application-wide instruction context, separate from each user's task content; the supported outcome is to ensure an API assistant consistently uses a defined support role across requests, whereas this scenario requires the ability to compute discounts through verified business code rather than generated arithmetic alone; a string placed in retrieved documents has no authority to redefine the application policy.

Question 404

Engineers are splitting an agent extensibility service into two independently tested functions. Function A must let an assistant recover from a missing order without inventing its details, while function B must let Claude distinguish a read-only invoice lookup from an invoice update. Which plan is sound?

  1. First component: Return structured tool errors. Second component: Write task-specific tool descriptions.
  2. First component: Define narrow tool input schemas. Second component: Write task-specific tool descriptions.
  3. First component: Return structured tool errors. Second component: Map tool_use IDs to results.
  4. First component: Map tool_use IDs to results. Second component: Define narrow tool input schemas.

Explanation

Correct Answer

A:

The first proposal fits its assigned 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 clear capabilities and side effects guide tool selection without granting new authority; their respective acceptance criteria are to let an assistant recover from a missing order without inventing its details and to let Claude distinguish a read-only invoice lookup from an invoice update.

Incorrect Answers

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 fits its assigned role because clear capabilities and side effects guide tool selection without granting new authority; their respective acceptance criteria are to let an assistant recover from a missing order without inventing its details and to let Claude distinguish a read-only invoice lookup from an invoice update.

C:

The first proposal fits its assigned 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 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 an assistant recover from a missing order without inventing its details and to let Claude distinguish a read-only invoice lookup from an invoice update.

D:

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 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 an assistant recover from a missing order without inventing its details and to let Claude distinguish a read-only invoice lookup from an invoice update.

Question 405

Engineers are splitting a latency optimization service into two independently tested functions. Function A must avoid rejecting tool schemas because serialized values are invalid, while function B must reduce setup overhead when a service sends many short requests. Which plan is sound?

  1. First component: Use the official SDK for standard requests. Second component: Use connection pooling for repeated HTTP calls.
  2. First component: Use JSON-safe types in request bodies. Second component: Use connection pooling for repeated HTTP calls.
  3. First component: Use a queue for burst absorption. Second component: Use the official SDK for standard requests.
  4. First component: Use JSON-safe types in request bodies. Second component: Use a queue for burst absorption.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations, while the second proposal fits its assigned role because reusable clients avoid unnecessary connection establishment under compatible networking conditions; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to reduce setup overhead when a service sends many short requests.

Incorrect Answers

A:

The first proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned first role because maintained client libraries wrap the HTTP API and expose structured response objects, while the second proposal fits its assigned role because reusable clients avoid unnecessary connection establishment under compatible networking conditions; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to reduce setup overhead when a service sends many short requests.

C:

The first proposal serves the different purpose to smooth sudden ingestion spikes before workers call a capacity-limited model API instead of the assigned first role because queueing decouples producers from consumer throughput and enables controlled retries, while the second proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned second role because maintained client libraries wrap the HTTP API and expose structured response objects; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to reduce setup overhead when a service sends many short requests.

D:

The first proposal fits its assigned role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations, while the second proposal serves the different purpose to smooth sudden ingestion spikes before workers call a capacity-limited model API instead of the assigned second role because queueing decouples producers from consumer throughput and enables controlled retries; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to reduce setup overhead when a service sends many short requests.

Question 406

The owner of a coding automation integration wants to provide a consistent shortcut for a common repository maintenance task. Which proposal provides the required mechanism?

  1. Connect an MCP server to Claude Code
  2. Define a custom slash command workflow
  3. Use a project-level CLAUDE.md file
  4. Use a pre-execution hook for deterministic checks

Explanation

Correct Answer

B:

Command-based workflows supply repeatable user-invoked instructions and arguments; this behavior directly supports the need to provide a consistent shortcut for a common repository maintenance task. A command does not on its own grant additional operating-system permissions.

Incorrect Answers

A:

For the alternate objective to expose approved project-specific actions without copying credentials into prompts, an MCP integration declares external capabilities and their transport while access remains controlled by the server; the feature here must provide a consistent shortcut for a common repository maintenance task, and a server connection does not automatically make every operation safe or authorized.

C:

When an application needs to share coding conventions with every collaborator entering the same repository, a checked-in memory file supplies persistent project context across relevant coding sessions; the current capability must instead provide a consistent shortcut for a common repository maintenance task, while a personal user-level instruction file does not automatically impose a shared team standard.

D:

Tool lifecycle hooks enforce programmable validation at defined execution points; the supported outcome is to block edits to a protected deployment file before a tool writes them, whereas this scenario requires the ability to provide a consistent shortcut for a common repository maintenance task; post-hoc code review cannot prevent the initial unauthorized edit.

Question 407

A team maintaining a credential management needs to route borderline high-risk requests to a review process instead of automatic publication. Which implementation most directly satisfies the requirement?

  1. Deploy content moderation and escalation
  2. Build a documented rollback and incident process
  3. Enforce least-privilege tool permissions
  4. Rate-limit high-risk endpoints

Explanation

Correct Answer

A:

A defined moderation workflow handles uncertain or sensitive material according to business policy; this behavior directly supports the need to route borderline high-risk requests to a review process instead of automatic publication. Blocking every ambiguous input may be unnecessarily disruptive.

Incorrect Answers

B:

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 route borderline high-risk requests to a review process instead of automatic publication; improvised rollback during an outage increases operational risk.

C:

For the alternate objective to let a support assistant read shipment status without issuing refunds, restricted scopes and read-only interfaces limit impact if a tool request is manipulated; the feature here must route borderline high-risk requests to a review process instead of automatic publication, and role language in the prompt cannot prevent an overprivileged API token from writing.

D:

Per-identity quotas and anomaly monitoring make bulk misuse harder; this applies to the different goal to reduce automated abuse of a model-backed export or search capability, not the requirement to route borderline high-risk requests to a review process instead of automatic publication; a single global throughput cap may still let one actor consume all capacity.

Question 408

A production API team owns two independent components. The first must reject forged callbacks from an external asynchronous job service; the second must reject a malformed tool argument payload before calling a payroll service. Which paired plan fulfills both?

  1. First component: Use pull requests and focused code review. Second component: Separate integration tests from unit tests.
  2. First component: Separate integration tests from unit tests. Second component: Validate JSON before deserialization.
  3. First component: Validate webhook signatures. Second component: Validate JSON before deserialization.
  4. First component: Validate webhook signatures. Second component: Use pull requests and focused code review.
  5. First component: Use exponential backoff with jitter. Second component: Use pull requests and focused code review.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because cryptographic verification checks the sender and payload integrity before processing the event, while the second proposal fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects; their respective acceptance criteria are to reject forged callbacks from an external asynchronous job service and to reject a malformed tool argument payload before calling a payroll service.

Incorrect Answers

A:

The first proposal serves the different purpose to detect unsafe permissions and schema changes before merging an agent tool instead of the assigned first role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned second role because integration tests exercise boundaries and serialization that isolated mocks may miss; their respective acceptance criteria are to reject forged callbacks from an external asynchronous job service and to reject a malformed tool argument payload before calling a payroll service.

B:

The first proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned first role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal fits its assigned role because a parser and schema validator catch missing types and invalid syntax before side effects; their respective acceptance criteria are to reject forged callbacks from an external asynchronous job service and to reject a malformed tool argument payload before calling a payroll service.

D:

The first proposal fits its assigned role because cryptographic verification checks the sender and payload integrity before processing the event, while the second proposal serves the different purpose to detect unsafe permissions and schema changes before merging an agent tool instead of the assigned second role because peer review creates an explicit checkpoint for correctness, security, and maintainability; their respective acceptance criteria are to reject forged callbacks from an external asynchronous job service and to reject a malformed tool argument payload before calling a payroll service.

E:

The first proposal serves the different purpose to recover from transient 429 responses without synchronized retry storms instead of the assigned first role because increasing randomized delays reduce contention and respect service throttling signals, while the second proposal serves the different purpose to detect unsafe permissions and schema changes before merging an agent tool instead of the assigned second role because peer review creates an explicit checkpoint for correctness, security, and maintainability; their respective acceptance criteria are to reject forged callbacks from an external asynchronous job service and to reject a malformed tool argument payload before calling a payroll service.

Question 409

A developer is reviewing alternatives for an API reliability feature that must restore an integration after an API key is revoked. Which option is a defensible fit?

  1. Interpret max_tokens as a truncation cause
  2. Investigate a 401 authentication failure
  3. Replay a failing case with a fixed fixture
  4. Investigate a 403 authorization failure

Explanation

Correct Answer

B:

Authentication errors require checking credential validity and configuration; this behavior directly supports the need to restore an integration after an API key is revoked. A larger output-token budget cannot authenticate the caller.

Incorrect Answers

A:

When an application needs 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 current capability must instead restore an integration after an API key is revoked, while a valid parse of the partial prefix does not make the report complete.

C:

This approach serves the separate need to compare application behavior before and after a prompt or SDK change because recorded inputs and tool mocks isolate regressions from variable live data; it does not establish the outcome to restore an integration after an API key is revoked, and an uncontrolled production retry can hide intermittent errors.

D:

Authorization failures concern permission or policy after identity is established; despite being useful when a service must determine why a valid service identity is denied a protected capability, it is not a solution to restore an integration after an API key is revoked; rotating an otherwise valid key will not necessarily grant missing access.

Question 410

The acceptance criteria for an agent extensibility change state that it must prevent a server update from returning incompatible payloads to clients. Which implementation aligns with that criterion?

  1. Expose an MCP tool for an external action
  2. Expose an MCP resource for reference content
  3. Use stdio for a local MCP process
  4. Validate MCP tool schemas and results

Explanation

Correct Answer

D:

Contract tests check declared capabilities, argument shapes, and expected response content; this behavior directly supports the need to prevent a server update from returning incompatible payloads to clients. Successful connection does not prove semantic correctness.

Incorrect Answers

A:

For the alternate objective to let multiple compatible clients request a controlled shipment lookup, MCP tools advertise callable operations with named parameters and schemas across client integrations; the feature here must prevent a server update from returning incompatible payloads to clients, and a resource intended only for reading context does not perform arbitrary commands.

B:

Resources provide identifiable data that clients can fetch for model context; this applies to the different goal to make a versioned product catalog available for read-oriented context retrieval, not the requirement to prevent a server update from returning incompatible payloads to clients; treating static content as a privileged executable tool unnecessarily expands authority.

C:

When an application needs to connect a desktop development tool to a trusted local server process, standard input and output transport is suitable for a client-managed local subprocess; the current capability must instead prevent a server update from returning incompatible payloads to clients, while it is not a remotely addressable network service by itself.

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