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?
Answer(s): A
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.
The Anthropic API deprecated a request parameter that your Claude application uses in approximately 40 places across the codebase. The deprecation notice gives a six-month window before the parameter is removed and recommends a replacement parameter with slightly different semantics.You would respond to the deprecation by...
Answer(s): C
The supplied examination source selects C. Because the replacement parameter has different semantics, this is not a mechanical rename. The application must establish what existing behavior is important, encode that behavior in regression tests, and migrate incrementally so deviations can be detected and isolated.Anthropic's deprecation guidance follows the same lifecycle principle. Deprecated components remain temporarily available but receive a retirement deadline and a recommended replacement. Anthropic advises migrating before retirement and thoroughly testing applications against replacements well in advance of the cutoff. Its API versioning documentation also emphasizes compatibility contracts while acknowledging that APIs evolve and deprecated versions eventually become unavailable.Batch migration reduces blast radius. If one migrated group fails regression tests, the team can diagnose the semantic difference before changing remaining call sites. It also avoids concentrating all migration risk near the retirement deadline.A delays risk until the worst possible time. B only hides the dependency and does not complete migration. D changes all 40 usages simultaneously, making regression diagnosis and rollback substantially harder.Relevant Claude Developer topics: API lifecycle, deprecation management, regression testing, incremental migration, compatibility, technical debt, and controlled change management.
Your Claude application is producing inconsistent outputs for similar inputs, even when using the same model and prompt. You want to debug the issue systematically.Your debugging approach would...
Answer(s): D
The examination source explicitly identifies D. Non-determinism is a normal LLM property, but that fact does not justify assuming every inconsistency is unavoidable. Systematic diagnosis begins by capturing the complete execution conditions for successful and unsuccessful runs.A useful trace should expose the actual user input, system prompt, prior messages or context, tools and tool results where applicable, model identifier, request parameters, output, stop reason, and relevant execution events. Current Anthropic agent infrastructure exposes session, span, and agent events specifically to provide observability into session state and execution progress. This makes comparison possible: the engineer can determine whether apparently 'same' calls actually differ in accumulated context, tool state, model configuration, parameters, or external data.A changes a variable before establishing the cause and, on newer Claude releases, temperature may not even be configurable. B generates additional samples but does not ensure the underlying conditions are understood. C prematurely classifies unexplained behavior as acceptable nondeterminism.The correct sequence is observe, compare, form a hypothesis, reproduce, modify, and evaluate.Relevant Claude Developer topics: observability, tracing, debugging, model nondeterminism, request-state capture, failure reproduction, and production diagnostics.
You are writing a system prompt for a Claude application that needs to produce output in a specific JSON shape. The downstream system will reject any output that does not match the schema.Your prompt would need to...
The supplied question selects D. If a downstream component requires an exact machine-readable structure, the expected structure must be communicated explicitly rather than left to Claude's discretion. The prompt should define required fields, types, nesting, permissible values where relevant, and instruct Claude not to emit surrounding prose.Anthropic's consistency guidance states that developers should precisely specify the desired output format when format consistency matters. More importantly, current Claude APIs provide Structured Outputs for cases requiring guaranteed JSON Schema conformance; Anthropic explicitly recommends Structured Outputs instead of prompt-only techniques when valid schema-compliant JSON is mandatory.Therefore, D is the strongest prompt choice among the listed alternatives. In a contemporary production implementation, the design can be strengthened further by supplying the schema through Claude's structured-output configuration and performing downstream semantic validation where business rules exceed JSON Schema.A permits arbitrary formatting. B intentionally creates inconsistent representations. C assumes post-processing can reliably reconstruct missing or ambiguously formatted information, which is significantly less robust than specifying the contract up front.Relevant Claude Developer topics: system prompts, JSON formatting, structured outputs, schema constraints, output contracts, validation, and downstream integration reliability.
You are building a Claude application that needs to deliver model output to end users as it is generated, instead of waiting for the full response to complete.The Claude API mechanism you would use is...
Answer(s): B
Option B is the intended and technically correct answer. The supplied Claude Developer exam source selects streaming responses. Streaming allows the client application to begin receiving output before generation of the complete message has finished, reducing perceived latency for interactive user experiences.Anthropic's official Messages API documentation states that setting stream: true causes responses to be delivered incrementally through Server-Sent Events (SSE). Claude can stream text deltas as well as other event types, including structured tool-use and extended-thinking events where applicable. Anthropic's SDKs provide corresponding synchronous or asynchronous streaming helpers.The application consumes events as they arrive, updates the UI progressively, and then handles the final event or stop reason when generation completes. This architecture is particularly useful for chat interfaces and other latency-sensitive interactive experiences.A addresses output structure, not progressive transmission. C is designed for asynchronous, throughput-oriented processing rather than immediate user interaction. D reduces processing cost and latency for repeated prompt prefixes but does not itself turn a response into an incremental stream.Relevant Claude Developer topics: Messages API, streaming, SSE, incremental tokens, latency, event handling, interactive applications, and API response mechanics.
Post your Comments and Discuss Anthropic CCDV-F exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CCDV-F content, but please register or login to continue.