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

Question 10

An engineer extending a data pipeline workflow has been asked to let Claude request a read-only inventory lookup with typed arguments. Which choice addresses the request most precisely?

  1. Handle message_stop and final usage events
  2. Supply a tool definition with input schema
  3. Process tool_use responses in the application
  4. Call the Messages API with explicit model and max_tokens
  5. Reconcile batch responses by custom_id

Explanation

Correct Answer

B:

A declared tool name, description, and schema constrain the interface offered to the model; this behavior directly supports the need to let Claude request a read-only inventory lookup with typed arguments. Listing a function in a prompt does not create a callable tool contract.

Incorrect Answers

A:

The final stream events signal completion and deliver accumulated metadata beyond individual text fragments; the supported outcome is to record complete streamed output and token usage accurately, whereas this scenario requires the ability to let Claude request a read-only inventory lookup with typed arguments; stopping after the first content delta truncates responses.

C:

Client tools execute in application code; the model emits structured requests but does not invoke external functions itself; despite being useful when a service must actually retrieve a customer's order status requested by Claude, it is not a solution to let Claude request a read-only inventory lookup with typed arguments; displaying the tool request as the final answer never performs the lookup.

D:

For the alternate objective to return an answer to a short user request through a backend service, a message request identifies the target model, a message list, and an output-token ceiling; the feature here must let Claude request a read-only inventory lookup with typed arguments, and the API is not a stateful chat session unless prior turns are supplied.

E:

A caller-assigned identifier links each result to the original request independently of result ordering; this applies to the different goal to match returned batch results to the right source documents despite varying completion order, not the requirement to let Claude request a read-only inventory lookup with typed arguments; assuming completion order matches submission order risks mixing customer data.

Question 11

A design meeting for a retrieval pipeline platform concludes that two isolated services require different behavior: one must avoid answering a pricing question from last month's retrieved cache, and another must prevent outdated user preferences from being treated as current task instructions. Which arrangement meets the specification?

  1. First component: Preserve instruction and evidence boundaries. Second component: Separate long-term memory from active scratchpad.
  2. First component: Prune obsolete tool outputs. Second component: Preserve instruction and evidence boundaries.
  3. First component: Refresh stale evidence before reuse. Second component: Separate long-term memory from active scratchpad.
  4. First component: Refresh stale evidence before reuse. Second component: Prune obsolete tool outputs.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because freshness checks determine whether a saved passage remains authoritative for a dynamic fact, while the second proposal fits its assigned role because explicit storage and freshness rules govern what is retained and when it is reintroduced; their respective acceptance criteria are to avoid answering a pricing question from last month's retrieved cache and to prevent outdated user preferences from being treated as current task instructions.

Incorrect Answers

A:

The first proposal serves the different purpose to keep an embedded webpage instruction from becoming higher-priority application policy instead of the assigned first role because context assembly must label external text as data and avoid granting it authority over tool use, while the second proposal fits its assigned role because explicit storage and freshness rules govern what is retained and when it is reintroduced; their respective acceptance criteria are to avoid answering a pricing question from last month's retrieved cache and to prevent outdated user preferences from being treated as current task instructions.

B:

The first proposal serves the different purpose to stop stale log dumps from crowding out new evidence during an agent session instead of the assigned first role because tool-result pruning removes redundant bulky observations after their findings are retained, while the second proposal serves the different purpose to keep an embedded webpage instruction from becoming higher-priority application policy instead of the assigned second role because context assembly must label external text as data and avoid granting it authority over tool use; their respective acceptance criteria are to avoid answering a pricing question from last month's retrieved cache and to prevent outdated user preferences from being treated as current task instructions.

D:

The first proposal fits its assigned role because freshness checks determine whether a saved passage remains authoritative for a dynamic fact, while the second proposal serves the different purpose to stop stale log dumps from crowding out new evidence during an agent session instead of the assigned second role because tool-result pruning removes redundant bulky observations after their findings are retained; their respective acceptance criteria are to avoid answering a pricing question from last month's retrieved cache and to prevent outdated user preferences from being treated as current task instructions.

Question 12

The current design of an engineering productivity pipeline does not adequately detect mistakes in an agent-generated SQL migration before running it. Which improvement resolves the gap?

  1. Use a graceful fallback path
  2. Use an independent verifier step
  3. Use a plan-execute-review loop
  4. Prefer a finite state machine for regulated steps

Explanation

Correct Answer

B:

A separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors; this behavior directly supports the need to detect mistakes in an agent-generated SQL migration before running it. Asking the original agent whether it is correct is weaker than executable verification.

Incorrect Answers

A:

A bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; the supported outcome is to keep a customer service application operating when an expensive specialist agent cannot complete, whereas this scenario requires the ability to detect mistakes in an agent-generated SQL migration before running it; unbounded retries do not ensure eventual success.

C:

Separating plan, execution, and review makes deviations visible before a final outcome is accepted; despite being useful when a service must manage a complex migration that requires checkpoints after several tool actions, it is not a solution to detect mistakes in an agent-generated SQL migration before running it; a one-shot response cannot verify environmental effects.

D:

For the alternate objective to enforce approval, execution, and confirmation order in a compliance workflow, explicit states and transitions control who may advance a case independently of generated language; the feature here must detect mistakes in an agent-generated SQL migration before running it, and an unrestricted agent loop can skip expected governance stages.

Question 13

A privacy controls review requires two independent, explicitly defined outcomes: the first workstream must prevent a compromised tool step from sending internal files to arbitrary destinations; a second must protect payload confidentiality between the application and its API endpoint. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Scope database credentials by tenant and operation
  2. Use output escaping to prevent XSS
  3. Add an explicit export approval check
  4. Encrypt sensitive data in transit
  5. Limit external network egress for agents

Explanation

Correct Answers

D:

Modern transport encryption limits interception across network boundaries; this directly supports task 2 to protect payload confidentiality between the application and its API endpoint, not the separate task or tasks to prevent a compromised tool step from sending internal files to arbitrary destinations; merely obfuscating a prompt is not transport security.

E:

Network policy restricts which services a tool process can contact; this directly supports task 1 to prevent a compromised tool step from sending internal files to arbitrary destinations, not the separate task or tasks to protect payload confidentiality between the application and its API endpoint; a natural-language prohibition cannot enforce packet-level isolation.

Incorrect Answers

A:

Least-privilege identity limits the damage from a manipulated tool call; this implements the different outcome to prevent a read-only support tool from modifying billing tables rather than the required tasks to prevent a compromised tool step from sending internal files to arbitrary destinations and to protect payload confidentiality between the application and its API endpoint, and a broad administrator token bypasses application intent, so it is not a direct solution to any of the assigned workstreams.

B:

Context-aware encoding prevents text from being interpreted as active HTML or JavaScript; this implements the different outcome to display generated customer notes safely in a browser rather than the required tasks to prevent a compromised tool step from sending internal files to arbitrary destinations and to protect payload confidentiality between the application and its API endpoint, and an instruction to the model not to write scripts is not a rendering control, so it is not a direct solution to any of the assigned workstreams.

C:

A separate authorization or human approval step can gate high-impact operations; this implements the different outcome to prevent unreviewed bulk downloads triggered by an agent's tool plan rather than the required tasks to prevent a compromised tool step from sending internal files to arbitrary destinations and to protect payload confidentiality between the application and its API endpoint, and the model's confidence in its own plan does not grant export permission, so it is not a direct solution to any of the assigned workstreams.

Question 14

An external system access delivery milestone depends on two separate capabilities. One module must call a protected internal pricing API under the application's own credentials; a second module must make a coding or API assistant follow organization-wide conventions. Which implementation option is appropriate?

  1. First component: Create a custom client-side tool. Second component: Use subagents for independent expertise.
  2. First component: Create a custom client-side tool. Second component: Use system or repository instructions for stable behavior.
  3. First component: Use a deterministic workflow for fixed stages. Second component: Use system or repository instructions for stable behavior.
  4. First component: Use subagents for independent expertise. Second component: Use a deterministic workflow for fixed stages.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because local execution gives the developer direct control over authentication, validation, and side effects, 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 call a protected internal pricing API under the application's own credentials and to make a coding or API assistant follow organization-wide conventions.

Incorrect Answers

A:

The first proposal fits its assigned role because local execution gives the developer direct control over authentication, validation, and side effects, 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 call a protected internal pricing API under the application's own credentials and to make a coding or API assistant follow organization-wide conventions.

C:

The first proposal serves the different purpose to automate the same classify-review-export path across predictable submissions instead of the assigned first role because explicit application control makes each transition testable and easier to audit, 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 call a protected internal pricing API under the application's own credentials and to make a coding or API assistant follow organization-wide conventions.

D:

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 automate the same classify-review-export path across predictable submissions instead of the assigned second role because explicit application control makes each transition testable and easier to audit; their respective acceptance criteria are to call a protected internal pricing API under the application's own credentials and to make a coding or API assistant follow organization-wide conventions.

Question 15

A design meeting for a Claude application platform concludes that two isolated services require different behavior: one must reproduce a working SDK installation across staging and production, and another must prevent bursts of document jobs from overwhelming rate limits and memory. Which arrangement meets the specification?

  1. First component: Pin dependencies with lockfiles. Second component: Enforce concurrency limits.
  2. First component: Pin dependencies with lockfiles. Second component: Keep secrets out of source control.
  3. First component: Keep secrets out of source control. Second component: Version APIs and response schemas.
  4. First component: Version APIs and response schemas. Second component: Enforce concurrency limits.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because locked versions and hashes constrain drift between build environments, while the second proposal fits its assigned role because a semaphore or bounded queue keeps in-flight work within measured capacity; their respective acceptance criteria are to reproduce a working SDK installation across staging and production and to prevent bursts of document jobs from overwhelming rate limits and memory.

Incorrect Answers

B:

The first proposal fits its assigned role because locked versions and hashes constrain drift between build environments, while the second proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned second role because secret stores or environment injection keep production tokens out of committed code; their respective acceptance criteria are to reproduce a working SDK installation across staging and production and to prevent bursts of document jobs from overwhelming rate limits and memory.

C:

The first proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned first role because secret stores or environment injection keep production tokens out of committed code, while the second proposal serves the different purpose to allow older application clients to keep working while a new extraction field is introduced instead of the assigned second role because compatibility-aware contracts and versioned behavior protect consumers from surprise breaking changes; their respective acceptance criteria are to reproduce a working SDK installation across staging and production and to prevent bursts of document jobs from overwhelming rate limits and memory.

D:

The first proposal serves the different purpose to allow older application clients to keep working while a new extraction field is introduced instead of the assigned first role because compatibility-aware contracts and versioned behavior protect consumers from surprise breaking changes, while the second proposal fits its assigned role because a semaphore or bounded queue keeps in-flight work within measured capacity; their respective acceptance criteria are to reproduce a working SDK installation across staging and production and to prevent bursts of document jobs from overwhelming rate limits and memory.

Question 16

A technical specification for an application security application assigns two jobs to separate modules: module A must block a generated database query that targets another tenant's records, and module B must stop an injected wiki page from asking an assistant to export credentials. Which two-part solution is appropriate?

  1. First component: Add an explicit export approval check. Second component: Scope database credentials by tenant and operation.
  2. First component: Validate tool arguments server-side. Second component: Treat tool and retrieval text as untrusted.
  3. First component: Validate tool arguments server-side. Second component: Add an explicit export approval check.
  4. First component: Scope database credentials by tenant and operation. Second component: Treat tool and retrieval text as untrusted.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal fits its assigned role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to stop an injected wiki page from asking an assistant to export credentials.

Incorrect Answers

A:

The first proposal serves the different purpose to prevent unreviewed bulk downloads triggered by an agent's tool plan instead of the assigned first role because a separate authorization or human approval step can gate high-impact operations, while the second proposal serves the different purpose to prevent a read-only support tool from modifying billing tables instead of the assigned second role because least-privilege identity limits the damage from a manipulated tool call; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to stop an injected wiki page from asking an assistant to export credentials.

C:

The first proposal fits its assigned role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal serves the different purpose to prevent unreviewed bulk downloads triggered by an agent's tool plan instead of the assigned second role because a separate authorization or human approval step can gate high-impact operations; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to stop an injected wiki page from asking an assistant to export credentials.

D:

The first proposal serves the different purpose to prevent a read-only support tool from modifying billing tables instead of the assigned first role because least-privilege identity limits the damage from a manipulated tool call, while the second proposal fits its assigned role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to stop an injected wiki page from asking an assistant to export credentials.

Question 17

A design review identifies a missing capability in a source-control workflow project: it must make a specialised review procedure available as task-specific instructions and assets. Which change meets that goal?

  1. Create a reusable Skill
  2. Define a custom slash command workflow
  3. Use a project-level CLAUDE.md file
  4. Connect an MCP server to Claude Code
  5. Use directory-scoped instructions

Explanation

Correct Answer

A:

A Skill packages a repeatable capability that Claude can load when relevant to the work; this behavior directly supports the need to make a specialised review procedure available as task-specific instructions and assets. A one-off chat turn is not a maintainable shared workflow definition.

Incorrect Answers

B:

For the alternate objective to provide a consistent shortcut for a common repository maintenance task, command-based workflows supply repeatable user-invoked instructions and arguments; the feature here must make a specialised review procedure available as task-specific instructions and assets, and a command does not on its own grant additional operating-system permissions.

C:

A checked-in memory file supplies persistent project context across relevant coding sessions; this applies to the different goal to share coding conventions with every collaborator entering the same repository, not the requirement to make a specialised review procedure available as task-specific instructions and assets; a personal user-level instruction file does not automatically impose a shared team standard.

D:

When an application needs 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 current capability must instead make a specialised review procedure available as task-specific instructions and assets, while a server connection does not automatically make every operation safe or authorized.

E:

More local instruction files help scope guidance to the appropriate subtree; the supported outcome is to apply specialised rules only to a sensitive infrastructure folder, whereas this scenario requires the ability to make a specialised review procedure available as task-specific instructions and assets; root guidance alone can be too broad when different modules have conflicting conventions.

Question 18

A design meeting for a tool integration platform concludes that two isolated services require different behavior: one must automate the same classify-review-export path across predictable submissions, and another must delegate a security analysis while keeping the main coordinator's context concise. Which arrangement meets the specification?

  1. First component: Use a deterministic workflow for fixed stages. Second component: Use subagents for independent expertise.
  2. First component: Use hooks for enforceable safety checks. Second component: Use subagents for independent expertise.
  3. First component: Use a deterministic workflow for fixed stages. Second component: Use system or repository instructions for stable behavior.
  4. First component: Use system or repository instructions for stable behavior. Second component: Use hooks for enforceable safety checks.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because explicit application control makes each transition testable and easier to audit, while the second proposal fits its assigned role because specialist contexts reduce tool-output contamination and support focused parallel work; their respective acceptance criteria are to automate the same classify-review-export path across predictable submissions and to delegate a security analysis while keeping the main coordinator's context concise.

Incorrect Answers

B:

The first proposal serves the different purpose to deny destructive filesystem operations before a coding agent executes them instead of the assigned first role because runtime interception can apply deterministic policies to proposed actions, while the second proposal fits its assigned role because specialist contexts reduce tool-output contamination and support focused parallel work; their respective acceptance criteria are to automate the same classify-review-export path across predictable submissions and to delegate a security analysis while keeping the main coordinator's context concise.

C:

The first proposal fits its assigned role because explicit application control makes each transition testable and easier to audit, while the second proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned second role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to automate the same classify-review-export path across predictable submissions and to delegate a security analysis while keeping the main coordinator's context concise.

D:

The first proposal serves the different purpose to make a coding or API assistant follow organization-wide conventions instead of the assigned first role because instructions shape model behavior and task framing without executing external operations, while the second proposal serves the different purpose to deny destructive filesystem operations before a coding agent executes them instead of the assigned second role because runtime interception can apply deterministic policies to proposed actions; their respective acceptance criteria are to automate the same classify-review-export path across predictable submissions and to delegate a security analysis while keeping the main coordinator's context concise.

Question 19

After pilot feedback, an incident response group needs two independent improvements. The first is to prevent a slow external inventory service from blocking an agent indefinitely; the second is to let an agent run generated scripts without exposing production host files. Which engineering proposal handles both?

  1. First component: Set a tool execution timeout. Second component: Choose isolated sandbox execution for untrusted code.
  2. First component: Set a tool execution timeout. Second component: Implement a custom Messages API tool loop.
  3. First component: Keep user-specific state out of a shared agent process. Second component: Choose isolated sandbox execution for untrusted code.
  4. First component: Implement a custom Messages API tool loop. Second component: Keep user-specific state out of a shared agent process.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because deadlines bound latency and convert stalled calls into explicit recoverable failures, while the second proposal fits its assigned role because a restricted execution environment limits filesystem, network, and resource privileges; their respective acceptance criteria are to prevent a slow external inventory service from blocking an agent indefinitely and to let an agent run generated scripts without exposing production host files.

Incorrect Answers

B:

The first proposal fits its assigned role because deadlines bound latency and convert stalled calls into explicit recoverable failures, while the second proposal serves the different purpose to retain complete control over a small set of proprietary tool calls and their execution order instead of the assigned second role because the application receives tool requests, validates inputs, executes authorized functions, and sends tool results back; their respective acceptance criteria are to prevent a slow external inventory service from blocking an agent indefinitely and to let an agent run generated scripts without exposing production host files.

C:

The first proposal serves the different purpose to serve many tenants without mixing their tool outputs or prior messages instead of the assigned first role because per-request identity and session boundaries prevent cross-tenant context leakage, while the second proposal fits its assigned role because a restricted execution environment limits filesystem, network, and resource privileges; their respective acceptance criteria are to prevent a slow external inventory service from blocking an agent indefinitely and to let an agent run generated scripts without exposing production host files.

D:

The first proposal serves the different purpose to retain complete control over a small set of proprietary tool calls and their execution order instead of the assigned first role because the application receives tool requests, validates inputs, executes authorized functions, and sends tool results back, while the second proposal serves the different purpose to serve many tenants without mixing their tool outputs or prior messages instead of the assigned second role because per-request identity and session boundaries prevent cross-tenant context leakage; their respective acceptance criteria are to prevent a slow external inventory service from blocking an agent indefinitely and to let an agent run generated scripts without exposing production host files.

Question 20

A token economics review requires two independent, explicitly defined outcomes: the first workstream must explain why a plausible answer can still contain an unsupported factual claim; a second must brainstorm diverse naming candidates without demanding identical wording on every run. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Use one representative example
  2. Use contrasting few-shot examples
  3. Recognize next-token generation
  4. Use varied sampling only for ideation
  5. Use low-temperature generation for repeatable extraction

Explanation

Correct Answers

C:

The model predicts likely continuations conditioned on context rather than querying an authoritative truth database by default; this directly supports task 1 to explain why a plausible answer can still contain an unsupported factual claim, not the separate task or tasks to brainstorm diverse naming candidates without demanding identical wording on every run; fluent prose is not evidence that a source was verified.

D:

Greater sampling diversity can produce a wider range of suggestions for exploratory work; this directly supports task 2 to brainstorm diverse naming candidates without demanding identical wording on every run, not the separate task or tasks to explain why a plausible answer can still contain an unsupported factual claim; it is not appropriate as the sole correctness control for structured production data.

Incorrect Answers

A:

A single demonstration can anchor the expected shape and tone of a generated response; this implements the different outcome to clarify a specific formatting convention that a plain instruction was not conveying rather than the required tasks to explain why a plausible answer can still contain an unsupported factual claim and to brainstorm diverse naming candidates without demanding identical wording on every run, and an example is not a formal guarantee that every response will conform, so it is not a direct solution to any of the assigned workstreams.

B:

Multiple representative cases help define a decision boundary and reduce ambiguity; this implements the different outcome to distinguish borderline policy labels with examples of both allowed and disallowed cases rather than the required tasks to explain why a plausible answer can still contain an unsupported factual claim and to brainstorm diverse naming candidates without demanding identical wording on every run, and repeating near-identical samples does not cover edge cases, so it is not a direct solution to any of the assigned workstreams.

E:

Lower randomness often improves consistency for narrow, constrained tasks; this implements the different outcome to reduce variation when a service maps documents into consistent categories rather than the required tasks to explain why a plausible answer can still contain an unsupported factual claim and to brainstorm diverse naming candidates without demanding identical wording on every run, and it does not guarantee identical output or replace schema validation, so it is not a direct solution to any of the assigned workstreams.

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