Anthropic CCDV-F - Claude Certified Developer-Foundations

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 .

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

Option A applies the correct context-engineering strategy: remove stale tool results once they no longer contribute useful information to subsequent reasoning. Agentic workflows frequently accumulate search results, file contents, API responses, and intermediate artifacts. Keeping all of them indefinitely consumes the finite context window, raises token cost, and can reduce model focus by introducing low-value information.

Anthropic specifically documents tool result clearing for this situation. Context Editing can remove older tool results when the conversation grows, while preserving recent interactions and optionally retaining tools whose results must remain available. Anthropic describes old tool outputs such as retrieved files or search results as candidates for clearing after Claude has processed them.

Prompt caching in B solves a different problem: it can lower cost and latency for repeated static prompt prefixes, but cached tokens still constitute context and therefore do not eliminate context-window pressure. C changes model capability without solving the architectural cause. D maximizes context pollution.

The correct architecture is therefore to preserve high-signal state while pruning ephemeral intermediate outputs. This aligns with Claude Developer coverage of context engineering, long-running agents, context-window management, tool-result clearing, and efficient agent state management. Anthropic's broader context-engineering guidance likewise emphasizes curating the smallest high-signal context necessary for successful inference.

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

Option A correctly treats the MCP server as a reusable integration boundary rather than application-specific code. Model Context Protocol separates capability providers from consuming Claude applications by exposing standardized tools, resources, and prompts through an MCP-compatible interface. A shared server therefore needs explicit capability definitions, an appropriate transport or communication pattern, and a deployment location reachable by its intended clients.

Anthropic’s MCP documentation distinguishes remote HTTP-based integrations from local/client-managed connections. For remotely shared services, the server must be reachable from the consuming environment; client-side MCP helpers additionally support broader MCP capabilities such as resources and prompts.

B unnecessarily couples the server design to the first consumer and encourages application-specific evolution of what should be a reusable service boundary. C prevents multi-application deployment because only local developer sessions could reach the service. D abandons MCP entirely and recreates duplicated integrations in every consuming application.

Thus, A provides the correct lifecycle: define the MCP contract, expose resources/tools/prompts appropriately, select the transport according to topology, deploy the service, and let multiple applications consume the standardized interface independently. Relevant Study Guide topics: MCP architecture, reusable services, tools, resources, prompts, transports, and deployment topology.

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

The supplied exam source marks D . Claude prompt caching is designed for repeated prompt prefixes, not semantic caching of generated answers. High-value cache candidates include stable system prompts, long instructions, tool definitions, shared background documents, repeated examples, and the previously accumulated prefix of a multi-turn conversation.

Anthropic explains that prompt caching reuses a matching prompt prefix and can substantially reduce processing time and input-token cost on subsequent requests. The cache operates across the request structure—tools, system content, and messages up to the relevant cache boundary. It is particularly useful for prompts with many examples, large repeated context, repetitive instructions, and long multi-turn conversations.

B describes response caching , which is a separate application-level technique and is not what Anthropic's prompt caching feature does. C targets the portion that usually changes most, making it a poor general cache boundary. A is incorrect because multi-turn workloads are a major prompt-caching use case.

Therefore, maximize reusable stable prefixes and place changing request-specific content after them where practical.

Relevant Claude Developer topics: Claude API Mechanics, prompt caching, cache prefixes, token-cost optimization, static context, system prompts, multi-turn conversations, and API efficiency .

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

Option C accurately captures Anthropic’s distinction. Prompt engineering primarily concerns how instructions are written, structured, and organized to obtain the desired behavior from a particular model invocation. Techniques include explicit instructions, examples, roles, XML structure, output requirements, and task-specific prompt construction. Context engineering operates at a broader architectural level: it determines which information should actually be present in the model’s context at each inference step.

Anthropic defines prompt engineering as methods for writing and organizing LLM instructions, whereas context engineering encompasses strategies for curating and maintaining the optimal set of tokens during inference. For long-running agents, context can contain system instructions, tools, MCP resources, retrieved documents, prior messages, tool results, summaries, and memory.

This distinction matters because multi-step agents continuously generate new state. Effective systems may prune obsolete results, retrieve information just in time, compact earlier conversation history, isolate subagent contexts, or store persistent state externally. B is incorrect because context engineering has not simply replaced prompt engineering; the two operate at different scopes. A defines context too narrowly, and D obscures an important architectural distinction.

Therefore, C correctly represents Claude Developer coverage of prompt engineering versus context engineering, context curation, agent state, long-horizon workflows, and context-window optimization.

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

Option A correctly applies selective enforcement. Claude Code hooks can execute automatically at lifecycle events such as PreToolUse, and matchers or conditions can narrow exactly which operations trigger a hook. Anthropic’s hook reference demonstrates this pattern by applying a PreToolUse hook specifically to destructive shell operations rather than indiscriminately processing every command. The documentation notes that if the matcher or conditional expression does not match, the handler is skipped, avoiding unnecessary process-spawn overhead.

That architecture is particularly appropriate for costly or security-sensitive checks. High-risk events—destructive file operations, privileged commands, production changes, or access to sensitive resources—can receive deterministic pre-execution enforcement while routine low-risk actions proceed without additional hook latency.

B creates an avoidable period in which safeguards disappear entirely. C reduces application availability without addressing the actual source of overhead. D is technically weaker because system-prompt instructions influence model behavior but are not equivalent to deterministic lifecycle interception capable of blocking execution.

Therefore, hooks should be scoped using event types, matchers, and conditions according to risk. Relevant Claude Developer topics are Claude Code hooks, agent construction, tool governance, deterministic controls, permission boundaries, safety/performance tradeoffs, and lifecycle interception.

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

Option D is correct because the problem is not insufficient nominal context capacity; it is degraded signal quality as the working context grows. Anthropic’s context-window guidance explicitly states that more context is not automatically better. As conversations expand, recall and accuracy can degrade through “context rot,” so long-running agents need active context management rather than simply retaining every prior tool result.

A good pattern preserves the active task state while compacting, summarizing, or pruning stale intermediate outputs. Anthropic documents server-side compaction for long-running conversations and context-editing/pruning approaches that clear old tool results when they no longer contribute useful information. This keeps high-value constraints and conclusions visible without carrying every verbose response forward.

Option A changes frameworks without fixing the architectural cause. Option B may reduce call count but also creates larger multi-purpose tools and does not guarantee better context quality. Option C increases capacity while preserving the same low-signal accumulation, so the relevant facts can remain buried.

Therefore, D best implements context engineering for agentic workloads. Relevant Study Guide topics: context engineering, context rot, compaction, tool-result pruning, long-running agents, state preservation, and context-window optimization.

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

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 .

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