Anthropic CCDV-F (Claude Certified Developer - Foundations) Practice Test 39

Question 380

A document processing application is approaching release, but the team still needs to give Claude Code the project's build, test, and architecture conventions. What is the most appropriate implementation?

  1. Put repository guidance in CLAUDE.md
  2. Validate configuration at startup
  3. Version prompt templates alongside code
  4. Keep environment-specific settings external
  5. Pin a tested model identifier

Explanation

Correct Answer

A:

Repository memory files provide persistent instructional context to coding sessions; this behavior directly supports the need to give Claude Code the project's build, test, and architecture conventions. They are not an application secrets manager or the API's global system prompt.

Incorrect Answers

B:

For the alternate objective to fail fast if a model ID or tool endpoint is absent in production, startup checks surface missing required values before user traffic reaches a broken path; the feature here must give Claude Code the project's build, test, and architecture conventions, and a late runtime exception spreads one configuration defect across many requests.

C:

Source-controlled prompt assets make rollbacks, diffs, and evaluations possible; this applies to the different goal to trace a quality regression to the exact instruction revision used, not the requirement to give Claude Code the project's build, test, and architecture conventions; editing prompts in an unversioned dashboard hides causal history.

D:

When an application needs to deploy the same application build to staging and production with distinct endpoints, configuration injection separates environment differences from immutable application artifacts; the current capability must instead give Claude Code the project's build, test, and architecture conventions, while hard-coded URLs require risky code changes for promotion.

E:

Explicit model versions support reproducibility and controlled migrations; the supported outcome is to keep deployment behavior stable while evaluating new model releases separately, whereas this scenario requires the ability to give Claude Code the project's build, test, and architecture conventions; a floating alias can change behavior without an application code change.

Question 381

A document processing team owns two independent components. The first must separate an end user's request from the developer's stable operating instructions; the second must stop processing when a user cancels a long report and release resources cleanly. Which paired plan fulfills both?

  1. First component: Keep user tasks in the user message. Second component: Add cancellation handling to streaming UI.
  2. First component: Keep user tasks in the user message. Second component: Create one session per user conversation.
  3. First component: Create one session per user conversation. Second component: Return user-friendly error states.
  4. First component: Return user-friendly error states. Second component: Add cancellation handling to streaming UI.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because explicit message roles distinguish requested work from higher-priority operational framing, while the second proposal fits its assigned role because cancellation signals should propagate through streams, queues, and workers where supported; their respective acceptance criteria are to separate an end user's request from the developer's stable operating instructions and to stop processing when a user cancels a long report and release resources cleanly.

Incorrect Answers

B:

The first proposal fits its assigned role because explicit message roles distinguish requested work from higher-priority operational framing, while the second proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned second role because session scoping ensures history and tool results belong to the correct principal; their respective acceptance criteria are to separate an end user's request from the developer's stable operating instructions and to stop processing when a user cancels a long report and release resources cleanly.

C:

The first proposal serves the different purpose to keep follow-up requests linked without exposing another tenant's messages instead of the assigned first role because session scoping ensures history and tool results belong to the correct principal, while the second proposal serves the different purpose to explain service limits or tool outages without leaking stack traces or secrets instead of the assigned second role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs; their respective acceptance criteria are to separate an end user's request from the developer's stable operating instructions and to stop processing when a user cancels a long report and release resources cleanly.

D:

The first proposal serves the different purpose to explain service limits or tool outages without leaking stack traces or secrets instead of the assigned first role because structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs, while the second proposal fits its assigned role because cancellation signals should propagate through streams, queues, and workers where supported; their respective acceptance criteria are to separate an end user's request from the developer's stable operating instructions and to stop processing when a user cancels a long report and release resources cleanly.

Question 382

An incident response application is approaching release, but the team still needs to branch between remediation and escalation based on the result of a security scan. What is the most appropriate implementation?

  1. Use an independent verifier step
  2. Use a plan-execute-review loop
  3. Use bounded memory with explicit provenance
  4. Use a graph with conditional edges

Explanation

Correct Answer

D:

Conditional graph transitions encode known branches while allowing model reasoning within selected nodes; this behavior directly supports the need to branch between remediation and escalation based on the result of a security scan. A linear chain cannot express result-dependent routing cleanly.

Incorrect Answers

A:

This approach serves the separate need to detect mistakes in an agent-generated SQL migration before running it because a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors; it does not establish the outcome to branch between remediation and escalation based on the result of a security scan, and asking the original agent whether it is correct is weaker than executable verification.

B:

Separating plan, execution, and review makes deviations visible before a final outcome is accepted; despite being useful when a service must manage a complex migration that requires checkpoints after several tool actions, it is not a solution to branch between remediation and escalation based on the result of a security scan; a one-shot response cannot verify environmental effects.

C:

For the alternate objective to preserve customer preferences across permitted sessions while distinguishing facts from assumptions, typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; the feature here must branch between remediation and escalation based on the result of a security scan, and arbitrary model-generated memories can become a source of drift.

Question 383

A release plan for a model platform platform has two acceptance checks: component one must lower spend for large scheduled classification jobs that do not need immediate responses; component two must reduce token spend without losing facts needed for the current request. Which proposal passes both?

  1. First component: Use batch pricing where deadline permits. Second component: Shorten irrelevant conversation history.
  2. First component: Keep volatile fields after reusable context. Second component: Shorten irrelevant conversation history.
  3. First component: Use batch pricing where deadline permits. Second component: Set maximum step counts for agents.
  4. First component: Set maximum step counts for agents. Second component: Keep volatile fields after reusable context.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal fits its assigned role because selective context assembly preserves active constraints while removing obsolete turns; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to reduce token spend without losing facts needed for the current request.

Incorrect Answers

B:

The first proposal serves the different purpose to prevent request timestamps from invalidating a costly static prefix instead of the assigned first role because stable instruction and reference sections should precede changing per-request details for effective prefix reuse, while the second proposal fits its assigned role because selective context assembly preserves active constraints while removing obsolete turns; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to reduce token spend without losing facts needed for the current request.

C:

The first proposal fits its assigned role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal serves the different purpose to contain cumulative token and tool cost across a recursive research session instead of the assigned second role because a bound on iterations prevents repeated generation and calls from growing without limit; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to reduce token spend without losing facts needed for the current request.

D:

The first proposal serves the different purpose to contain cumulative token and tool cost across a recursive research session instead of the assigned first role because a bound on iterations prevents repeated generation and calls from growing without limit, while the second proposal serves the different purpose to prevent request timestamps from invalidating a costly static prefix instead of the assigned second role because stable instruction and reference sections should precede changing per-request details for effective prefix reuse; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to reduce token spend without losing facts needed for the current request.

Question 384

A developer is reviewing alternatives for an incident response feature that must execute an unchanged sequence of extraction, validation, and publishing steps. Which option is a defensible fit?

  1. Use a deterministic workflow
  2. Pass structured handoff artifacts between workers
  3. Apply routing before task execution
  4. Use an agentic decision loop
  5. Use parallel fan-out and a reconciliation step

Explanation

Correct Answer

A:

A fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit; this behavior directly supports the need to execute an unchanged sequence of extraction, validation, and publishing steps. A free-running agent adds planning variability without helping when every step is already known.

Incorrect Answers

B:

When an application needs to preserve evidence and data lineage when one agent delegates a subtask to another, defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff; the current capability must instead execute an unchanged sequence of extraction, validation, and publishing steps, while free-form chat summaries can omit identifiers required by the next worker.

C:

An inexpensive classification or rule-based router sends each request to the applicable predefined workflow; the supported outcome is to choose the right specialised handling path from the request category, whereas this scenario requires the ability to execute an unchanged sequence of extraction, validation, and publishing steps; a generic autonomous planner is unnecessary when branches are stable and explicitly defined.

D:

This approach serves the separate need to investigate an open-ended incident where the next query depends on earlier findings because a model-directed loop can choose subsequent actions based on tool observations until it reaches a stopping condition; it does not establish the outcome to execute an unchanged sequence of extraction, validation, and publishing steps, and a predetermined chain cannot reliably anticipate all branches of an exploratory diagnosis.

E:

Parallel tasks reduce critical-path latency when they do not depend on one another; a join step resolves conflicting findings; despite being useful when a service must analyze several independent document sections concurrently and combine the results, it is not a solution to execute an unchanged sequence of extraction, validation, and publishing steps; a serial chain makes independent stages wait without improving correctness.

Question 385

A data pipeline team is evaluating two disjoint use cases. For one use case, it must rotate production credentials without committing new source code; for the other, it must allow broad exploratory tools in a sandbox but only approved reads in production. Which paired choices are justified?

  1. First component: Store API keys in managed secret storage. Second component: Use separate permission profiles by environment.
  2. First component: Use settings.json for Claude Code permissions. Second component: Use separate permission profiles by environment.
  3. First component: Store API keys in managed secret storage. Second component: Validate configuration at startup.
  4. First component: Validate configuration at startup. Second component: Use settings.json for Claude Code permissions.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because central secret management supports scoped access, auditing, and key rotation, while the second proposal fits its assigned role because environment-scoped policy avoids inheriting development privileges in a live setting; their respective acceptance criteria are to rotate production credentials without committing new source code and to allow broad exploratory tools in a sandbox but only approved reads in production.

Incorrect Answers

B:

The first proposal serves the different purpose to constrain a repository coding assistant's allowed tools and execution behavior instead of the assigned first role because permission settings define configurable controls for Claude Code rather than merely describing preferences, while the second proposal fits its assigned role because environment-scoped policy avoids inheriting development privileges in a live setting; their respective acceptance criteria are to rotate production credentials without committing new source code and to allow broad exploratory tools in a sandbox but only approved reads in production.

C:

The first proposal fits its assigned role because central secret management supports scoped access, auditing, and key rotation, while the second proposal serves the different purpose to fail fast if a model ID or tool endpoint is absent in production instead of the assigned second role because startup checks surface missing required values before user traffic reaches a broken path; their respective acceptance criteria are to rotate production credentials without committing new source code and to allow broad exploratory tools in a sandbox but only approved reads in production.

D:

The first proposal serves the different purpose to fail fast if a model ID or tool endpoint is absent in production instead of the assigned first role because startup checks surface missing required values before user traffic reaches a broken path, while the second proposal serves the different purpose to constrain a repository coding assistant's allowed tools and execution behavior instead of the assigned second role because permission settings define configurable controls for Claude Code rather than merely describing preferences; their respective acceptance criteria are to rotate production credentials without committing new source code and to allow broad exploratory tools in a sandbox but only approved reads in production.

Question 386

A team maintaining a Claude Code repository needs to block edits to a protected deployment file before a tool writes them. Which implementation most directly satisfies the requirement?

  1. Configure permissions in Claude Code settings
  2. Use a pre-execution hook for deterministic checks
  3. Use a project-level CLAUDE.md file
  4. Use headless invocation for automation

Explanation

Correct Answer

B:

Tool lifecycle hooks enforce programmable validation at defined execution points; this behavior directly supports the need to block edits to a protected deployment file before a tool writes them. Post-hoc code review cannot prevent the initial unauthorized edit.

Incorrect Answers

A:

This approach serves the separate need to deny destructive commands regardless of what a generated plan proposes because explicit allow and deny rules establish executable tool policy rather than advisory prose; it does not establish the outcome to block edits to a protected deployment file before a tool writes them, and a markdown warning can be ignored or misinterpreted by the agent.

C:

For the alternate objective to share coding conventions with every collaborator entering the same repository, a checked-in memory file supplies persistent project context across relevant coding sessions; the feature here must block edits to a protected deployment file before a tool writes them, and a personal user-level instruction file does not automatically impose a shared team standard.

D:

Noninteractive execution lets scripts integrate agent work into existing pipelines with controlled formats; this applies to the different goal to run Claude Code inside a CI job and capture its output without interactive prompts, not the requirement to block edits to a protected deployment file before a tool writes them; treating interactive terminal output as a stable machine interface is fragile.

Question 387

Engineers are splitting an agent governance service into two independently tested functions. Function A must block a generated database query that targets another tenant's records, while function B must avoid transmitting unnecessary customer identifiers with a summarization request. Which plan is sound?

  1. First component: Use output escaping to prevent XSS. Second component: Minimize personally identifiable information.
  2. First component: Validate tool arguments server-side. Second component: Minimize personally identifiable information.
  3. First component: Treat tool and retrieval text as untrusted. Second component: Use output escaping to prevent XSS.
  4. First component: Validate tool arguments server-side. Second component: Treat tool and retrieval text as untrusted.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal fits its assigned role because redaction and selective fields reduce exposure before data enters model or logging paths; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to avoid transmitting unnecessary customer identifiers with a summarization request.

Incorrect Answers

A:

The first proposal serves the different purpose to display generated customer notes safely in a browser instead of the assigned first role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript, while the second proposal fits its assigned role because redaction and selective fields reduce exposure before data enters model or logging paths; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to avoid transmitting unnecessary customer identifiers with a summarization request.

C:

The first proposal serves the different purpose to stop an injected wiki page from asking an assistant to export credentials instead of the assigned first role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates, while the second proposal serves the different purpose to display generated customer notes safely in a browser instead of the assigned second role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to avoid transmitting unnecessary customer identifiers with a summarization request.

D:

The first proposal fits its assigned role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal serves the different purpose to stop an injected wiki page from asking an assistant to export credentials instead of the assigned second role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; their respective acceptance criteria are to block a generated database query that targets another tenant's records and to avoid transmitting unnecessary customer identifiers with a summarization request.

Question 388

A developer is reviewing alternatives for a model platform feature that must classify a familiar support message where labels and criteria are already clear. Which option is a defensible fit?

  1. Use varied sampling only for ideation
  2. Use contrasting few-shot examples
  3. Apply zero-shot instructions for a straightforward task
  4. Budget tokens rather than characters

Explanation

Correct Answer

C:

Direct instructions can be sufficient when the task is simple and well specified; this behavior directly supports the need to classify a familiar support message where labels and criteria are already clear. Adding examples unnecessarily consumes context and can introduce biases.

Incorrect Answers

A:

For the alternate objective to brainstorm diverse naming candidates without demanding identical wording on every run, greater sampling diversity can produce a wider range of suggestions for exploratory work; the feature here must classify a familiar support message where labels and criteria are already clear, and it is not appropriate as the sole correctness control for structured production data.

B:

Multiple representative cases help define a decision boundary and reduce ambiguity; this applies to the different goal to distinguish borderline policy labels with examples of both allowed and disallowed cases, not the requirement to classify a familiar support message where labels and criteria are already clear; repeating near-identical samples does not cover edge cases.

D:

Tokenization splits text into model-specific units, so character counts are not a reliable context proxy; the supported outcome is to estimate whether a multilingual request will fit a model context window, whereas this scenario requires the ability to classify a familiar support message where labels and criteria are already clear; equal-length strings can have different token usage.

Question 389

In an operations orchestration project, acceptance test A checks whether a component can explain why an agent modified a configuration during a failed automated release. Acceptance test B checks whether a different component can keep a customer service application operating when an expensive specialist agent cannot complete. Which plan satisfies both tests?

  1. First component: Use event logs for tool actions. Second component: Use bounded memory with explicit provenance.
  2. First component: Use an independent verifier step. Second component: Use a graceful fallback path.
  3. First component: Use event logs for tool actions. Second component: Use a graceful fallback path.
  4. First component: Use bounded memory with explicit provenance. Second component: Use an independent verifier step.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because structured traces connect tool intent, arguments, results, and subsequent decisions for audit and replay, while the second proposal fits its assigned role because a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; their respective acceptance criteria are to explain why an agent modified a configuration during a failed automated release and to keep a customer service application operating when an expensive specialist agent cannot complete.

Incorrect Answers

A:

The first proposal fits its assigned role because structured traces connect tool intent, arguments, results, and subsequent decisions for audit and replay, while the second proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned second role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to explain why an agent modified a configuration during a failed automated release and to keep a customer service application operating when an expensive specialist agent cannot complete.

B:

The first proposal serves the different purpose to detect mistakes in an agent-generated SQL migration before running it instead of the assigned first role because a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors, while the second proposal fits its assigned role because a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; their respective acceptance criteria are to explain why an agent modified a configuration during a failed automated release and to keep a customer service application operating when an expensive specialist agent cannot complete.

D:

The first proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned first role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions, while the second proposal serves the different purpose to detect mistakes in an agent-generated SQL migration before running it instead of the assigned second role because a separate validation stage checks the artifact against explicit tests and constraints, limiting self-confirming errors; their respective acceptance criteria are to explain why an agent modified a configuration during a failed automated release and to keep a customer service application operating when an expensive specialist agent cannot complete.

Question 390

A production-readiness check for an incident response component requires the service to preserve evidence and data lineage when one agent delegates a subtask to another. Which approach passes this check?

  1. Pass structured handoff artifacts between workers
  2. Use an explicit completion condition and step budget
  3. Use a deterministic workflow
  4. Introduce a human approval checkpoint

Explanation

Correct Answer

A:

Defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff; this behavior directly supports the need to preserve evidence and data lineage when one agent delegates a subtask to another. Free-form chat summaries can omit identifiers required by the next worker.

Incorrect Answers

B:

For the alternate objective to bound the runtime of an agent that repeatedly searches without converging, a maximum iteration or cost budget plus a clear success criterion stops runaway tool loops; the feature here must preserve evidence and data lineage when one agent delegates a subtask to another, and merely asking the model to finish quickly does not enforce execution limits.

C:

A fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit; this applies to the different goal to execute an unchanged sequence of extraction, validation, and publishing steps, not the requirement to preserve evidence and data lineage when one agent delegates a subtask to another; a free-running agent adds planning variability without helping when every step is already known.

D:

When an application needs to prevent an autonomous investigation from issuing irreversible account changes without review, a human gate separates analysis from externally consequential action and gives a reviewer a veto; the current capability must instead preserve evidence and data lineage when one agent delegates a subtask to another, while a system-prompt request to be careful is not an enforceable approval workflow.

Claude Certified Developer - Foundations (CCDV-F) Practice Tests