CCDV-F Exam Questions & Answers

Option B applies few-shot, or multishot, prompting, one of Anthropic's recommended techniques for steering Claude when examples of desired behavior are available. Labeled input/output pairs give Claude concrete demonstrations of how it should respond, which is particularly valuable when edge cases are difficult to express completely through abstract rules.

Anthropic states that examples are among the most reliable mechanisms for steering output format, tone, and structure. Its prompting guidance recommends relevant, diverse examples that cover edge cases while avoiding accidental patterns. For best results, examples should be clearly separated from the main instructions, such as by using <example> and <examples> tags.

A retrieval database could be useful if a very large or dynamically selected example collection were required, but that adds unnecessary complexity for the small labeled set described. C is disproportionate: a few examples do not justify replacing the application's Claude integration with custom model training. D avoids rather than solves the identified failure mode.

Therefore, B directly uses the available supervision at inference time and allows rapid iteration through evaluation. Relevant Claude Developer topics are prompt construction, few-shot prompting, edge-case handling, example selection, evaluation-driven iteration, and behavioral steering.

The supplied Claude Developer item selects A. The symptoms---duplicated logic, tangled control flow, and increasing difficulty adding features---indicate accumulated technical debt in a component that has become structurally difficult to change. Because the problem is already materially reducing development velocity, deliberate refactoring should occur before additional feature pressure compounds it.

The objective is behavioral preservation with structural improvement. Duplicated prompt construction should be consolidated where the behavior is genuinely shared. Prompt preparation, configuration, API invocation, validation, error handling, and post-processing should have clear responsibilities. Control flow should be simplified so each stage is testable independently. Existing tests should first capture important current behavior so refactoring can proceed without silently changing application semantics.

B can be appropriate for minor cleanup, but the question describes broad systemic complexity. Mixing substantial structural refactoring into unrelated feature tickets makes scope, review, and regression analysis harder. C knowingly allows the debt to compound. D centralizes complexity rather than removing it and violates separation of concerns.

Relevant Claude Developer topics: SW Eng Foundations, refactoring, technical debt, DRY, separation of concerns, maintainability, modular design, regression testing, and control-flow simplification.

The supplied Claude Certified Developer Foundations material identifies A as the best answer. The decision should begin with the actual capability gap rather than a predetermined preference for built-in or custom tooling. If the existing capability can satisfy the requirement with a small supported extension or composition, using it avoids unnecessary implementation and maintenance. If the missing capability is fundamental, a custom tool becomes justified.

Anthropic's tool architecture explicitly supports both categories. Claude provides Anthropic-managed or predefined tools while also allowing developers to define custom tools for operations specific to their application. With a custom client tool, the application defines the contract and executes the operation before returning its result to Claude.

A is more complete than C because it evaluates both sides of the boundary: whether the existing mechanism can realistically meet the missing requirement and, if not, whether custom implementation is warranted. B prioritizes precedent over current requirements. D only determines whether the unmodified built-in tool is sufficient and does not address what to do when it is almost---but not entirely---sufficient.

Relevant Claude Developer topics: built-in tools, custom tools, capability-gap analysis, tool contracts, maintenance cost, extensibility, and agent construction decisions.

Option D applies the correct hybrid pattern. Anthropic distinguishes workflows---where LLMs and tools execute along predefined code paths---from agents, where the model dynamically determines how to proceed. Anthropic recommends choosing the simplest architecture that meets the requirement: workflows provide predictability and consistency for well-understood tasks, while agents are valuable where flexible model-driven decisions are necessary.

Standard invoice processing is explicitly described as a small number of known steps. That makes a deterministic workflow the appropriate default because the path can be tested, monitored, and reproduced. The unexpected-format branch is different: the system must reason among rerouting, requesting clarification, or human escalation. That decision point is where agentic flexibility adds value.

A makes the entire process autonomous even though most steps do not require autonomy, increasing cost, latency, and unpredictability. B introduces multiple specialized agents despite no demonstrated need for that complexity. C collapses deterministic processing and exception handling into one monolithic model call, making validation and debugging harder.

Therefore, D combines workflow predictability with targeted agentic reasoning. Relevant Study Guide topics: workflows versus agents, routing, exception handling, hybrid agentic architecture, escalation, and complexity minimization.

Option D treats prompts as production configuration and executable application behavior rather than informal text. A prompt modification can change output format, tool-selection behavior, policy enforcement, downstream compatibility, token usage, or model quality just as materially as an ordinary source-code change. Consequently, prompt changes need traceability, review, testing, and rollback.

A single source of truth prevents different application paths from silently using inconsistent prompt versions. Version control provides an immutable history showing who changed the prompt, what changed, and which application release used it. Pull-request review enables peer assessment and automated evaluation before deployment. The same configuration-as-code principle appears throughout Claude Code's project configuration model, where shared project configuration is designed to live with version-controlled project artifacts.

A removes governance and creates an uncontrolled external state. B increases hidden runtime behavior and bypasses normal review. C solves fragmentation but leaves the exact governance failure described in the scenario---the ability to ship prompt changes without review.

Therefore, D provides reproducibility and controlled change management. Relevant Study Guide topics: prompt versioning, configuration management, source control, change review, reproducibility, regression testing, and rollback.