Anthropic CCDV-F real exam prep : Claude Certified Developer-Foundations

The team is debating whether to build a new capability as a custom tool or to use an existing built-in tool that nearly covers the use case but lacks one specific feature.
How would you decide?

• A. Review the built-in tool's documentation and assess whether its existing capabilities are sufficient to cover the use case without any modification or extension.
• B. Identify whether the team has previously built similar custom tools and use those precedents to determine which approach is more consistent with the existing codebase.
• C. Examine the custom tool option by scoping the implementation effort and determining whether the additional flexibility justifies the development and maintenance cost.
• D. Evaluate whether the missing feature can be addressed by extending the built-in tool or warrants a custom tool, then choose accordingly.

A teammate has asked you to explain the difference between context engineering and prompt engineering.
They have heard the terms used interchangeably and are unsure how each applies to a Claude application that processes long-running multi-step tasks.
How would you describe the distinction?

• A. Prompt engineering and context engineering each address content the team gives Claude, but the team can group them under a single workflow because the practices use overlapping techniques.
• B. Prompt engineering shapes individual prompts for specific outputs, while context engineering manages how content flows across turns and steps and takes steps to keep relevant state visible.
• C. Prompt engineering is the older term for prompt design, while context engineering is the newer term that has replaced it in modern Claude applications across the industry.
• D. Prompt engineering focuses on the model's response, while context engineering focuses on the user's input across many sessions in a long-running multi-step Claude application.

A teammate has asked you to explain why your Claude agent's tools include detailed descriptions in the tool definition, even when the tool name is already descriptive. The teammate suggests removing the descriptions to simplify the tool definitions.
How would you respond?

• A. Suggest replacing the descriptions with example calls embedded in the tool definition, treating example calls as a complete substitute for the prose description.
• B. Suggest moving the descriptions out of the tool definition and into a separate documentation file the team maintains so the tool definitions stay short and the descriptions remain available.
• C. Agree with the teammate because tool names are sufficient for the model to choose the right tool on every request the agent handles.
• D. Explain that the model uses the tool description to decide when to call the tool, and descriptions disambiguate cases where the tool name is not enough.

A teammate is debugging a Claude application whose system prompt has grown to several hundred lines and now contains overlapping, contradictory, and obsolete instructions.
How would you advise the teammate?

• A. Split the prompt across multiple system prompts so the model sees a smaller portion at any given time.
• B. Add more explicit instructions so the most recent rules dominate the model's interpretation of the prompt during each request.
• C. Tighten only the contradictory rules first, treating the overlap and obsolete content as lower-priority work the team can address later.
• D. Audit the prompt for overlap, contradiction, and obsolete content, then refactor so each instruction is clear, current, and non-redundant.

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?

• A. Keep the schema strict, validate arguments before dispatching, and return a structured error so the agent can retry.
• B. 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.
• C. 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.
• D. Loosen the schema as the teammate proposed so the downstream service receives every call the agent makes during normal operation.