You are deciding between Claude models for a task. The team has identified three relevant tradeoff dimensions: quality, latency, and cost.The right model is the one that...
Answer(s): C
The supplied Claude Certified Developer Foundations source marks C. Model selection is a multidimensional engineering decision. There is no universally correct Claude model independent of workload requirements; the application must satisfy the required capability or quality while remaining within acceptable latency and cost envelopes.Anthropic's official model-selection guidance explicitly identifies capabilities, speed, and cost as core considerations and recommends testing models against workload-specific benchmarks rather than selecting them from a single metric. The guidance further recommends evaluating actual prompts and data, comparing response accuracy, quality, and edge-case behavior, and then weighing the resulting performance and cost tradeoffs.Options A, B, and D each establish one or two dimensions as primary and effectively defer the remainder. That can lead to a technically unsuitable model---for example, a cheap model that fails the quality threshold or a high-quality model whose latency makes the user experience unacceptable.The correct method is to define minimum acceptable thresholds across all relevant dimensions and benchmark candidate models against the actual workload.Relevant Claude Developer topics: Claude App Design, model selection, capability, quality, latency, cost, benchmarking, workload evaluation, tradeoff analysis, and production optimization.
Your Claude application's prompt was written months ago and has not been updated. The team has discovered through evals that the prompt produces good results on common cases but underperforms on a specific category of inputs that has grown in volume.How would you respond?
Answer(s): A
The correct response is iterative prompt improvement backed by evaluation, making A the appropriate choice. The supplied Claude Certified Developer Foundations material explicitly selects A. When production input distribution changes, a prompt that previously met requirements can become inadequate. The correct engineering response is not to preserve the prompt merely because it once worked; prompts are application components that should evolve with observed workload behavior.Anthropic's official evaluation guidance describes prompt development as a cycle involving test cases, an initial prompt, iterative testing and refinement, final validation, and deployment. Success criteria should be specific and measurable, and evaluations should include representative cases that expose known failure modes.The underperforming category should therefore be incorporated into the evaluation set. The team can modify instructions, examples, context organization, or other prompt components, then compare the revised prompt against both the newly important category and existing common cases. This prevents improvement in one segment from silently producing regressions elsewhere.B avoids the defect instead of correcting it. C risks degrading previously successful behavior. D creates unnecessary architectural fragmentation.Relevant Claude Developer topics: prompt iteration, evaluation-driven development, regression testing, representative test sets, prompt optimization, and production feedback loops.
You are explaining to a stakeholder why running the same Claude prompt twice can produce slightly different results. The stakeholder is concerned this means the application is broken.How would you address the stakeholder's concern?
Option C correctly explains a fundamental property of generative language models. The supplied examination material identifies C as the correct answer. Claude generates subsequent tokens probabilistically rather than retrieving a single fixed answer for each prompt. Consequently, identical or highly similar requests can produce variations in wording, ordering, explanation depth, and sometimes substantive details.Anthropic's API documentation explicitly states that sampling parameters control randomness and, importantly, that even configurations historically using a temperature of 0.0 were not fully deterministic. Current newer Claude models increasingly manage sampling behavior internally, so application design should not assume byte-for-byte identical responses across executions.Production systems therefore handle variation through architecture: schema validation for machine-consumed output, deterministic business-rule checks, retries where appropriate, evaluations for acceptable behavioral ranges, and application-level safeguards. Temperature adjustment may reduce variation on models that support the parameter, but it does not fundamentally convert an LLM into a deterministic function.A incorrectly labels normal model behavior as a defect. B confuses network latency with generation variability. D overstates model snapshot behavior; pinning a model prevents silent model-version changes but does not eliminate sampling variability.Relevant topics: sampling, nondeterminism, validation, retries, model versions, and robust Claude API integration.
You are building an agent that needs to call several internal APIs and a database in a structured, repeatable way. Your team has decided to use the Claude Agent SDK rather than build a custom loop. You are setting up the agent's tool definitions and execution loop.How would you set up the tools and execution loop?
The supplied Claude Developer examination source selects A. The purpose of choosing an agent SDK rather than implementing a custom Messages API loop is to consume the SDK's higher-level abstractions. Re-implementing dispatch, iteration, and state handling would discard much of the value provided by the SDK.Anthropic's current documentation distinguishes low-level tool-use loops from higher-level SDK-managed abstractions. With a manually implemented Messages API workflow, application code must inspect stop_reason, execute requested client tools, append tool_result blocks, preserve conversation history, and repeat until Claude completes the turn. Anthropic's higher-level tooling can instead encapsulate this repetitive control flow. Current migration guidance also confirms that Agent SDK @tool functions are automatically dispatched by the SDK and that agents, tools, and sessions are first-class SDK concepts.B is incorrect because structured tool use should not be replaced with informal plain-text calls. C introduces an unnecessary custom state dependency when no external persistence requirement exists. D duplicates control-loop functionality despite the explicit decision to use the SDK.Relevant Claude Developer topics: Agent SDK, tool definitions, dispatch, agentic loops, conversation state, tool execution, and abstraction selection.
You are choosing between using STDIO-based communication and HTTP-based communication for an MCP server. The server will be invoked by a Claude Code session running locally.Which communication pattern would you use?
Answer(s): D
Option D is directly supported by both the supplied examination material and Claude Code's MCP documentation. The examination source selects STDIO for this local-process scenario.Claude Code's official MCP guidance distinguishes remote HTTP servers from local STDIO servers. Anthropic states that STDIO servers run as local processes and communicate through standard input and standard output. They are particularly suitable for local tools requiring direct machine access or for custom scripts. Claude Code can launch the process itself and communicate with it without creating, exposing, securing, or maintaining a network listener.HTTP is appropriate when the MCP server exists as a separately reachable network service, especially for cloud-hosted or shared services. That requirement is absent here: the server is being invoked locally from a Claude Code session.A creates duplicate transport infrastructure without a stated availability requirement. B incorrectly assumes one transport is universally superior regardless of deployment topology. C describes HTTP polling rather than the normal MCP transport relationship and introduces unnecessary request overhead.Therefore, local execution strongly favors STDIO; remote/shared deployment generally favors HTTP.Relevant Claude Developer topics: MCP architecture, STDIO transport, HTTP transport, Claude Code integrations, local process communication, and deployment topology.
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.