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

Question 90

A language-model integration review requires two independent, explicitly defined outcomes: the first workstream must estimate model-token input demand before launching a large processing job; a second must implement an interactive collaboration channel requiring messages in both directions. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Use direct HTTP REST integration for unsupported runtimes
  2. Use the official SDK for standard requests
  3. Use the Messages count_tokens capability
  4. Choose WebSockets for bidirectional realtime exchange
  5. Use a queue for burst absorption

Explanation

Correct Answers

C:

Token counting helps check input budgets before generation and cost planning; this directly supports task 1 to estimate model-token input demand before launching a large processing job, not the separate task or tasks to implement an interactive collaboration channel requiring messages in both directions; word or byte count is not a reliable substitute across diverse content.

D:

Persistent two-way channels fit interactive event exchange where the client also sends messages during a session; this directly supports task 2 to implement an interactive collaboration channel requiring messages in both directions, not the separate task or tasks to estimate model-token input demand before launching a large processing job; standard response streaming alone is not a general bidirectional messaging protocol.

Incorrect Answers

A:

A standards-based HTTP client can send JSON requests with the correct headers and decode responses; this implements the different outcome to call the Messages endpoint from a language without a mature provider SDK rather than the required tasks to implement an interactive collaboration channel requiring messages in both directions and to estimate model-token input demand before launching a large processing job, and a wrapper package is optional, not the underlying API transport, so it is not a direct solution to any of the assigned workstreams.

B:

Maintained client libraries wrap the HTTP API and expose structured response objects; this implements the different outcome to simplify authentication, serialization, and response typing in a Python service rather than the required tasks to implement an interactive collaboration channel requiring messages in both directions and to estimate model-token input demand before launching a large processing job, and SDK convenience does not eliminate the need for correct retry and error handling, so it is not a direct solution to any of the assigned workstreams.

E:

Queueing decouples producers from consumer throughput and enables controlled retries; this implements the different outcome to smooth sudden ingestion spikes before workers call a capacity-limited model API rather than the required tasks to implement an interactive collaboration channel requiring messages in both directions and to estimate model-token input demand before launching a large processing job, and increasing frontend timeouts does not eliminate backend capacity limits, so it is not a direct solution to any of the assigned workstreams.

Question 91

A workflow automation application is approaching release, but the team still needs to answer questions from changing internal documentation with traceable source excerpts. What is the most appropriate implementation?

  1. Use bounded memory with explicit provenance
  2. Use a graceful fallback path
  3. Use a framework only when its primitives fit
  4. Use retrieval before generation
  5. Use a graph with conditional edges

Explanation

Correct Answer

D:

Retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current; this behavior directly supports the need to answer questions from changing internal documentation with traceable source excerpts. The retrieved text remains untrusted as instructions and needs relevance checks.

Incorrect Answers

A:

Typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; this applies to the different goal to preserve customer preferences across permitted sessions while distinguishing facts from assumptions, not the requirement to answer questions from changing internal documentation with traceable source excerpts; arbitrary model-generated memories can become a source of drift.

B:

When an application needs to keep a customer service application operating when an expensive specialist agent cannot complete, a bounded failure branch can return a safe partial result or route to a human rather than loop indefinitely; the current capability must instead answer questions from changing internal documentation with traceable source excerpts, while unbounded retries do not ensure eventual success.

C:

Frameworks can help with graphs, retries, and checkpoints but create maintenance and integration costs; the supported outcome is to select orchestration dependencies for a project that already has a stable task engine, whereas this scenario requires the ability to answer questions from changing internal documentation with traceable source excerpts; adopting a framework solely for fashionable abstraction is not a technical requirement.

E:

Conditional graph transitions encode known branches while allowing model reasoning within selected nodes; despite being useful when a service must branch between remediation and escalation based on the result of a security scan, it is not a solution to answer questions from changing internal documentation with traceable source excerpts; a linear chain cannot express result-dependent routing cleanly.

Question 92

After pilot feedback, a document processing group needs two independent improvements. The first is to detect unsafe permissions and schema changes before merging an agent tool; the second is to reproduce a working SDK installation across staging and production. Which engineering proposal handles both?

  1. First component: Use pull requests and focused code review. Second component: Pin dependencies with lockfiles.
  2. First component: Use pull requests and focused code review. Second component: Use feature flags for risky behavior changes.
  3. First component: Separate integration tests from unit tests. Second component: Pin dependencies with lockfiles.
  4. First component: Use feature flags for risky behavior changes. Second component: Separate integration tests from unit tests.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal fits its assigned role because locked versions and hashes constrain drift between build environments; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reproduce a working SDK installation across staging and production.

Incorrect Answers

B:

The first proposal fits its assigned role because peer review creates an explicit checkpoint for correctness, security, and maintainability, while the second proposal serves the different purpose to activate a new tool execution path for only internal testers instead of the assigned second role because runtime controls can segment rollout and permit quick disabling without a code rebuild; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reproduce a working SDK installation across staging and production.

C:

The first proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned first role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal fits its assigned role because locked versions and hashes constrain drift between build environments; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reproduce a working SDK installation across staging and production.

D:

The first proposal serves the different purpose to activate a new tool execution path for only internal testers instead of the assigned first role because runtime controls can segment rollout and permit quick disabling without a code rebuild, while the second proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned second role because integration tests exercise boundaries and serialization that isolated mocks may miss; their respective acceptance criteria are to detect unsafe permissions and schema changes before merging an agent tool and to reproduce a working SDK installation across staging and production.

Question 93

A data pipeline review requires two independent, explicitly defined outcomes: the first workstream must compute discounts through verified business code rather than generated arithmetic alone; a second must explain service limits or tool outages without leaking stack traces or secrets. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Separate model reasoning from authoritative calculations
  2. Treat retrieval results as untrusted data
  3. Keep user tasks in the user message
  4. Create one session per user conversation
  5. Return user-friendly error states

Explanation

Correct Answers

A:

Deterministic services can enforce exact formulas and rounding before the model explains the result; this directly supports task 1 to compute discounts through verified business code rather than generated arithmetic alone, not the separate task or tasks to explain service limits or tool outages without leaking stack traces or secrets; a plausible model narrative is not a reliable financial ledger.

E:

Structured error mapping presents actionable feedback while retaining detailed diagnostics in protected logs; this directly supports task 2 to explain service limits or tool outages without leaking stack traces or secrets, not the separate task or tasks to compute discounts through verified business code rather than generated arithmetic alone; returning a raw exception can expose internal infrastructure details.

Incorrect Answers

B:

Retrieved content should be framed as evidence, never upgraded to new tool or system authority; this implements the different outcome to prevent a malicious help article from ordering the model to reveal secrets rather than the required tasks to explain service limits or tool outages without leaking stack traces or secrets and to compute discounts through verified business code rather than generated arithmetic alone, and a trustworthy source URL does not make embedded commands authorized, so it is not a direct solution to any of the assigned workstreams.

C:

Explicit message roles distinguish requested work from higher-priority operational framing; this implements the different outcome to separate an end user's request from the developer's stable operating instructions rather than the required tasks to explain service limits or tool outages without leaking stack traces or secrets and to compute discounts through verified business code rather than generated arithmetic alone, and merging everything into one unstructured prompt weakens provenance, so it is not a direct solution to any of the assigned workstreams.

D:

Session scoping ensures history and tool results belong to the correct principal; this implements the different outcome to keep follow-up requests linked without exposing another tenant's messages rather than the required tasks to explain service limits or tool outages without leaking stack traces or secrets and to compute discounts through verified business code rather than generated arithmetic alone, and a global conversation list risks mixing private records, so it is not a direct solution to any of the assigned workstreams.

Question 94

A team maintaining an MCP interoperability needs to deny destructive filesystem operations before a coding agent executes them. Which implementation most directly satisfies the requirement?

  1. Use a deterministic workflow for fixed stages
  2. Use an autonomous agent for exploratory work
  3. Use hooks for enforceable safety checks
  4. Use system or repository instructions for stable behavior

Explanation

Correct Answer

C:

Runtime interception can apply deterministic policies to proposed actions; this behavior directly supports the need to deny destructive filesystem operations before a coding agent executes them. A skill that asks for caution does not guarantee prevention.

Incorrect Answers

A:

Explicit application control makes each transition testable and easier to audit; this applies to the different goal to automate the same classify-review-export path across predictable submissions, not the requirement to deny destructive filesystem operations before a coding agent executes them; an autonomous agent is unnecessary when the path is already fixed.

B:

When an application needs to perform open-ended troubleshooting where tool selection changes after each observation, model-directed planning supports adaptive sequences when the next action is not known in advance; the current capability must instead deny destructive filesystem operations before a coding agent executes them, while a rigid workflow struggles with unforeseen branches without extensive coding.

D:

This approach serves the separate need to make a coding or API assistant follow organization-wide conventions because instructions shape model behavior and task framing without executing external operations; it does not establish the outcome to deny destructive filesystem operations before a coding agent executes them, and descriptive rules do not replace programmatic validation or IAM.

Question 95

The owner of a language-model integration integration wants to simplify authentication, serialization, and response typing in a Python service. Which proposal provides the required mechanism?

  1. Use a queue for burst absorption
  2. Separate transport failures from model refusals
  3. Use the official SDK for standard requests
  4. Use connection pooling for repeated HTTP calls
  5. Choose SSE for one-way streamed responses

Explanation

Correct Answer

C:

Maintained client libraries wrap the HTTP API and expose structured response objects; this behavior directly supports the need to simplify authentication, serialization, and response typing in a Python service. SDK convenience does not eliminate the need for correct retry and error handling.

Incorrect Answers

A:

Queueing decouples producers from consumer throughput and enables controlled retries; this applies to the different goal to smooth sudden ingestion spikes before workers call a capacity-limited model API, not the requirement to simplify authentication, serialization, and response typing in a Python service; increasing frontend timeouts does not eliminate backend capacity limits.

B:

When an application needs to surface network timeouts differently from a completed response that declines a task, a transport error occurs before a valid application-level completion; refusals are model outcomes; the current capability must instead simplify authentication, serialization, and response typing in a Python service, while treating both as one generic retry condition can loop endlessly.

D:

This approach serves the separate need to reduce setup overhead when a service sends many short requests because reusable clients avoid unnecessary connection establishment under compatible networking conditions; it does not establish the outcome to simplify authentication, serialization, and response typing in a Python service, and creating a fresh client per request can increase latency and resource churn.

E:

Server-sent events provide ordered server-to-client updates over an HTTP stream; despite being useful when a service must deliver tokens to a browser without maintaining a bidirectional command channel, it is not a solution to simplify authentication, serialization, and response typing in a Python service; a WebSocket is not required solely to push a response as it arrives.

Question 96

The current design of an application security pipeline does not adequately stop an injected wiki page from asking an assistant to export credentials. Which improvement resolves the gap?

  1. Validate tool arguments server-side
  2. Limit external network egress for agents
  3. Use output escaping to prevent XSS
  4. Encrypt sensitive data in transit
  5. Treat tool and retrieval text as untrusted

Explanation

Correct Answer

E:

Lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; this behavior directly supports the need to stop an injected wiki page from asking an assistant to export credentials. A model can be persuaded by source text unless boundaries are enforced.

Incorrect Answers

A:

Backend authorization checks must bind the requested operation to the caller's entitlements; this applies to the different goal to block a generated database query that targets another tenant's records, not the requirement to stop an injected wiki page from asking an assistant to export credentials; well-formed arguments are not proof of permission.

B:

When an application needs to prevent a compromised tool step from sending internal files to arbitrary destinations, network policy restricts which services a tool process can contact; the current capability must instead stop an injected wiki page from asking an assistant to export credentials, while a natural-language prohibition cannot enforce packet-level isolation.

C:

Context-aware encoding prevents text from being interpreted as active HTML or JavaScript; the supported outcome is to display generated customer notes safely in a browser, whereas this scenario requires the ability to stop an injected wiki page from asking an assistant to export credentials; an instruction to the model not to write scripts is not a rendering control.

D:

This approach serves the separate need to protect payload confidentiality between the application and its API endpoint because modern transport encryption limits interception across network boundaries; it does not establish the outcome to stop an injected wiki page from asking an assistant to export credentials, and merely obfuscating a prompt is not transport security.

Question 97

A design meeting for a document processing platform concludes that two isolated services require different behavior: one must debug where a request stalls between the web UI, queue, and Claude gateway, and another must prevent bursts of document jobs from overwhelming rate limits and memory. Which arrangement meets the specification?

  1. First component: Correlate distributed traces across services. Second component: Enforce concurrency limits.
  2. First component: Correlate distributed traces across services. Second component: Keep secrets out of source control.
  3. First component: Keep secrets out of source control. Second component: Separate integration tests from unit tests.
  4. First component: Separate integration tests from unit tests. Second component: Enforce concurrency limits.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because a trace identifier links timing and errors through multiple process boundaries, while the second proposal fits its assigned role because a semaphore or bounded queue keeps in-flight work within measured capacity; their respective acceptance criteria are to debug where a request stalls between the web UI, queue, and Claude gateway and to prevent bursts of document jobs from overwhelming rate limits and memory.

Incorrect Answers

B:

The first proposal fits its assigned role because a trace identifier links timing and errors through multiple process boundaries, while the second proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned second role because secret stores or environment injection keep production tokens out of committed code; their respective acceptance criteria are to debug where a request stalls between the web UI, queue, and Claude gateway and to prevent bursts of document jobs from overwhelming rate limits and memory.

C:

The first proposal serves the different purpose to prevent API credentials from being exposed through shared repository history instead of the assigned first role because secret stores or environment injection keep production tokens out of committed code, while the second proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned second role because integration tests exercise boundaries and serialization that isolated mocks may miss; their respective acceptance criteria are to debug where a request stalls between the web UI, queue, and Claude gateway and to prevent bursts of document jobs from overwhelming rate limits and memory.

D:

The first proposal serves the different purpose to verify that a real staging tool and its API contract work together instead of the assigned first role because integration tests exercise boundaries and serialization that isolated mocks may miss, while the second proposal fits its assigned role because a semaphore or bounded queue keeps in-flight work within measured capacity; their respective acceptance criteria are to debug where a request stalls between the web UI, queue, and Claude gateway and to prevent bursts of document jobs from overwhelming rate limits and memory.

Question 98

After pilot feedback, a customer platform group needs two independent improvements. The first is to ensure protected records are processed only in approved jurisdictions; the second is to build an intake service that accepts scanned documents as well as typed text. Which engineering proposal handles both?

  1. First component: Identify authoritative source systems. Second component: Define input modalities and size bounds.
  2. First component: Set an explicit data residency constraint. Second component: Define input modalities and size bounds.
  3. First component: Set an explicit data residency constraint. Second component: Classify data sensitivity up front.
  4. First component: Classify data sensitivity up front. Second component: Identify authoritative source systems.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because documented residency requirements inform cloud placement, logging, storage, and vendor selection, while the second proposal fits its assigned role because format, resolution, size, and throughput requirements determine preprocessing and model-call strategy; their respective acceptance criteria are to ensure protected records are processed only in approved jurisdictions and to build an intake service that accepts scanned documents as well as typed text.

Incorrect Answers

A:

The first proposal serves the different purpose to prevent a Claude assistant from inventing account balances when it lacks current ledger data instead of the assigned first role because source-of-truth mapping identifies which verified systems must supply facts and what freshness guarantees apply, while the second proposal fits its assigned role because format, resolution, size, and throughput requirements determine preprocessing and model-call strategy; their respective acceptance criteria are to ensure protected records are processed only in approved jurisdictions and to build an intake service that accepts scanned documents as well as typed text.

C:

The first proposal fits its assigned role because documented residency requirements inform cloud placement, logging, storage, and vendor selection, while the second proposal serves the different purpose to decide which customer fields must be redacted before model requests instead of the assigned second role because data classification guides minimization, access controls, retention, and acceptable transfers; their respective acceptance criteria are to ensure protected records are processed only in approved jurisdictions and to build an intake service that accepts scanned documents as well as typed text.

D:

The first proposal serves the different purpose to decide which customer fields must be redacted before model requests instead of the assigned first role because data classification guides minimization, access controls, retention, and acceptable transfers, while the second proposal serves the different purpose to prevent a Claude assistant from inventing account balances when it lacks current ledger data instead of the assigned second role because source-of-truth mapping identifies which verified systems must supply facts and what freshness guarantees apply; their respective acceptance criteria are to ensure protected records are processed only in approved jurisdictions and to build an intake service that accepts scanned documents as well as typed text.

Question 99

A privacy controls application is approaching release, but the team still needs to prevent a tool action from proceeding when its authorization service is unreachable. What is the most appropriate implementation?

  1. Use a post-tool hook to record outcomes
  2. Use a pre-tool hook to deny dangerous commands
  3. Fail closed when a required safety hook fails
  4. Keep hook scripts under change control

Explanation

Correct Answer

C:

A fail-closed gate treats missing approval as denial for sensitive operations; this behavior directly supports the need to prevent a tool action from proceeding when its authorization service is unreachable. Fail-open behavior favors availability at the expense of an important security boundary.

Incorrect Answers

A:

Post-execution events are useful for audit, metrics, and follow-up checks once the tool has run; the supported outcome is to capture which files an approved agent operation actually modified, whereas this scenario requires the ability to prevent a tool action from proceeding when its authorization service is unreachable; they cannot serve as the only prevention mechanism for an irreversible action.

B:

This approach serves the separate need to stop a coding agent from running a destructive deployment command before execution because pre-execution interception provides a deterministic opportunity to reject a proposed tool call; it does not establish the outcome to prevent a tool action from proceeding when its authorization service is unreachable, and auditing the outcome afterward cannot undo the command.

D:

For the alternate objective to prevent an unnoticed local edit from disabling a team's protection of secret files, versioning and review make guardrail behavior inspectable and reproducible; the feature here must prevent a tool action from proceeding when its authorization service is unreachable, and unreviewed workstation-local scripts can drift across developers.

Question 100

A document processing review requires two independent, explicitly defined outcomes: the first workstream must give Claude Code the project's build, test, and architecture conventions; a second must rotate production credentials without committing new source code. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Use settings.json for Claude Code permissions
  2. Store API keys in managed secret storage
  3. Put repository guidance in CLAUDE.md
  4. Validate configuration at startup
  5. Keep environment-specific settings external

Explanation

Correct Answers

B:

Central secret management supports scoped access, auditing, and key rotation; this directly supports task 2 to rotate production credentials without committing new source code, not the separate task or tasks to give Claude Code the project's build, test, and architecture conventions; a plain-text config checked into a repository is an inappropriate credential store.

C:

Repository memory files provide persistent instructional context to coding sessions; this directly supports task 1 to give Claude Code the project's build, test, and architecture conventions, not the separate task or tasks to rotate production credentials without committing new source code; they are not an application secrets manager or the API's global system prompt.

Incorrect Answers

A:

Permission settings define configurable controls for Claude Code rather than merely describing preferences; this implements the different outcome to constrain a repository coding assistant's allowed tools and execution behavior rather than the required tasks to give Claude Code the project's build, test, and architecture conventions and to rotate production credentials without committing new source code, and a CLAUDE.md comment cannot be relied on as a hard execution gate, so it is not a direct solution to any of the assigned workstreams.

D:

Startup checks surface missing required values before user traffic reaches a broken path; this implements the different outcome to fail fast if a model ID or tool endpoint is absent in production rather than the required tasks to give Claude Code the project's build, test, and architecture conventions and to rotate production credentials without committing new source code, and a late runtime exception spreads one configuration defect across many requests, so it is not a direct solution to any of the assigned workstreams.

E:

Configuration injection separates environment differences from immutable application artifacts; this implements the different outcome to deploy the same application build to staging and production with distinct endpoints rather than the required tasks to give Claude Code the project's build, test, and architecture conventions and to rotate production credentials without committing new source code, and hard-coded URLs require risky code changes for promotion, so it is not a direct solution to any of the assigned workstreams.

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