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

Question 740

An architecture decision for a TypeScript Claude integration must support preserve an understandable outcome when model generation cannot complete and enable an administrator to determine how a particular AI decision was produced. Which option gives a complete rather than partial solution?

  1. Perform both steps: (1) Version tool input schemas and coordinate dependent client changes; (2) require structured request ids, tool traces, and version metadata with privacy controls.
  2. Perform both steps: (1) Specify user-visible degraded responses and recovery paths; (2) require structured request ids, tool traces, and version metadata with privacy controls.
  3. Perform both steps: (1) Version tool input schemas and coordinate dependent client changes; (2) apply content checks at suitable input and output boundaries.
  4. Perform both steps: (1) Specify user-visible degraded responses and recovery paths; (2) apply content checks at suitable input and output boundaries.

Explanation

Correct Answer

B:

The first change enables the team to preserve an understandable outcome when model generation cannot complete because a fallback requirement defines what customers see when an API call times out or is refused rather than assuming every inference will succeed; the second addresses the separate need 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.

Incorrect Answers

A:

The second step meets the requirement 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 first step would only help to migrate tool argument fields without breaking older workers because contract versioning prevents producers and consumers from silently disagreeing about required fields or meanings, leaving the separate requirement to preserve an understandable outcome when model generation cannot complete unmet.

C:

Both steps target different results—migrate tool argument fields without breaking older workers and filter risky user-visible content according to application policy—because contract versioning prevents producers and consumers from silently disagreeing about required fields or meanings and moderation is a defense layer applied around generation, not a substitute for authenticated tool access or scoped retrieval; the required capabilities are instead to preserve an understandable outcome when model generation cannot complete and to enable an administrator to determine how a particular AI decision was produced.

D:

The first step is appropriate for the requirement to preserve an understandable outcome when model generation cannot complete because a fallback requirement defines what customers see when an API call times out or is refused rather than assuming every inference will succeed; the other step instead aims 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, which does not meet the second requirement to enable an administrator to determine how a particular AI decision was produced.

Question 741

An end-to-end test for a multi-tenant support application checks whether it can avoid assuming a structured SDK response is a plain string and recover when a response ends because its generation budget was reached. Which plan should be approved to satisfy both checks?

  1. Perform both steps: (1) Inspect response.content blocks and metadata through the SDK's typed representation; (2) configure the max_tokens request parameter appropriately.
  2. Perform both steps: (1) Detect transport interruption and mark incomplete generated content; (2) configure the max_tokens request parameter appropriately.
  3. Perform both steps: (1) Detect transport interruption and mark incomplete generated content; (2) handle stop_reason max_tokens as truncation and continue or revise the limit.
  4. Perform both steps: (1) Inspect response.content blocks and metadata through the SDK's typed representation; (2) handle stop_reason max_tokens as truncation and continue or revise the limit.

Explanation

Correct Answer

D:

The first change enables the team to avoid assuming a structured SDK response is a plain string because the SDK exposes block types, stop reason, and usage separately; naïve string concatenation can lose tool requests or other content; the second addresses the separate need to recover when a response ends because its generation budget was reached because a truncated completion may contain unfinished content, so treating it as a validated final answer risks losing required fields.

Incorrect Answers

A:

The first step is appropriate for the requirement to avoid assuming a structured SDK response is a plain string because the SDK exposes block types, stop reason, and usage separately; naïve string concatenation can lose tool requests or other content; the other step instead aims to cap the maximum output generated by a Messages API request because a generation limit controls maximum output length, not total cost or correctness; too low a value can truncate useful answers, which does not meet the second requirement to recover when a response ends because its generation budget was reached.

B:

Both steps target different results—avoid silently treating a broken streaming connection as a complete answer and cap the maximum output generated by a Messages API request—because network termination before a final message event can leave a partial response, which needs explicit recovery rather than success handling and a generation limit controls maximum output length, not total cost or correctness; too low a value can truncate useful answers; the required capabilities are instead to avoid assuming a structured SDK response is a plain string and to recover when a response ends because its generation budget was reached.

C:

The second step meets the requirement to recover when a response ends because its generation budget was reached because a truncated completion may contain unfinished content, so treating it as a validated final answer risks losing required fields; the first step would only help to avoid silently treating a broken streaming connection as a complete answer because network termination before a final message event can leave a partial response, which needs explicit recovery rather than success handling, leaving the separate requirement to avoid assuming a structured SDK response is a plain string unmet.

Question 742

A release check on a Python Claude API backend found two unsatisfied conditions: the service must map out-of-order batch outputs back to source records reliably, and it must process a large queue of independent, noninteractive requests at a lower-cost asynchronous pace. Which complete engineering plan satisfies both?

  1. Perform both steps: (1) Treat stop_reason end_turn as a completed assistant turn; (2) use stop_sequences and inspect the returned stop_sequence field.
  2. Perform both steps: (1) Assign and preserve unique custom identifiers for batched requests; (2) submit independent requests through the message batches api.
  3. Perform both steps: (1) Treat stop_reason end_turn as a completed assistant turn; (2) submit independent requests through the message batches api.
  4. Perform both steps: (1) Assign and preserve unique custom identifiers for batched requests; (2) use stop_sequences and inspect the returned stop_sequence field.

Explanation

Correct Answer

B:

The first change enables the team to map out-of-order batch outputs back to source records reliably because asynchronous results need stable correlation keys; relying on processing order can attach an output to the wrong input; the second addresses the separate need to process a large queue of independent, noninteractive requests at a lower-cost asynchronous pace because batch processing is suited to deferred work with eventual result collection and is not a substitute for an interactive low-latency chat endpoint.

Incorrect Answers

A:

Both steps target different results—detect that the assistant has naturally finished a response and enforce a caller-defined textual boundary on generation—because the completion signal is explicit in the response metadata; it should not be inferred solely from a sentence ending in punctuation and a stop sequence halts generation at a specified marker, distinct from natural completion and separate from a JSON schema validator; the required capabilities are instead to map out-of-order batch outputs back to source records reliably and to process a large queue of independent, noninteractive requests at a lower-cost asynchronous pace.

C:

The second step meets the requirement to process a large queue of independent, noninteractive requests at a lower-cost asynchronous pace because batch processing is suited to deferred work with eventual result collection and is not a substitute for an interactive low-latency chat endpoint; the first step would only help to detect that the assistant has naturally finished a response because the completion signal is explicit in the response metadata; it should not be inferred solely from a sentence ending in punctuation, leaving the separate requirement to map out-of-order batch outputs back to source records reliably unmet.

D:

The first step is appropriate for the requirement to map out-of-order batch outputs back to source records reliably because asynchronous results need stable correlation keys; relying on processing order can attach an output to the wrong input; the other step instead aims to enforce a caller-defined textual boundary on generation because a stop sequence halts generation at a specified marker, distinct from natural completion and separate from a JSON schema validator, which does not meet the second requirement to process a large queue of independent, noninteractive requests at a lower-cost asynchronous pace.

Question 743

While planning a customer-facing AI feature, the product owner specifies that it must prevent a document-upload endpoint from passing unsupported bytes to the model. Which solution fulfills the requirement?

  1. Validate file type, size, and allowed content conversion before API submission.
  2. Persist explicit job states with allowed transitions.
  3. Configure supported structured outputs with a JSON Schema.
  4. Apply a context retention policy and summarize earlier turns where suitable.

Explanation

Correct Answer

A:

To prevent a document-upload endpoint from passing unsupported bytes to the model in this customer-facing AI feature, client filenames are not enough to establish content validity; ingestion must enforce protocol and product constraints; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

The proposed alternative helps to distinguish queued, running, waiting-for-approval, failed, and completed agent jobs because a state machine prevents an incomplete tool operation from being shown as successful and makes retries and cancellation predictable; that mechanism does not meet the different requirement to prevent a document-upload endpoint from passing unsupported bytes to the model.

C:

The proposed alternative helps 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; that mechanism does not meet the different requirement to prevent a document-upload endpoint from passing unsupported bytes to the model.

D:

The proposed alternative helps to stay within input limits while keeping the most important conversation constraints because selective history management preserves task-critical state; dropping random leading messages can erase consent or requirements; that mechanism does not meet the different requirement to prevent a document-upload endpoint from passing unsupported bytes to the model.

Question 744

Two acceptance tests block a production inference application: one requires the ability to apply consistent reviewed tool permissions to an entire Claude Code repository team; the other requires the ability to customize one developer's default Claude Code behavior across local projects. Which plan clears both tests?

  1. Perform both steps: (1) Release to a small monitored cohort before broad deployment; (2) assemble messages with correct user and assistant roles.
  2. Perform both steps: (1) Store team settings in the project's shared configuration file; (2) assemble messages with correct user and assistant roles.
  3. Perform both steps: (1) Release to a small monitored cohort before broad deployment; (2) use the user's own claude code settings file.
  4. Perform both steps: (1) Store team settings in the project's shared configuration file; (2) use the user's own claude code settings file.

Explanation

Correct Answer

D:

The first change enables the team to apply consistent reviewed tool permissions to an entire Claude Code repository team because repository-level settings can be versioned and reviewed, unlike private preferences that vary across each developer's machine; the second addresses the separate need 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.

Incorrect Answers

A:

Both steps target different results—limit the blast radius of a new model configuration during rollout and distinguish an end user's request from previous assistant turns in a dialogue—because canary exposure provides real traffic signals with an option to stop or roll back, unlike a simultaneous change for every customer and conversation structure influences how the model interprets dialogue and tool history; flattening roles into one text string loses that structure; the required capabilities are instead to apply consistent reviewed tool permissions to an entire Claude Code repository team and to customize one developer's default Claude Code behavior across local projects.

B:

The first step is appropriate for the requirement to apply consistent reviewed tool permissions to an entire Claude Code repository team because repository-level settings can be versioned and reviewed, unlike private preferences that vary across each developer's machine; the other step instead aims to distinguish an end user's request from previous assistant turns in a dialogue because conversation structure influences how the model interprets dialogue and tool history; flattening roles into one text string loses that structure, which does not meet the second requirement to customize one developer's default Claude Code behavior across local projects.

C:

The second step meets the requirement 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 first step would only help to limit the blast radius of a new model configuration during rollout because canary exposure provides real traffic signals with an option to stop or roll back, unlike a simultaneous change for every customer, leaving the separate requirement to apply consistent reviewed tool permissions to an entire Claude Code repository team unmet.

Question 745

The technical owner of a business workflow that calls Claude has to distinguish an end user's request from previous assistant turns in a dialogue. A separate requirement is to cap the maximum output generated by a Messages API request. Which two-part remediation covers both?

  1. Perform both steps: (1) Assemble messages with correct user and assistant roles; (2) send instructions using the request's top-level system field.
  2. Perform both steps: (1) Parse response content by block type and follow current thinking-field rules; (2) send instructions using the request's top-level system field.
  3. Perform both steps: (1) Assemble messages with correct user and assistant roles; (2) configure the max_tokens request parameter appropriately.
  4. Perform both steps: (1) Parse response content by block type and follow current thinking-field rules; (2) configure the max_tokens request parameter appropriately.

Explanation

Correct Answer

C:

The first change enables the team to distinguish an end user's request from previous assistant turns in a dialogue because conversation structure influences how the model interprets dialogue and tool history; flattening roles into one text string loses that structure; the second addresses the separate need to cap the maximum output generated by a Messages API request because a generation limit controls maximum output length, not total cost or correctness; too low a value can truncate useful answers.

Incorrect Answers

A:

The first step is appropriate for the requirement to distinguish an end user's request from previous assistant turns in a dialogue because conversation structure influences how the model interprets dialogue and tool history; flattening roles into one text string loses that structure; the other step instead aims to set consistent developer-controlled behavior separately from untrusted user text because the system field separates higher-priority application guidance from user-message content and should not be simulated by ordinary quoted text, which does not meet the second requirement to cap the maximum output generated by a Messages API request.

B:

Both steps target different results—handle a response containing reasoning-related blocks without confusing them with ordinary final text and set consistent developer-controlled behavior separately from untrusted user text—because structured content may contain distinct block types and signatures; a parser that assumes only plain text can discard important protocol data and the system field separates higher-priority application guidance from user-message content and should not be simulated by ordinary quoted text; the required capabilities are instead to distinguish an end user's request from previous assistant turns in a dialogue and to cap the maximum output generated by a Messages API request.

D:

The second step meets the requirement to cap the maximum output generated by a Messages API request because a generation limit controls maximum output length, not total cost or correctness; too low a value can truncate useful answers; the first step would only help to handle a response containing reasoning-related blocks without confusing them with ordinary final text because structured content may contain distinct block types and signatures; a parser that assumes only plain text can discard important protocol data, leaving the separate requirement to distinguish an end user's request from previous assistant turns in a dialogue unmet.

Question 746

A test for a high-volume Messages API gateway fails because it cannot detect a changed tool response field before it breaks downstream code. Which change fixes the identified failure?

  1. Use the user's own Claude Code settings file.
  2. Place a valid secret in the documented API authentication header.
  3. Supply the required API version header.
  4. Add automated consumer-provider contract tests.

Explanation

Correct Answer

D:

To detect a changed tool response field before it breaks downstream code in this high-volume Messages API gateway, schema contracts make integration changes visible and prevent a renamed field from silently corrupting later model context; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps 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; that mechanism does not meet the different requirement to detect a changed tool response field before it breaks downstream code.

B:

The proposed alternative helps to authenticate a server-to-server Claude API request because API authentication is a request transport concern; placing a key inside the prompt body neither authenticates the request nor protects it; that mechanism does not meet the different requirement to detect a changed tool response field before it breaks downstream code.

C:

The proposed alternative helps to make a direct REST request with a declared supported API contract because the version header selects the protocol contract supported by the endpoint, preventing accidental dependence on unspecified behavior; that mechanism does not meet the different requirement to detect a changed tool response field before it breaks downstream code.

Question 747

A production readiness review of a hosted document-processing service finds that the team cannot yet compare candidate models before switching a mission-critical endpoint or customize one developer's default Claude Code behavior across local projects. Which paired changes directly remedy the two gaps?

  1. Perform both steps: (1) Treat model migration as a tested deployment with staged traffic; (2) use the user's own claude code settings file.
  2. Perform both steps: (1) Treat model migration as a tested deployment with staged traffic; (2) use the provider-specific endpoint, authentication, and request conventions.
  3. Perform both steps: (1) Keep versioned artifacts and a tested rollback procedure; (2) use the user's own claude code settings file.
  4. Perform both steps: (1) Keep versioned artifacts and a tested rollback procedure; (2) use the provider-specific endpoint, authentication, and request conventions.

Explanation

Correct Answer

A:

The first change enables the team to compare candidate models before switching a mission-critical endpoint because model upgrades may alter output distributions or supported features; staged validation reduces the chance of an unnoticed behavior shift; the second addresses the separate need 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.

Incorrect Answers

B:

The first step is appropriate for the requirement to compare candidate models before switching a mission-critical endpoint because model upgrades may alter output distributions or supported features; staged validation reduces the chance of an unnoticed behavior shift; the other step instead aims to support Claude models accessed through different supported cloud offerings because Claude API, Bedrock, and Vertex-style integrations are not interchangeable URLs; host authentication and service wrappers differ, which does not meet the second requirement to customize one developer's default Claude Code behavior across local projects.

C:

The second step meets the requirement 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 first step would only help to restore a known-working prompt and model configuration after quality degrades because model IDs, prompts, schemas, and tool contracts are release components; restoring just the application binary may not restore prior behavior, leaving the separate requirement to compare candidate models before switching a mission-critical endpoint unmet.

D:

Both steps target different results—restore a known-working prompt and model configuration after quality degrades and support Claude models accessed through different supported cloud offerings—because model IDs, prompts, schemas, and tool contracts are release components; restoring just the application binary may not restore prior behavior and Claude API, Bedrock, and Vertex-style integrations are not interchangeable URLs; host authentication and service wrappers differ; the required capabilities are instead to compare candidate models before switching a mission-critical endpoint and to customize one developer's default Claude Code behavior across local projects.

Question 748

To ship a TypeScript Claude integration, the application must shield customer traffic when inference capacity is exhausted and keep one customer from consuming an entire shared inference budget. Which pair of listed actions is necessary for those stated capabilities? Choose TWO.

  1. Delimit retrieved text as untrusted source material.
  2. Queue or reject excess requests using bounded admission control.
  3. Store and retrieve message history by authenticated tenant and conversation ID.
  4. Enforce per-tenant token and request budgets in the backend.
  5. Validate file type, size, and allowed content conversion before API submission.

Explanation

Correct Answers

B:

To shield customer traffic when inference capacity is exhausted as part of a design that must also keep one customer from consuming an entire shared inference budget, controlled queuing protects system latency and prevents unbounded retries from overwhelming downstream provider quotas; this is why the action is one of the two required selections.

D:

To keep one customer from consuming an entire shared inference budget as part of a design that must also shield customer traffic when inference capacity is exhausted, application quotas isolate noisy tenants and control spending; provider-wide rate limits alone do not guarantee fairness between customers; this is why the action is one of the two required selections.

Incorrect Answers

A:

This alternative serves the separate goal to prevent a retrieved article's embedded commands from being treated as developer instructions because explicit trust boundaries help the model interpret documents as evidence rather than operational orders, and runtime controls must enforce privileged actions; the required outcomes are instead to shield customer traffic when inference capacity is exhausted and to keep one customer from consuming an entire shared inference budget.

C:

This alternative serves the separate goal to prevent chat transcripts from different accounts entering the same Claude request because session hygiene requires server-enforced isolation; model instructions cannot repair a history assembled from the wrong user; the required outcomes are instead to shield customer traffic when inference capacity is exhausted and to keep one customer from consuming an entire shared inference budget.

E:

This alternative serves the separate goal to prevent a document-upload endpoint from passing unsupported bytes to the model because client filenames are not enough to establish content validity; ingestion must enforce protocol and product constraints; the required outcomes are instead to shield customer traffic when inference capacity is exhausted and to keep one customer from consuming an entire shared inference budget.

Question 749

A planned upgrade to a multi-tenant support application has two requirements that must both pass: expose external business tools only to workflows that actually need them; prevent chat transcripts from different accounts entering the same Claude request. Identify the two direct implementations. Choose TWO.

  1. Add application-owned approval logic around the refund tool.
  2. Store and retrieve message history by authenticated tenant and conversation ID.
  3. Enable required plugin or connector capabilities using least-privilege configuration.
  4. Buffer structured data until it can be parsed and validated before UI commit.
  5. Use strict tool input validation for the exposed tool interface.

Explanation

Correct Answers

B:

To prevent chat transcripts from different accounts entering the same Claude request as part of a design that must also expose external business tools only to workflows that actually need them, session hygiene requires server-enforced isolation; model instructions cannot repair a history assembled from the wrong user; this is why the action is one of the two required selections.

C:

To expose external business tools only to workflows that actually need them as part of a design that must also prevent chat transcripts from different accounts entering the same Claude request, tools expand the application's action surface; indiscriminate activation increases risk and can confuse model selection among similar functions; this is why the action is one of the two required selections.

Incorrect Answers

A:

This alternative serves the separate goal to ensure refunds above a policy limit receive human sign-off because decisions that create financial side effects require deterministic authorization checks beyond a model's recommendation; the required outcomes are instead to expose external business tools only to workflows that actually need them and to prevent chat transcripts from different accounts entering the same Claude request.

D:

This alternative serves the separate goal to display partial sentences without publishing malformed structured records because a text stream can arrive in fragments; consumers must distinguish presentation updates from complete machine-readable objects; the required outcomes are instead to expose external business tools only to workflows that actually need them and to prevent chat transcripts from different accounts entering the same Claude request.

E:

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 expose external business tools only to workflows that actually need them and to prevent chat transcripts from different accounts entering the same Claude request.

Question 750

In a Python Claude API backend, a release requirement is to reuse a long stable instruction or document prefix over repeated requests. Which implementation addresses that specific requirement?

  1. Assign and preserve unique custom identifiers for batched requests.
  2. Read the completed stream's usage and final message metadata.
  3. Cache an eligible unchanged prefix with cache_control.
  4. Inspect changes to content and ordering before the cache breakpoint.

Explanation

Correct Answer

C:

To reuse a long stable instruction or document prefix over repeated requests in this Python Claude API backend, prompt caching reduces repeated input processing when the prefix matches; changes before the cache boundary can prevent a hit; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to map out-of-order batch outputs back to source records reliably because asynchronous results need stable correlation keys; relying on processing order can attach an output to the wrong input; that mechanism does not meet the different requirement to reuse a long stable instruction or document prefix over repeated requests.

B:

The proposed alternative helps to account accurately for token consumption when a response is streamed because early text deltas do not necessarily carry authoritative final usage or stop information; accounting must wait for the appropriate terminal event; that mechanism does not meet the different requirement to reuse a long stable instruction or document prefix over repeated requests.

D:

The proposed alternative helps to explain why a previously cached prompt is now charged as new input because cache reuse depends on matching prefix material; adding text to the front changes what is cached even if later text is unchanged; that mechanism does not meet the different requirement to reuse a long stable instruction or document prefix over repeated requests.

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