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

Question 660

In a Claude inference cost review, a release requirement is to choose between two supported model releases using evidence rather than reputation. Which implementation addresses that specific requirement?

  1. Compare both candidates on identical representative eval cases.
  2. Design an approved fallback model path with compatibility checks.
  3. Iterate the SDK or HTTP event stream until its terminal event.
  4. Compare quality-adjusted cost per accepted result across candidate models.

Explanation

Correct Answer

A:

To choose between two supported model releases using evidence rather than reputation in this Claude inference cost review, holding inputs and scoring constant reveals quality and latency changes that generic model descriptions cannot settle; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

The proposed alternative helps to preserve critical service during a temporary primary-model problem because fallbacks improve resilience only when downstream schemas, cost limits, and policy controls work with the alternate model; that mechanism does not meet the different requirement to choose between two supported model releases using evidence rather than reputation.

C:

The proposed alternative helps to process partial model output as it is delivered over a streaming connection because streaming clients must handle both content deltas and final status rather than assuming the first chunk is the complete response; that mechanism does not meet the different requirement to choose between two supported model releases using evidence rather than reputation.

D:

The proposed alternative helps to choose a cheaper model only when the workload-level economics improve because a lower token price can be offset by retries, higher failure rates, or excessive output, so accepted-result cost is the useful measure; that mechanism does not meet the different requirement to choose between two supported model releases using evidence rather than reputation.

Question 661

An end-to-end test for a multi-tenant support application checks whether it can identify which search services and internal systems are critical to the workflow and verify that generated categorization meets a business-approved standard. Which plan should be approved to satisfy both checks?

  1. Perform both steps: (1) Refactor in bounded steps under existing tests; (2) convert quality expectations into labeled tests and failure thresholds.
  2. Perform both steps: (1) Refactor in bounded steps under existing tests; (2) use the user's own claude code settings file.
  3. Perform both steps: (1) List upstream systems with permissions, quotas, and failure behavior; (2) convert quality expectations into labeled tests and failure thresholds.
  4. Perform both steps: (1) List upstream systems with permissions, quotas, and failure behavior; (2) use the user's own claude code settings file.

Explanation

Correct Answer

C:

The first change enables the team to identify which search services and internal systems are critical to the workflow because a dependency inventory exposes the operational and authorization constraints that a purely model-centered design misses; the second addresses the separate need to verify that generated categorization meets a business-approved standard because acceptance is meaningful only with representative cases and explicit quality criteria; subjective demo approval cannot establish production fitness.

Incorrect Answers

A:

The second step meets the requirement to verify that generated categorization meets a business-approved standard because acceptance is meaningful only with representative cases and explicit quality criteria; subjective demo approval cannot establish production fitness; the first step would only help to preserve behavior while replacing a fragile parser in an AI integration because small changes constrain regression scope; a wholesale rewrite makes it harder to isolate whether model or parsing behavior changed, leaving the separate requirement to identify which search services and internal systems are critical to the workflow unmet.

B:

Both steps target different results—preserve behavior while replacing a fragile parser in an AI integration and customize one developer's default Claude Code behavior across local projects—because small changes constrain regression scope; a wholesale rewrite makes it harder to isolate whether model or parsing behavior changed and user settings are scoped to one person, so they should not be relied on for enforcing team-wide policy; the required capabilities are instead to identify which search services and internal systems are critical to the workflow and to verify that generated categorization meets a business-approved standard.

D:

The first step is appropriate for the requirement to identify which search services and internal systems are critical to the workflow because a dependency inventory exposes the operational and authorization constraints that a purely model-centered design misses; the other step instead aims to customize one developer's default Claude Code behavior across local projects because user settings are scoped to one person, so they should not be relied on for enforcing team-wide policy, which does not meet the second requirement to verify that generated categorization meets a business-approved standard.

Question 662

A production readiness review of a safety-sensitive Claude application finds that the team cannot yet stop an authenticated user from reading another tenant's records via a tool or reject a malicious instruction inserted into a web-search result rather than the user's direct request. Which paired changes directly remedy the two gaps?

  1. Perform both steps: (1) Check resource-level authorization for every sensitive tool request; (2) revoke and rotate the affected credential and update dependent services.
  2. Perform both steps: (1) Define fail-closed behavior for an enforcement hook and test failure paths; (2) revoke and rotate the affected credential and update dependent services.
  3. Perform both steps: (1) Define fail-closed behavior for an enforcement hook and test failure paths; (2) isolate external search results and validate any resulting tool action independently.
  4. Perform both steps: (1) Check resource-level authorization for every sensitive tool request; (2) isolate external search results and validate any resulting tool action independently.

Explanation

Correct Answer

D:

The first change enables the team to stop an authenticated user from reading another tenant's records via a tool because proving identity does not grant access to every object; the backend must enforce tenant and resource permissions separately; the second addresses the separate need to reject a malicious instruction inserted into a web-search result rather than the user's direct request because indirect attacks exploit lower-trust retrieval surfaces, so trusting search snippets as operational directives crosses a security boundary.

Incorrect Answers

A:

The first step is appropriate for the requirement to stop an authenticated user from reading another tenant's records via a tool because proving identity does not grant access to every object; the backend must enforce tenant and resource permissions separately; the other step instead aims to reduce exposure after an API key is suspected compromised because rotation restores credential control only when the old secret is disabled and consumers move to the replacement safely, which does not meet the second requirement to reject a malicious instruction inserted into a web-search result rather than the user's direct request.

B:

Both steps target different results—avoid accidentally allowing critical writes when a safety check crashes and reduce exposure after an API key is suspected compromised—because a guardrail that silently skips checks on errors is not an effective boundary; failures must prevent the protected action when policy requires it and rotation restores credential control only when the old secret is disabled and consumers move to the replacement safely; the required capabilities are instead to stop an authenticated user from reading another tenant's records via a tool and to reject a malicious instruction inserted into a web-search result rather than the user's direct request.

C:

The second step meets the requirement to reject a malicious instruction inserted into a web-search result rather than the user's direct request because indirect attacks exploit lower-trust retrieval surfaces, so trusting search snippets as operational directives crosses a security boundary; the first step would only help to avoid accidentally allowing critical writes when a safety check crashes because a guardrail that silently skips checks on errors is not an effective boundary; failures must prevent the protected action when policy requires it, leaving the separate requirement to stop an authenticated user from reading another tenant's records via a tool unmet.

Question 663

A design review for a Claude API workload benchmark asks for support to forecast spend for a batch of documents with different input sizes, together with a way to reduce repeated cost for a stable lengthy policy prefix reused many times. Select the two appropriate changes. Choose TWO.

  1. Estimate cost from expected input and output tokens and current model rates.
  2. Compare quality-adjusted cost per accepted result across candidate models.
  3. Measure cache-write overhead against subsequent cache-read savings.
  4. Report p50, p95, and p99 latency by model and operation.
  5. Iterate the SDK or HTTP event stream until its terminal event.

Explanation

Correct Answers

A:

To forecast spend for a batch of documents with different input sizes as part of a design that must also reduce repeated cost for a stable lengthy policy prefix reused many times, workload cost depends on token mix, model choice, and any applicable discounts or caching rather than request count alone; this is why the action is one of the two required selections.

C:

To reduce repeated cost for a stable lengthy policy prefix reused many times as part of a design that must also forecast spend for a batch of documents with different input sizes, cache writes may cost extra while hits are cheaper; the reuse frequency determines whether the optimization saves money; this is why the action is one of the two required selections.

Incorrect Answers

B:

This alternative serves the separate goal to choose a cheaper model only when the workload-level economics improve because a lower token price can be offset by retries, higher failure rates, or excessive output, so accepted-result cost is the useful measure; the required outcomes are instead to forecast spend for a batch of documents with different input sizes and to reduce repeated cost for a stable lengthy policy prefix reused many times.

D:

This alternative serves the separate goal to avoid overlooking slow tail requests hidden by a good average because percentiles expose user experience at the tail and can reveal bottlenecks that a mean response time conceals; the required outcomes are instead to forecast spend for a batch of documents with different input sizes and to reduce repeated cost for a stable lengthy policy prefix reused many times.

E:

This alternative serves the separate goal to process partial model output as it is delivered over a streaming connection because streaming clients must handle both content deltas and final status rather than assuming the first chunk is the complete response; the required outcomes are instead to forecast spend for a batch of documents with different input sizes and to reduce repeated cost for a stable lengthy policy prefix reused many times.

Question 664

The owner of a production inference application needs to ensure refunds above a policy limit receive human sign-off as well as keep a browser application from exposing the secret used for model calls. Which two changes belong in the minimum remediation plan? Choose TWO.

  1. Route Claude requests through a trusted backend service.
  2. Use strict tool input validation for the exposed tool interface.
  3. Place stable application rules in system instructions and untrusted requests in user content.
  4. Add application-owned approval logic around the refund tool.
  5. Configure supported structured outputs with a JSON Schema.

Explanation

Correct Answers

A:

To keep a browser application from exposing the secret used for model calls as part of a design that must also ensure refunds above a policy limit receive human sign-off, a backend controls credentials and access policy while the UI sends user input through an authenticated application endpoint; this is why the action is one of the two required selections.

D:

To ensure refunds above a policy limit receive human sign-off as part of a design that must also keep a browser application from exposing the secret used for model calls, decisions that create financial side effects require deterministic authorization checks beyond a model's recommendation; this is why the action is one of the two required selections.

Incorrect Answers

B:

This alternative serves the separate goal to reject tool arguments that fail a declared shape before tool execution because a strict schema constrains the arguments a model may emit, but application authorization and business-rule checks remain necessary; the required outcomes are instead to ensure refunds above a policy limit receive human sign-off and to keep a browser application from exposing the secret used for model calls.

C:

This alternative serves the separate goal to keep application policy separate from a user's question because instruction placement preserves the distinction between developer intent and user-supplied data; concatenating everything blurs that boundary; the required outcomes are instead to ensure refunds above a policy limit receive human sign-off and to keep a browser application from exposing the secret used for model calls.

E:

This alternative serves the separate goal to need schema-conformant JSON for a downstream parser at generation time because constrained JSON generation targets machine-parseable fields and types; free-form prompting alone does not establish the same guarantee; the required outcomes are instead to ensure refunds above a policy limit receive human sign-off and to keep a browser application from exposing the secret used for model calls.

Question 665

While planning a developer workstation running Claude Code, the product owner specifies that it must give Claude Code repository-specific build and test instructions for future sessions. Which solution fulfills the requirement?

  1. Initialize project guidance and review the resulting CLAUDE.md content.
  2. Invoke the supported noninteractive or print-mode command interface.
  3. Add concise project guidance to the appropriate CLAUDE.md file.
  4. Place a path-targeted rule in the repository's rules configuration.

Explanation

Correct Answer

C:

To give Claude Code repository-specific build and test instructions for future sessions in this developer workstation running Claude Code, Claude Code reads persistent project instructions from its memory hierarchy; one-off chat messages do not reliably establish durable repository guidance; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to introduce Claude Code to an unfamiliar codebase's conventions and commands because repository setup discovers useful project practices, but autogenerated guidance still needs a human check for accuracy and unnecessary detail; that mechanism does not meet the different requirement to give Claude Code repository-specific build and test instructions for future sessions.

B:

The proposed alternative helps to run a Claude Code task from an automated CI job without an interactive terminal because headless operation outputs results for automation and requires explicit credential, permission, and failure handling in the CI environment; that mechanism does not meet the different requirement to give Claude Code repository-specific build and test instructions for future sessions.

D:

The proposed alternative helps to apply a coding convention only when Claude Code edits a particular path because scoped rules keep specialized instructions close to their applicable files, avoiding global instructions that conflict with other modules; that mechanism does not meet the different requirement to give Claude Code repository-specific build and test instructions for future sessions.

Question 666

An end-to-end test for a Claude inference cost review checks whether it can explain a billing increase after lengthy system instructions are added and forecast spend for a batch of documents with different input sizes. Which plan should be approved to satisfy both checks?

  1. Perform both steps: (1) Measure input-token usage per request and track the prompt components; (2) iterate the sdk or http event stream until its terminal event.
  2. Perform both steps: (1) Measure input-token usage per request and track the prompt components; (2) estimate cost from expected input and output tokens and current model rates.
  3. Perform both steps: (1) Propagate cancellation to the active network request when supported; (2) iterate the sdk or http event stream until its terminal event.
  4. Perform both steps: (1) Propagate cancellation to the active network request when supported; (2) estimate cost from expected input and output tokens and current model rates.

Explanation

Correct Answer

B:

The first change enables the team to explain a billing increase after lengthy system instructions are added because repeated prefixes and conversation history consume billable input, so cost cannot be inferred from output length alone; the second addresses the separate need to forecast spend for a batch of documents with different input sizes because workload cost depends on token mix, model choice, and any applicable discounts or caching rather than request count alone.

Incorrect Answers

A:

The first step is appropriate for the requirement to explain a billing increase after lengthy system instructions are added because repeated prefixes and conversation history consume billable input, so cost cannot be inferred from output length alone; the other step instead aims to process partial model output as it is delivered over a streaming connection because streaming clients must handle both content deltas and final status rather than assuming the first chunk is the complete response, which does not meet the second requirement to forecast spend for a batch of documents with different input sizes.

C:

Both steps target different results—stop a no-longer-needed inference when the user's request is cancelled and process partial model output as it is delivered over a streaming connection—because cancelling work can free local resources and avoid processing obsolete results, though already-incurred provider work may still be billed and streaming clients must handle both content deltas and final status rather than assuming the first chunk is the complete response; the required capabilities are instead to explain a billing increase after lengthy system instructions are added and to forecast spend for a batch of documents with different input sizes.

D:

The second step meets the requirement to forecast spend for a batch of documents with different input sizes because workload cost depends on token mix, model choice, and any applicable discounts or caching rather than request count alone; the first step would only help to stop a no-longer-needed inference when the user's request is cancelled because cancelling work can free local resources and avoid processing obsolete results, though already-incurred provider work may still be billed, leaving the separate requirement to explain a billing increase after lengthy system instructions are added unmet.

Question 667

An operational review of a hosted document-processing service reports distinct failures: it cannot keep sensitive case material within approved processing and retention boundaries, and it cannot verify that generated categorization meets a business-approved standard. Which two repairs are required? Choose TWO.

  1. Convert quality expectations into labeled tests and failure thresholds.
  2. Document permitted processing regions and data-handling obligations before selecting a deployment.
  3. Apply content checks at suitable input and output boundaries.
  4. Require structured request IDs, tool traces, and version metadata with privacy controls.
  5. Define availability objectives with failure and recovery criteria.

Explanation

Correct Answers

A:

To verify that generated categorization meets a business-approved standard as part of a design that must also keep sensitive case material within approved processing and retention boundaries, acceptance is meaningful only with representative cases and explicit quality criteria; subjective demo approval cannot establish production fitness; this is why the action is one of the two required selections.

B:

To keep sensitive case material within approved processing and retention boundaries as part of a design that must also verify that generated categorization meets a business-approved standard, legal or organizational constraints must inform provider routing, logging, and retention rather than being added after data already flows; this is why the action is one of the two required selections.

Incorrect Answers

C:

This alternative serves the separate goal to filter risky user-visible content according to application policy because moderation is a defense layer applied around generation, not a substitute for authenticated tool access or scoped retrieval; the required outcomes are instead to keep sensitive case material within approved processing and retention boundaries and to verify that generated categorization meets a business-approved standard.

D:

This alternative serves the separate goal to enable an administrator to determine how a particular AI decision was produced because traceability depends on consistent operational evidence, not just retaining the final generated answer or a screenshot; the required outcomes are instead to keep sensitive case material within approved processing and retention boundaries and to verify that generated categorization meets a business-approved standard.

E:

This alternative serves the separate goal to state how much interruption a customer-facing AI feature can tolerate because reliability requirements determine fallback, retries, health monitoring, and degraded behavior; they are distinct from the response's linguistic quality; the required outcomes are instead to keep sensitive case material within approved processing and retention boundaries and to verify that generated categorization meets a business-approved standard.

Question 668

An operational review of a specialist-agent orchestration service reports distinct failures: it cannot run the same retrieval, validation, and publishing stages in an approved order for every request, and it cannot pursue an open-ended investigation where the next action depends on intermediate evidence. Which two repairs are required? Choose TWO.

  1. Persist and resume the agent session using supported state handling.
  2. Delegate source analysis to a subagent and return a concise result.
  3. Alternate model tool-use requests with tool results until completion.
  4. Encode a deterministic workflow with explicit transitions between stages.
  5. Give an agent a bounded objective and a tool-selection loop.

Explanation

Correct Answers

D:

To run the same retrieval, validation, and publishing stages in an approved order for every request as part of a design that must also pursue an open-ended investigation where the next action depends on intermediate evidence, known control flow belongs in application code, allowing each stage to be tested and audited without asking a model to improvise the sequence; this is why the action is one of the two required selections.

E:

To pursue an open-ended investigation where the next action depends on intermediate evidence as part of a design that must also run the same retrieval, validation, and publishing stages in an approved order for every request, agentic control lets the model choose among permitted steps as observations arrive; budgets and termination conditions still bound its autonomy; this is why the action is one of the two required selections.

Incorrect Answers

A:

This alternative serves the separate goal to continue a paused multi-step task with its legitimate prior context because session continuity preserves relevant work across invocations; discarding session state can cause repeated tools or lost intermediate decisions; the required outcomes are instead to run the same retrieval, validation, and publishing stages in an approved order for every request and to pursue an open-ended investigation where the next action depends on intermediate evidence.

B:

This alternative serves the separate goal to keep a large source-reading task from crowding the coordinator's working context because isolated workspaces let a specialist process extensive material while the parent receives only task-relevant evidence instead of every intermediate token; the required outcomes are instead to run the same retrieval, validation, and publishing stages in an approved order for every request and to pursue an open-ended investigation where the next action depends on intermediate evidence.

C:

This alternative serves the separate goal to plan another step only after inspecting the result of a requested external operation because the loop returns observations to the model so subsequent decisions are informed by actual tool output rather than imagined execution; the required outcomes are instead to run the same retrieval, validation, and publishing stages in an approved order for every request and to pursue an open-ended investigation where the next action depends on intermediate evidence.

Question 669

A production readiness review of a tool-calling Claude workflow finds that the team cannot yet prevent two similarly named lookup tools from being confused or expose a business lookup with predictable typed arguments. Which paired changes directly remedy the two gaps?

  1. Perform both steps: (1) Describe each tool's purpose, required inputs, and limitations clearly; (2) return an explicit tool error indication and an informative safe message.
  2. Perform both steps: (1) Give each tool a timeout and controlled retry or failure result; (2) define a descriptive tool name and validated input schema.
  3. Perform both steps: (1) Give each tool a timeout and controlled retry or failure result; (2) return an explicit tool error indication and an informative safe message.
  4. Perform both steps: (1) Describe each tool's purpose, required inputs, and limitations clearly; (2) define a descriptive tool name and validated input schema.

Explanation

Correct Answer

D:

The first change enables the team to prevent two similarly named lookup tools from being confused because tool descriptions influence the model's selection, so overlapping or vague names make dispatch less reliable; the second addresses the separate need to expose a business lookup with predictable typed arguments because well-described schemas help Claude select a capability and emit usable arguments; the backend still validates authorization and meaning.

Incorrect Answers

A:

The first step is appropriate for the requirement to prevent two similarly named lookup tools from being confused because tool descriptions influence the model's selection, so overlapping or vague names make dispatch less reliable; the other step instead aims to let Claude distinguish a failed database lookup from an empty successful result because an error result preserves failure semantics, preventing the model from inventing a no-record finding for a call that never succeeded, which does not meet the second requirement to expose a business lookup with predictable typed arguments.

B:

The second step meets the requirement to expose a business lookup with predictable typed arguments because well-described schemas help Claude select a capability and emit usable arguments; the backend still validates authorization and meaning; the first step would only help to stop a slow external system from trapping an agent loop indefinitely because tool execution is a separate latency source; bounded calls prevent one dependency from exhausting the entire agent budget, leaving the separate requirement to prevent two similarly named lookup tools from being confused unmet.

C:

Both steps target different results—stop a slow external system from trapping an agent loop indefinitely and let Claude distinguish a failed database lookup from an empty successful result—because tool execution is a separate latency source; bounded calls prevent one dependency from exhausting the entire agent budget and an error result preserves failure semantics, preventing the model from inventing a no-record finding for a call that never succeeded; the required capabilities are instead to prevent two similarly named lookup tools from being confused and to expose a business lookup with predictable typed arguments.

Question 670

A team maintaining a Python Claude API backend has two different engineering requirements: (1) apply consistent reviewed tool permissions to an entire Claude Code repository team, and (2) reproduce production behavior across deploys instead of silently adopting a new model release. Which TWO independent changes directly meet them? Choose TWO.

  1. Use the user's own Claude Code settings file.
  2. Pin a supported explicit model version where stability is required.
  3. Track enabled plugins and their compatible versions as release dependencies.
  4. Store team settings in the project's shared configuration file.
  5. Enforce per-tenant token and request budgets in the backend.

Explanation

Correct Answers

B:

To reproduce production behavior across deploys instead of silently adopting a new model release as part of a design that must also apply consistent reviewed tool permissions to an entire Claude Code repository team, explicit version selection limits unexpected changes; a release process should evaluate upgrades and retirement timelines deliberately; this is why the action is one of the two required selections.

D:

To apply consistent reviewed tool permissions to an entire Claude Code repository team as part of a design that must also reproduce production behavior across deploys instead of silently adopting a new model release, repository-level settings can be versioned and reviewed, unlike private preferences that vary across each developer's machine; this is why the action is one of the two required selections.

Incorrect Answers

A:

This alternative serves the separate goal to customize one developer's default Claude Code behavior across local projects because user settings are scoped to one person, so they should not be relied on for enforcing team-wide policy; the required outcomes are instead to apply consistent reviewed tool permissions to an entire Claude Code repository team and to reproduce production behavior across deploys instead of silently adopting a new model release.

C:

This alternative serves the separate goal to avoid a plugin update unexpectedly changing tools available to a coding agent because plugin capability changes can affect tool names and permissions, so production configuration should be reproducible and reviewed; the required outcomes are instead to apply consistent reviewed tool permissions to an entire Claude Code repository team and to reproduce production behavior across deploys instead of silently adopting a new model release.

E:

This alternative serves the separate goal to keep one customer from consuming an entire shared inference budget because application quotas isolate noisy tenants and control spending; provider-wide rate limits alone do not guarantee fairness between customers; the required outcomes are instead to apply consistent reviewed tool permissions to an entire Claude Code repository team and to reproduce production behavior across deploys instead of silently adopting a new model release.

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