Skip to main content
ITPrepCerts
Login
Exams Free Samples About Contact
Login Create an account

CCDV-F Claude Certified Developer Foundations

  • Anthropic
  • 97 practice questions
  • Updated Sep 2026
  • 16 free sample questions

About this exam

CCDV-F is the Anthropic exam Claude Certified Developer Foundations. Practice material is available as a PDF, an interactive practice test or a bundle of both.

Exam code
CCDV-F
Vendor
Anthropic
Practice questions
97
Questions with an explanation
97 of 97
Free sample questions
16
Question bank last updated
11 Sep 2026

Try 2 sample questions

Taken from the free sample set for CCDV-F.

Question 1

Your Claude agent has access to a tool that retrieves customer records. A teammate has noticed that the agent occasionally calls the tool with arguments the schema does not declare, and the tool's downstream service returns an error each time. The teammate proposes loosening the schema so the tool accepts whatever arguments the model produces.

How would you respond?

  1. Option A:

    Add a system prompt instruction telling the model to produce schema-conforming arguments, treating the prompt instruction as the primary mechanism for keeping the agent's tool calls valid.

  2. Option B:

    Keep the schema strict, validate arguments before dispatching, and return a structured error so the agent can retry.


  3. Option C:

    Remove the schema entirely and rely on the downstream service to reject invalid calls, treating the downstream service as the team's primary enforcement layer.


  4. Option D:

    Loosen the schema as the teammate proposed so the downstream service receives every call the agent makes during normal operation.


Show answer and explanation

Correct answer: B

The supplied question identifies B as the intended answer. Tool schemas are contracts between Claude and executable application code. When the downstream service accepts only a defined set of arguments, relaxing that schema merely shifts invalid data farther into the system and increases runtime failures.

Anthropic's current tooling provides an even stronger implementation of this principle through strict tool use . Setting strict: true constrains tool inputs to the declared JSON Schema, preventing undeclared properties, missing required values, and incompatible parameter types where the supported schema subset is used. Anthropic explicitly recommends strict tool use for validated parameters, type-safe function calls, and reliable agentic workflows.

In a non-strict or legacy implementation, the application should still validate arguments before dispatch and convert invalid calls into structured tool errors that Claude can interpret and potentially correct. A prompt instruction can reinforce behavior, but it should not replace deterministic validation. C and D weaken the system boundary and knowingly send invalid calls downstream.

Therefore, maintain the contract rather than adapting the contract to malformed model output.

Relevant Claude Developer topics: Agent Construction, tool schemas, strict tool use, JSON Schema, parameter validation, structured errors, retry behavior, and defensive execution boundaries .

===============

Question 2

Your Claude agent has too many tools, and many of them have overlapping functionality. The agent often picks an inappropriate tool when several could plausibly handle a request.

How would you address the tool selection problem?

  1. Option A:

    Add more tools to cover every variation of the requests the agent handles, on the grounds that more tools give the agent more accurate options to choose from.


  2. Option B:

    Remove all tools and rely on the agent's general capability instead, with the application losing the workflows that previously relied on tools.


  3. Option C:

    Add detailed examples to each tool's description so the agent can match incoming requests to the right tool by example, treating the examples as the team's selection mechanism.

  4. Option D:

    Restructure the tool set by consolidating overlapping tools, removing unused tools, and clarifying tool descriptions so each tool has a distinct purpose.

Show answer and explanation

Correct answer: D

Option D addresses the architectural cause of the failure: an ambiguous tool surface. Claude chooses tools partly from their names, descriptions, schemas, and the relationship between the request and the capability described. If multiple tools appear to perform substantially the same task, selection becomes unnecessarily difficult.

Anthropic’s tool-definition guidance explicitly recommends consolidating related operations into fewer tools and making descriptions clear about both what a tool does and when it should be used. The documentation notes that fewer, more capable tools reduce selection ambiguity and make the available tool surface easier for Claude to navigate.

Option A makes the ambiguity worse by expanding an already overlapping tool set. B destroys required application capabilities. C could improve selection somewhat, because examples can clarify complex inputs, but it leaves the underlying duplication intact. Examples complement good tool design; they are not a substitute for distinct tool responsibilities.

Therefore, D is the strongest solution: remove unused tools, merge functions that represent the same conceptual operation, and write discriminative descriptions defining appropriate and inappropriate usage. Relevant Study Guide topics: tool design, tool selection, descriptions, tool consolidation, agent construction, and reducing ambiguity.

===============

See all 16 free sample questions