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

Question 320

A test for an incident involving failed Claude completions fails because it cannot find a request schema error instead of repeatedly changing the system prompt. Which change fixes the identified failure?

  1. Examine correlated request, tool, and transformation traces stage by stage.
  2. Trace the API credential and access permissions for the 401 or 403 response.
  3. Read the 400 error details and validate the request payload.
  4. Inspect stop_reason and output limits before changing the parser.

Explanation

Correct Answer

C:

To find a request schema error instead of repeatedly changing the system prompt in this incident involving failed Claude completions, an invalid API field or incompatible parameter cannot be fixed by natural-language instructions within the malformed request; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to locate which component of a multi-tool answer introduced the wrong value because structured traces reveal whether retrieval, tool execution, postprocessing, or generation caused the defect; reading only the final text cannot isolate it; that mechanism does not meet the different requirement to find a request schema error instead of repeatedly changing the system prompt.

B:

The proposed alternative helps to identify why a request is rejected before any inference happens because unauthorized access fails at the transport or authorization boundary, not because Claude misunderstood the prompt; that mechanism does not meet the different requirement to find a request schema error instead of repeatedly changing the system prompt.

D:

The proposed alternative helps to find why a JSON record unexpectedly ends midway through a field because a max_tokens stop indicates incomplete generation; the parser may be working correctly against a response that was never finished; that mechanism does not meet the different requirement to find a request schema error instead of repeatedly changing the system prompt.

Question 321

An architecture review of a business workflow that calls Claude asks how to keep one customer from consuming an entire shared inference budget. Which action is the best fit?

  1. Enforce per-tenant token and request budgets in the backend.
  2. Apply a context retention policy and summarize earlier turns where suitable.
  3. Configure supported structured outputs with a JSON Schema.
  4. Persist explicit job states with allowed transitions.

Explanation

Correct Answer

A:

To keep one customer from consuming an entire shared inference budget in this business workflow that calls Claude, application quotas isolate noisy tenants and control spending; provider-wide rate limits alone do not guarantee fairness between customers; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

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 keep one customer from consuming an entire shared inference budget.

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 keep one customer from consuming an entire shared inference budget.

D:

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 keep one customer from consuming an entire shared inference budget.

Question 322

Two acceptance tests block an enterprise MCP client: one requires the ability to help a client learn which callable and informational capabilities a server offers; the other requires the ability to expose an MCP server to clients across a network boundary. Which plan clears both tests?

  1. Perform both steps: (1) Implement the appropriate MCP capability listing and metadata endpoints; (2) configure a supported remote http transport with authentication and deployment controls.
  2. Perform both steps: (1) Implement the appropriate MCP capability listing and metadata endpoints; (2) implement a client-side handler and return its result with the tool-use identifier.
  3. Perform both steps: (1) Return an explicit tool error indication and an informative safe message; (2) configure a supported remote http transport with authentication and deployment controls.
  4. Perform both steps: (1) Return an explicit tool error indication and an informative safe message; (2) implement a client-side handler and return its result with the tool-use identifier.

Explanation

Correct Answer

A:

The first change enables the team to help a client learn which callable and informational capabilities a server offers because discovery advertises tools, resources, or prompts so clients can use supported contracts rather than guessing names or arguments; the second addresses the separate need to expose an MCP server to clients across a network boundary because remote connectivity needs network routing, identity, and authorization; a local stdio subprocess is not a remotely reachable service.

Incorrect Answers

B:

The first step is appropriate for the requirement to help a client learn which callable and informational capabilities a server offers because discovery advertises tools, resources, or prompts so clients can use supported contracts rather than guessing names or arguments; the other step instead aims to connect a Claude tool request to an internal service whose logic the application owns because a declared client tool does not execute itself; application code runs it and feeds results back into the conversation, which does not meet the second requirement to expose an MCP server to clients across a network boundary.

C:

The second step meets the requirement to expose an MCP server to clients across a network boundary because remote connectivity needs network routing, identity, and authorization; a local stdio subprocess is not a remotely reachable service; the first step would only help 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, leaving the separate requirement to help a client learn which callable and informational capabilities a server offers unmet.

D:

Both steps target different results—let Claude distinguish a failed database lookup from an empty successful result and connect a Claude tool request to an internal service whose logic the application owns—because an error result preserves failure semantics, preventing the model from inventing a no-record finding for a call that never succeeded and a declared client tool does not execute itself; application code runs it and feeds results back into the conversation; the required capabilities are instead to help a client learn which callable and informational capabilities a server offers and to expose an MCP server to clients across a network boundary.

Question 323

A planned upgrade to a Claude integration debugging session has two requirements that must both pass: find why a JSON record unexpectedly ends midway through a field; identify why a request is rejected before any inference happens. Identify the two direct implementations. Choose TWO.

  1. Inspect the HTTP 429 status and rate-limit metadata before retrying.
  2. Read the 400 error details and validate the request payload.
  3. Trace the API credential and access permissions for the 401 or 403 response.
  4. Inspect stop_reason and output limits before changing the parser.
  5. Check that each tool_use identifier receives one matching tool_result.

Explanation

Correct Answers

C:

To identify why a request is rejected before any inference happens as part of a design that must also find why a JSON record unexpectedly ends midway through a field, unauthorized access fails at the transport or authorization boundary, not because Claude misunderstood the prompt; this is why the action is one of the two required selections.

D:

To find why a JSON record unexpectedly ends midway through a field as part of a design that must also identify why a request is rejected before any inference happens, a max_tokens stop indicates incomplete generation; the parser may be working correctly against a response that was never finished; this is why the action is one of the two required selections.

Incorrect Answers

A:

This alternative serves the separate goal to distinguish an upstream throttling response from a malformed model answer because a rate limit is a request-layer capacity problem; the response needs controlled pacing rather than a prompt rewrite; the required outcomes are instead to find why a JSON record unexpectedly ends midway through a field and to identify why a request is rejected before any inference happens.

B:

This alternative serves the separate goal to find a request schema error instead of repeatedly changing the system prompt because an invalid API field or incompatible parameter cannot be fixed by natural-language instructions within the malformed request; the required outcomes are instead to find why a JSON record unexpectedly ends midway through a field and to identify why a request is rejected before any inference happens.

E:

This alternative serves the separate goal to explain why an agent loop is stuck after a model requested an external function because an unmatched tool call leaves a protocol-level continuation gap, even if the handler actually ran successfully; the required outcomes are instead to find why a JSON record unexpectedly ends midway through a field and to identify why a request is rejected before any inference happens.

Question 324

In a Claude inference cost review, a release requirement is to implement a low-volume command-line utility that handles one inference at a time. Which implementation addresses that specific requirement?

  1. Use a WebSocket protocol only when the target endpoint actually offers one.
  2. Call the documented HTTPS endpoint with explicit headers and JSON serialization.
  3. Use a synchronous client with explicit timeout and error handling.
  4. Benchmark a suitable Haiku-family model for the simple task.

Explanation

Correct Answer

C:

To implement a low-volume command-line utility that handles one inference at a time in this Claude inference cost review, synchronous calls are simplest for strictly sequential work, where concurrency would add complexity without improving throughput; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to build bidirectional persistent event communication where the chosen platform supports it because webSockets can carry two-way events over a long-lived connection; they are not a drop-in replacement for every HTTP or SSE endpoint; that mechanism does not meet the different requirement to implement a low-volume command-line utility that handles one inference at a time.

B:

The proposed alternative helps to work in an environment that lacks a compatible Claude SDK because direct REST access remains possible when an SDK is unavailable, but the caller owns wire-format correctness and response parsing; that mechanism does not meet the different requirement to implement a low-volume command-line utility that handles one inference at a time.

D:

The proposed alternative helps to serve high-volume straightforward classification at a tight latency and cost target because lightweight model tiers can favor speed and unit economics, but accuracy must still meet the specific evaluation threshold; that mechanism does not meet the different requirement to implement a low-volume command-line utility that handles one inference at a time.

Question 325

An architecture decision for a production tool-calling agent must support pinpoint which known workflow stage failed when the final artifact is incomplete and send distinct request types to specialized handlers while keeping the routing rule inspectable. Which option gives a complete rather than partial solution?

  1. Perform both steps: (1) Chain dependent operations serially with explicit input and output contracts; (2) classify the request and dispatch to an appropriate specialized workflow.
  2. Perform both steps: (1) Record stage-level traces and intermediate validation outcomes; (2) classify the request and dispatch to an appropriate specialized workflow.
  3. Perform both steps: (1) Chain dependent operations serially with explicit input and output contracts; (2) define structured inputs, expected outputs, and failure states for each delegate.
  4. Perform both steps: (1) Record stage-level traces and intermediate validation outcomes; (2) define structured inputs, expected outputs, and failure states for each delegate.

Explanation

Correct Answer

B:

The first change enables the team to pinpoint which known workflow stage failed when the final artifact is incomplete because deterministic stages are operationally useful when their boundaries are observable; a final answer alone cannot reveal which step produced the fault; the second addresses the separate need to send distinct request types to specialized handlers while keeping the routing rule inspectable because routing separates distinct pathways without making the entire task autonomously planned; the classification decision must be observable and tested.

Incorrect Answers

A:

The second step meets the requirement to send distinct request types to specialized handlers while keeping the routing rule inspectable because routing separates distinct pathways without making the entire task autonomously planned; the classification decision must be observable and tested; the first step would only help to ensure each later tool receives a validated artifact from its preceding stage because later steps cannot safely start until upstream data exists; passing validated outputs prevents races and malformed downstream input, leaving the separate requirement to pinpoint which known workflow stage failed when the final artifact is incomplete unmet.

C:

Both steps target different results—ensure each later tool receives a validated artifact from its preceding stage and prevent specialists from producing incompatible artifacts for the orchestrator—because later steps cannot safely start until upstream data exists; passing validated outputs prevents races and malformed downstream input and explicit delegation contracts make multi-agent integration testable; free-form handoffs often obscure whether a child finished its assigned task; the required capabilities are instead to pinpoint which known workflow stage failed when the final artifact is incomplete and to send distinct request types to specialized handlers while keeping the routing rule inspectable.

D:

The first step is appropriate for the requirement to pinpoint which known workflow stage failed when the final artifact is incomplete because deterministic stages are operationally useful when their boundaries are observable; a final answer alone cannot reveal which step produced the fault; the other step instead aims to prevent specialists from producing incompatible artifacts for the orchestrator because explicit delegation contracts make multi-agent integration testable; free-form handoffs often obscure whether a child finished its assigned task, which does not meet the second requirement to send distinct request types to specialized handlers while keeping the routing rule inspectable.

Question 326

A team maintaining a Python Claude API backend has two different engineering requirements: (1) distinguish queued, running, waiting-for-approval, failed, and completed agent jobs, and (2) expose external business tools only to workflows that actually need them. Which TWO independent changes directly meet them? Choose TWO.

  1. Validate generated fields against domain rules after parsing.
  2. Persist explicit job states with allowed transitions.
  3. Enable required plugin or connector capabilities using least-privilege configuration.
  4. Delimit retrieved text as untrusted source material.
  5. Apply a context retention policy and summarize earlier turns where suitable.

Explanation

Correct Answers

B:

To distinguish queued, running, waiting-for-approval, failed, and completed agent jobs as part of a design that must also expose external business tools only to workflows that actually need them, a state machine prevents an incomplete tool operation from being shown as successful and makes retries and cancellation predictable; 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 distinguish queued, running, waiting-for-approval, failed, and completed agent jobs, 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 stop a well-formed JSON response from introducing an impossible customer status because a syntactically valid object may still contain invalid business values; server-side semantics determine whether it is acceptable; the required outcomes are instead to distinguish queued, running, waiting-for-approval, failed, and completed agent jobs and to expose external business tools only to workflows that actually need them.

D:

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 distinguish queued, running, waiting-for-approval, failed, and completed agent jobs and to expose external business tools only to workflows that actually need them.

E:

This alternative serves the separate goal 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; the required outcomes are instead to distinguish queued, running, waiting-for-approval, failed, and completed agent jobs and to expose external business tools only to workflows that actually need them.

Question 327

An architecture review of a tool-calling Claude workflow asks how to ensure an agent obtains explicit authorization before updating a customer record. Which action is the best fit?

  1. Implement a narrowly scoped read-only tool handler.
  2. Disable the capability at configuration or tool-registration level.
  3. Configure a supported remote HTTP transport with authentication and deployment controls.
  4. Put an approval gate in the host-side write handler.

Explanation

Correct Answer

D:

To ensure an agent obtains explicit authorization before updating a customer record in this tool-calling Claude workflow, an irreversible or sensitive write must be permitted by trusted application logic, not merely because the model selected a tool; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to expose a diagnostic capability without allowing the model to modify records because a restricted read interface supports observation while preventing data mutation, unlike giving a diagnostic agent a general administrative API; that mechanism does not meet the different requirement to ensure an agent obtains explicit authorization before updating a customer record.

B:

The proposed alternative helps to remove an agent's access to an obsolete integration without rewriting all its task prompts because actual registered capabilities define what may execute; changing descriptive prompt text alone does not revoke a previously available tool; that mechanism does not meet the different requirement to ensure an agent obtains explicit authorization before updating a customer record.

C:

The proposed alternative helps to expose an MCP server to clients across a network boundary because remote connectivity needs network routing, identity, and authorization; a local stdio subprocess is not a remotely reachable service; that mechanism does not meet the different requirement to ensure an agent obtains explicit authorization before updating a customer record.

Question 328

For a multi-stage support automation, a design is acceptable only if it can execute a requested internal business function inside the application's trusted process while also being able to inspect the result of a completed tool call before later model reasoning consumes it. Which paired implementation is sufficient?

  1. Perform both steps: (1) Inspect the tool_use block, invoke the authorized handler, and return tool_result; (2) return a separate tool_result for every corresponding tool_use identifier.
  2. Perform both steps: (1) Chain dependent operations serially with explicit input and output contracts; (2) attach a post-execution observation hook to the tool lifecycle.
  3. Perform both steps: (1) Chain dependent operations serially with explicit input and output contracts; (2) return a separate tool_result for every corresponding tool_use identifier.
  4. Perform both steps: (1) Inspect the tool_use block, invoke the authorized handler, and return tool_result; (2) attach a post-execution observation hook to the tool lifecycle.

Explanation

Correct Answer

D:

The first change enables the team to execute a requested internal business function inside the application's trusted process because client tools are executed by the application, not by merely declaring a schema; every returned result must be matched to its tool-use identifier; the second addresses the separate need to inspect the result of a completed tool call before later model reasoning consumes it because post-tool inspection can record or validate outcomes after execution, but it cannot retroactively prevent side effects from the completed call.

Incorrect Answers

A:

The first step is appropriate for the requirement to execute a requested internal business function inside the application's trusted process because client tools are executed by the application, not by merely declaring a schema; every returned result must be matched to its tool-use identifier; the other step instead aims to handle several independent tool_use blocks in one assistant message because parallel tool execution requires complete, correctly linked results; dropping one identifier leaves the model's outstanding request unresolved, which does not meet the second requirement to inspect the result of a completed tool call before later model reasoning consumes it.

B:

The second step meets the requirement to inspect the result of a completed tool call before later model reasoning consumes it because post-tool inspection can record or validate outcomes after execution, but it cannot retroactively prevent side effects from the completed call; the first step would only help to ensure each later tool receives a validated artifact from its preceding stage because later steps cannot safely start until upstream data exists; passing validated outputs prevents races and malformed downstream input, leaving the separate requirement to execute a requested internal business function inside the application's trusted process unmet.

C:

Both steps target different results—ensure each later tool receives a validated artifact from its preceding stage and handle several independent tool_use blocks in one assistant message—because later steps cannot safely start until upstream data exists; passing validated outputs prevents races and malformed downstream input and parallel tool execution requires complete, correctly linked results; dropping one identifier leaves the model's outstanding request unresolved; the required capabilities are instead to execute a requested internal business function inside the application's trusted process and to inspect the result of a completed tool call before later model reasoning consumes it.

Question 329

An end-to-end test for a long-context summarization workflow checks whether it can reduce the chance that critical instructions become buried in a huge prompt and answer a company-policy question from current approved records instead of relying on general knowledge. Which plan should be approved to satisfy both checks?

  1. Perform both steps: (1) Place essential constraints prominently and structure large evidence clearly; (2) retrieve authoritative policy passages and cite those used.
  2. Perform both steps: (1) Have a scoped subagent process sources and return a concise verified handoff; (2) retrieve authoritative policy passages and cite those used.
  3. Perform both steps: (1) Have a scoped subagent process sources and return a concise verified handoff; (2) ground consequential statements in retrieved evidence or external checks.
  4. Perform both steps: (1) Place essential constraints prominently and structure large evidence clearly; (2) ground consequential statements in retrieved evidence or external checks.

Explanation

Correct Answer

A:

The first change enables the team to reduce the chance that critical instructions become buried in a huge prompt because ordering, headings, and explicit references help the model distinguish governing rules from supporting material in large requests; the second addresses the separate need to answer a company-policy question from current approved records instead of relying on general knowledge because retrieval supplies task-specific facts that pretraining may not include, while source attribution lets the application verify the response.

Incorrect Answers

B:

The second step meets the requirement to answer a company-policy question from current approved records instead of relying on general knowledge because retrieval supplies task-specific facts that pretraining may not include, while source attribution lets the application verify the response; the first step would only help to analyze a large source set without exposing every raw document to the parent agent because separate contexts let specialists work deeply while the coordinator sees only claims and references needed for the final decision, leaving the separate requirement to reduce the chance that critical instructions become buried in a huge prompt unmet.

C:

Both steps target different results—analyze a large source set without exposing every raw document to the parent agent and avoid treating fluent model wording as evidence that a claim is verified—because separate contexts let specialists work deeply while the coordinator sees only claims and references needed for the final decision and linguistic confidence is not a calibrated truth guarantee, so factual correctness requires independent support; the required capabilities are instead to reduce the chance that critical instructions become buried in a huge prompt and to answer a company-policy question from current approved records instead of relying on general knowledge.

D:

The first step is appropriate for the requirement to reduce the chance that critical instructions become buried in a huge prompt because ordering, headings, and explicit references help the model distinguish governing rules from supporting material in large requests; the other step instead aims to avoid treating fluent model wording as evidence that a claim is verified because linguistic confidence is not a calibrated truth guarantee, so factual correctness requires independent support, which does not meet the second requirement to answer a company-policy question from current approved records instead of relying on general knowledge.

Question 330

In a repository-level Claude Code rollout, a release requirement is to make a reusable development procedure available to Claude Code with supporting files. Which implementation addresses that specific requirement?

  1. Invoke the supported noninteractive or print-mode command interface.
  2. Configure a specialized Claude Code subagent with a narrow remit.
  3. Create a project skill with the documented skill metadata and content.
  4. Define policy in the appropriate managed or shared settings scope.

Explanation

Correct Answer

C:

To make a reusable development procedure available to Claude Code with supporting files in this repository-level Claude Code rollout, a skill packages guidance or a workflow for reuse across relevant tasks; it is not identical to granting a runtime tool permission; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

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 make a reusable development procedure available to Claude Code with supporting files.

B:

The proposed alternative helps to delegate an independent code review without filling the main coding session with details because subagents can focus on a task and return a summary, limiting noise in the parent session and allowing separate permissions when configured; that mechanism does not meet the different requirement to make a reusable development procedure available to Claude Code with supporting files.

D:

The proposed alternative helps to enforce a team-approved permission policy despite local developer preferences because Claude Code has multiple configuration scopes; binding policy to the required scope matters more than placing a rule in an arbitrary JSON file; that mechanism does not meet the different requirement to make a reusable development procedure available to Claude Code with supporting files.

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