CCDV-F Anthropic Claude Certified Developer-Foundations Free Practice Exam Questions (2026 Updated)

Option B is correct because destructive production operations require deterministic enforcement outside the model’s probabilistic reasoning. Claude Code hooks can intercept lifecycle events before tool execution and explicitly allow, deny, or request further handling based on concrete rules.

Anthropic’s hooks documentation provides this exact security pattern. A PreToolUse hook can inspect a proposed command before execution and return a blocking decision. Anthropic’s example demonstrates blocking destructive operations such as drop table, while other commands proceed normally.

That mechanism can be adapted to database controls: block DROP, destructive DELETE, unauthorized schema modifications, or production writes; require explicit approval for high-risk operations; and allow read-only or known-safe queries automatically.

A merely increases the probability that someone might notice an unsafe operation and does not prevent execution. C assumes model capability can replace access controls, which is an unacceptable safety boundary. D is useful behavioral guidance but remains probabilistic and cannot guarantee prevention.

Therefore, B creates a deterministic control between model intent and side-effect execution. Relevant Study Guide topics: Claude hooks, PreToolUse, tool governance, deterministic enforcement, approval gates, least privilege, and destructive-operation protection.

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

Option C is correct. Claude Code uses CLAUDE.md as the standard mechanism for supplying persistent project-level instructions and context. Anthropic's Claude Code documentation states that project instructions can be stored in ./CLAUDE.md or ./.claude/CLAUDE.md and shared with team members through source control. Appropriate content includes coding standards, architectural decisions, project conventions, build/test commands, preferred workflows, and information developers would otherwise need to repeat to Claude during every session. The /init command can also generate an initial CLAUDE.md based on the repository.

A wiki may be valuable for human documentation, but Claude Code does not automatically receive that material as project context. B creates developer-specific configuration and risks inconsistency across the team. D places the information in a human-facing README but does not use Claude Code's purpose-built persistent instruction mechanism.

Therefore, C gives the repository a shared, version-controlled source of Claude-specific project guidance. Relevant Study Guide topics: CLAUDE.md, project configuration, persistent instructions, repository context, team standards, and configuration management.

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

Option B is correct because plugin dependencies and releases must be versioned deliberately if the team wants reproducible behavior and a reliable rollback path. Claude Code’s plugin documentation supports explicit semantic versions in plugin manifests and marketplace entries, and the plugin system uses the resolved version as part of update detection and caching. Version constraints can also keep dependent plugins on a tested compatible range until the team intentionally upgrades.

The incident happened because the team could not determine which plugin version had previously worked. Explicit tracking solves that directly: record the version in project configuration, pin known-good releases where stability matters, test upgrades, and change versions through reviewed configuration updates. This creates traceability and makes regression isolation much faster.

Option A removes useful extension functionality instead of managing it. Option C treats third-party change as uncontrollable even though the platform provides version-management mechanisms. Option D automatically moving everything to the latest release increases change frequency and can reproduce the same regression problem.

Therefore, B is the correct configuration-management response. Relevant Study Guide topics: Claude Code plugins, semantic versioning, dependency constraints, reproducible configuration, controlled upgrades, rollback, and configuration management.

B is directly supported by both the supplied examination source and Claude Code's configuration model. The source marks the hierarchical CLAUDE.md approach as correct. Claude Code supports instructions at multiple scopes, allowing broadly applicable standards to be separated from project-specific context rather than duplicated across every repository.

Anthropic documents several CLAUDE.md scopes. Organization-managed instructions can apply broadly; user-level instructions in ~/.claude/CLAUDE.md apply across a user's projects; project instructions in ./CLAUDE.md or ./.claude/CLAUDE.md provide repository-specific architecture, conventions, commands, and workflows. Claude Code loads applicable files according to the directory hierarchy, allowing broad instructions and more specific local instructions to coexist.

This arrangement improves maintainability because common coding standards are defined once at the appropriate scope, while each repository retains only the context unique to that project. A documentation website does not automatically inject rules into Claude Code context. C creates inconsistent manual configuration. D improperly couples unrelated repositories to one repository's configuration.

Relevant Claude Developer topics: Confia Management, CLAUDE.md hierarchy, organization scope, user scope, project scope, repository configuration, instruction inheritance, and configuration reuse .

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

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 .

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

Option B addresses the actual architectural failure: low-value historical material is crowding out the high-signal information required for current reasoning. A larger context window does not guarantee better attention to important constraints. Effective agent architecture actively manages what remains in context as the workflow progresses.

Anthropic's Context Editing documentation explicitly provides tool-result clearing for agentic workflows with heavy tool usage. Once Claude has processed an older result, verbose file contents, search output, or API responses may no longer need to remain in full. Older results can therefore be removed while recent and important state remains available. Anthropic also documents compaction, where accumulated history is summarized and replaced with a smaller representation that preserves important task state.

A removes an important agent capability rather than solving context growth. C retains all accumulated noise and merely gives it more space. D repeatedly destroys valuable task state and creates artificial workflow boundaries.

Therefore, B preserves goals, decisions, unresolved constraints, and necessary results while reducing irrelevant historical content. Relevant Study Guide topics: context engineering, tool-result clearing, compaction, long-running agents, context quality, and task-state preservation.

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

The question presents a trust-boundary failure: model-generated tool arguments are being accepted without sufficient validation before an external operation executes. A tool call should therefore be treated like input arriving at any typed application interface—the application must ensure that the tool name and arguments satisfy the declared contract before dispatch.

Anthropic describes tool use as a contract in which the application defines the tool's schema and Claude returns structured tool_use input. Current Claude functionality also supports strict: true, which guarantees schema-compliant tool inputs through constrained generation and specifically addresses invented parameters, incompatible types, and missing required fields. For applications not using strict tool use, explicit application-side validation and a controlled error path remain essential.

B knowingly executes invalid input. C relies on uncontrolled repetition rather than deterministic validation and bounded recovery. D eliminates a useful capability instead of correcting its execution boundary.

Therefore, A provides the correct defensive design. Relevant Study Guide topics: tool calling, tool_use, input_schema, strict tool use, schema validation, defensive execution, error handling, and secure tool dispatch.