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

Question 550

For a model-output validation layer, the missing capability is to prevent a generated status outside a database's accepted code set. What should the developers implement?

  1. Map or reject values not in the approved enumeration.
  2. Validate parsed output against the application's declared schema.
  3. Ground consequential statements in retrieved evidence or external checks.
  4. Revise one prompt component at a time against a regression evaluation set.

Explanation

Correct Answer

A:

To prevent a generated status outside a database's accepted code set in this model-output validation layer, controlled vocabularies need explicit allowed values; a plausible new status label can still break downstream contracts; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

The proposed alternative helps to reject model output missing a field that a downstream service requires because parsing proves a string is legal JSON, but schema validation checks required keys, types, and structural constraints; that mechanism does not meet the different requirement to prevent a generated status outside a database's accepted code set.

C:

The proposed alternative helps 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; that mechanism does not meet the different requirement to prevent a generated status outside a database's accepted code set.

D:

The proposed alternative helps to improve a prompt while preserving performance on previously solved cases because controlled prompt iteration distinguishes genuine quality gains from regressions or overfitting to one attractive example; that mechanism does not meet the different requirement to prevent a generated status outside a database's accepted code set.

Question 551

In a customer-facing AI feature, testing reveals that the system cannot enable an administrator to determine how a particular AI decision was produced and cannot design for a documented burst of simultaneous requests without uncontrolled overload. Select the two targeted actions that close these gaps. Choose TWO.

  1. Require structured request IDs, tool traces, and version metadata with privacy controls.
  2. Configure the max_tokens request parameter appropriately.
  3. Specify expected concurrency and enforce admission or queueing limits.
  4. Use the API's documented POST request with a JSON body.
  5. Supply the required API version header.

Explanation

Correct Answers

A:

To enable an administrator to determine how a particular AI decision was produced as part of a design that must also design for a documented burst of simultaneous requests without uncontrolled overload, traceability depends on consistent operational evidence, not just retaining the final generated answer or a screenshot; this is why the action is one of the two required selections.

C:

To design for a documented burst of simultaneous requests without uncontrolled overload as part of a design that must also enable an administrator to determine how a particular AI decision was produced, capacity planning separates average traffic from peak demand and prevents upstream rate limits from becoming cascading application failures; this is why the action is one of the two required selections.

Incorrect Answers

B:

This alternative serves the separate goal 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 required outcomes are instead to enable an administrator to determine how a particular AI decision was produced and to design for a documented burst of simultaneous requests without uncontrolled overload.

D:

This alternative serves the separate goal to send a model inference request with the operation expected by the REST endpoint because a state-changing inference operation is submitted as an HTTP request with an explicit method and payload, not inferred from a browser URL alone; the required outcomes are instead to enable an administrator to determine how a particular AI decision was produced and to design for a documented burst of simultaneous requests without uncontrolled overload.

E:

This alternative serves the separate goal 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; the required outcomes are instead to enable an administrator to determine how a particular AI decision was produced and to design for a documented burst of simultaneous requests without uncontrolled overload.

Question 552

An end-to-end test for an agent access-control assessment checks whether it can detect unauthorized modifications to a tool result before it reaches the model and investigate user actions without leaking API keys into operational records. Which plan should be approved to satisfy both checks?

  1. Perform both steps: (1) Verify origin and integrity of sensitive external data where supported; (2) redact secrets and protect log access with retention controls.
  2. Perform both steps: (1) Verify origin and integrity of sensitive external data where supported; (2) use a server-side workload identity or scoped service credential.
  3. Perform both steps: (1) Revoke and rotate the affected credential and update dependent services; (2) redact secrets and protect log access with retention controls.
  4. Perform both steps: (1) Revoke and rotate the affected credential and update dependent services; (2) use a server-side workload identity or scoped service credential.

Explanation

Correct Answer

A:

The first change enables the team to detect unauthorized modifications to a tool result before it reaches the model because trusted decisions require confidence that tool outputs were not altered; transport and signature checks complement content validation; the second addresses the separate need to investigate user actions without leaking API keys into operational records because logs support accountability only when access and retention are restricted; copying all prompt content into logs creates another exposure surface.

Incorrect Answers

B:

The first step is appropriate for the requirement to detect unauthorized modifications to a tool result before it reaches the model because trusted decisions require confidence that tool outputs were not altered; transport and signature checks complement content validation; the other step instead aims to stop frontend users from receiving unrestricted backend tool credentials because service identities tie privileges to a runtime workload and avoid exposing long-lived secrets to browsers or untrusted users, which does not meet the second requirement to investigate user actions without leaking API keys into operational records.

C:

The second step meets the requirement to investigate user actions without leaking API keys into operational records because logs support accountability only when access and retention are restricted; copying all prompt content into logs creates another exposure surface; the first step would only help to reduce exposure after an API key is suspected compromised because rotation restores credential control only when the old secret is disabled and consumers move to the replacement safely, leaving the separate requirement to detect unauthorized modifications to a tool result before it reaches the model unmet.

D:

Both steps target different results—reduce exposure after an API key is suspected compromised and stop frontend users from receiving unrestricted backend tool credentials—because rotation restores credential control only when the old secret is disabled and consumers move to the replacement safely and service identities tie privileges to a runtime workload and avoid exposing long-lived secrets to browsers or untrusted users; the required capabilities are instead to detect unauthorized modifications to a tool result before it reaches the model and to investigate user actions without leaking API keys into operational records.

Question 553

A planned upgrade to a structured output service has two requirements that must both pass: keep only evidence that matters to the question when retrieval returns hundreds of documents; identify when a long agent discussion begins solving a different problem than the user approved. Identify the two direct implementations. Choose TWO.

  1. Recheck current plans against a stored objective and constraints.
  2. Validate parsed output against the application's declared schema.
  3. Escape or sanitize model text in the output presentation layer.
  4. Rank and select relevant passages before building the model context.
  5. Name each mandatory field or section and provide formatting constraints.

Explanation

Correct Answers

A:

To identify when a long agent discussion begins solving a different problem than the user approved as part of a design that must also keep only evidence that matters to the question when retrieval returns hundreds of documents, explicit objective comparison detects drift before tool actions diverge from the original task; extra history alone cannot guarantee alignment; this is why the action is one of the two required selections.

D:

To keep only evidence that matters to the question when retrieval returns hundreds of documents as part of a design that must also identify when a long agent discussion begins solving a different problem than the user approved, relevance filtering reduces distracting information and token usage; dumping every retrieved page can degrade grounding and exceed limits; this is why the action is one of the two required selections.

Incorrect Answers

B:

This alternative serves the separate goal to reject model output missing a field that a downstream service requires because parsing proves a string is legal JSON, but schema validation checks required keys, types, and structural constraints; the required outcomes are instead to keep only evidence that matters to the question when retrieval returns hundreds of documents and to identify when a long agent discussion begins solving a different problem than the user approved.

C:

This alternative serves the separate goal to safely render generated text in a browser without executing embedded markup because generated content is untrusted for HTML rendering; injection into the DOM must not become executable client-side code; the required outcomes are instead to keep only evidence that matters to the question when retrieval returns hundreds of documents and to identify when a long agent discussion begins solving a different problem than the user approved.

E:

This alternative serves the separate goal to require that a generated report have a fixed set of sections because concrete desired structure is easier to verify than a vague instruction to be professional or comprehensive; the required outcomes are instead to keep only evidence that matters to the question when retrieval returns hundreds of documents and to identify when a long agent discussion begins solving a different problem than the user approved.

Question 554

A change request for a high-volume Messages API gateway combines two needs: avoid retrying a malformed request that the API consistently rejects, and recover transient 429 or 5xx responses without creating a retry storm. Which implementation pair addresses both, not just one?

  1. Perform both steps: (1) Classify permanent client errors separately from transient failures; (2) retry eligible failures with capped exponential backoff and jitter.
  2. Perform both steps: (1) Classify permanent client errors separately from transient failures; (2) use the api's documented post request with a json body.
  3. Perform both steps: (1) Refactor in bounded steps under existing tests; (2) use the api's documented post request with a json body.
  4. Perform both steps: (1) Refactor in bounded steps under existing tests; (2) retry eligible failures with capped exponential backoff and jitter.

Explanation

Correct Answer

A:

The first change enables the team to avoid retrying a malformed request that the API consistently rejects because a deterministic validation or authorization error requires fixing the request or credential, not another identical attempt; the second addresses the separate need to recover transient 429 or 5xx responses without creating a retry storm because backoff spreads retry traffic and respects transient capacity limits; blind immediate repetition worsens overload.

Incorrect Answers

B:

The first step is appropriate for the requirement to avoid retrying a malformed request that the API consistently rejects because a deterministic validation or authorization error requires fixing the request or credential, not another identical attempt; the other step instead aims to send a model inference request with the operation expected by the REST endpoint because a state-changing inference operation is submitted as an HTTP request with an explicit method and payload, not inferred from a browser URL alone, which does not meet the second requirement to recover transient 429 or 5xx responses without creating a retry storm.

C:

Both steps target different results—preserve behavior while replacing a fragile parser in an AI integration and send a model inference request with the operation expected by the REST endpoint—because small changes constrain regression scope; a wholesale rewrite makes it harder to isolate whether model or parsing behavior changed and a state-changing inference operation is submitted as an HTTP request with an explicit method and payload, not inferred from a browser URL alone; the required capabilities are instead to avoid retrying a malformed request that the API consistently rejects and to recover transient 429 or 5xx responses without creating a retry storm.

D:

The second step meets the requirement to recover transient 429 or 5xx responses without creating a retry storm because backoff spreads retry traffic and respects transient capacity limits; blind immediate repetition worsens overload; the first step would only help to preserve behavior while replacing a fragile parser in an AI integration because small changes constrain regression scope; a wholesale rewrite makes it harder to isolate whether model or parsing behavior changed, leaving the separate requirement to avoid retrying a malformed request that the API consistently rejects unmet.

Question 555

The technical owner of a tool-calling Claude workflow has to let Claude distinguish a failed database lookup from an empty successful result. A separate requirement is to ensure an agent obtains explicit authorization before updating a customer record. Which two-part remediation covers both?

  1. Perform both steps: (1) Describe each tool's purpose, required inputs, and limitations clearly; (2) implement a narrowly scoped read-only tool handler.
  2. Perform both steps: (1) Describe each tool's purpose, required inputs, and limitations clearly; (2) put an approval gate in the host-side write handler.
  3. Perform both steps: (1) Return an explicit tool error indication and an informative safe message; (2) put an approval gate in the host-side write handler.
  4. Perform both steps: (1) Return an explicit tool error indication and an informative safe message; (2) implement a narrowly scoped read-only tool handler.

Explanation

Correct Answer

C:

The first change enables the team 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; the second addresses the separate need to ensure an agent obtains explicit authorization before updating a customer record because an irreversible or sensitive write must be permitted by trusted application logic, not merely because the model selected a tool.

Incorrect Answers

A:

Both steps target different results—prevent two similarly named lookup tools from being confused and expose a diagnostic capability without allowing the model to modify records—because tool descriptions influence the model's selection, so overlapping or vague names make dispatch less reliable and a restricted read interface supports observation while preventing data mutation, unlike giving a diagnostic agent a general administrative API; the required capabilities are instead to let Claude distinguish a failed database lookup from an empty successful result and to ensure an agent obtains explicit authorization before updating a customer record.

B:

The second step meets the requirement to ensure an agent obtains explicit authorization before updating a customer record because an irreversible or sensitive write must be permitted by trusted application logic, not merely because the model selected a tool; the first step would only help to prevent two similarly named lookup tools from being confused because tool descriptions influence the model's selection, so overlapping or vague names make dispatch less reliable, leaving the separate requirement to let Claude distinguish a failed database lookup from an empty successful result unmet.

D:

The first step is appropriate for the requirement 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; the other step instead aims 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, which does not meet the second requirement to ensure an agent obtains explicit authorization before updating a customer record.

Question 556

For a secure tool-execution boundary, the missing capability is to avoid accidentally allowing critical writes when a safety check crashes. What should the developers implement?

  1. Treat retrieved content as untrusted and prevent its instructions from controlling tools.
  2. Define fail-closed behavior for an enforcement hook and test failure paths.
  3. Record authenticated approval events with actor, scope, and request correlation.
  4. Use layered policy enforcement and restrict powerful tools independently of chat text.

Explanation

Correct Answer

B:

To avoid accidentally allowing critical writes when a safety check crashes in this secure tool-execution boundary, a guardrail that silently skips checks on errors is not an effective boundary; failures must prevent the protected action when policy requires it; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to resist instructions embedded in a retrieved support ticket that demand secret disclosure because source material is data rather than authority; enforcing tool permissions and separating roles limits an attacker's ability to redirect execution; that mechanism does not meet the different requirement to avoid accidentally allowing critical writes when a safety check crashes.

C:

The proposed alternative helps to demonstrate who approved a privileged tool action and when because an audit trail binds authorization to a specific action, making privilege use reviewable without treating model-generated text as proof of consent; that mechanism does not meet the different requirement to avoid accidentally allowing critical writes when a safety check crashes.

D:

The proposed alternative helps to prevent an adversarial user from bypassing safety policy by roleplay instructions because adversarial prompting can target instruction hierarchy, so product controls and tool authorization must remain effective when wording is manipulated; that mechanism does not meet the different requirement to avoid accidentally allowing critical writes when a safety check crashes.

Question 557

While planning a multi-tenant support application, the product owner specifies that it must filter risky user-visible content according to application policy. Which solution fulfills the requirement?

  1. Retain source identifiers with retrieved evidence and render supported citations.
  2. Apply content checks at suitable input and output boundaries.
  3. Apply a context retention policy and summarize earlier turns where suitable.
  4. Use strict tool input validation for the exposed tool interface.

Explanation

Correct Answer

B:

To filter risky user-visible content according to application policy in this multi-tenant support application, moderation is a defense layer applied around generation, not a substitute for authenticated tool access or scoped retrieval; the proposed implementation directly supplies that capability.

Incorrect Answers

A:

The proposed alternative helps to let a reviewer trace claims to the material actually consulted because traceability requires linking claims to accessible source passages; fabricated URLs or unlabeled snippets do not provide verifiable provenance; that mechanism does not meet the different requirement to filter risky user-visible content according to application policy.

C:

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 filter risky user-visible content according to application policy.

D:

The proposed alternative helps 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; that mechanism does not meet the different requirement to filter risky user-visible content according to application policy.

Question 558

An architecture decision for an internal agent-extension rollout must support reject a date or identifier that violates business constraints before a service call and let Claude distinguish a failed database lookup from an empty successful result. Which option gives a complete rather than partial solution?

  1. Perform both steps: (1) Publish a properly described MCP tool and its input contract; (2) put an approval gate in the host-side write handler.
  2. Perform both steps: (1) Validate model-supplied tool arguments against schema and domain rules; (2) put an approval gate in the host-side write handler.
  3. Perform both steps: (1) Validate model-supplied tool arguments against schema and domain rules; (2) return an explicit tool error indication and an informative safe message.
  4. Perform both steps: (1) Publish a properly described MCP tool and its input contract; (2) return an explicit tool error indication and an informative safe message.

Explanation

Correct Answer

C:

The first change enables the team to reject a date or identifier that violates business constraints before a service call because even syntactically correct generated inputs can violate account scope or allowed values, so execution must validate both levels; the second addresses the separate need 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.

Incorrect Answers

A:

Both steps target different results—let an MCP client invoke a business capability through a standard server interface and ensure an agent obtains explicit authorization before updating a customer record—because MCP tools represent callable operations with typed parameters; the server executes authorized behavior rather than only providing reference text and an irreversible or sensitive write must be permitted by trusted application logic, not merely because the model selected a tool; the required capabilities are instead to reject a date or identifier that violates business constraints before a service call and to let Claude distinguish a failed database lookup from an empty successful result.

B:

The first step is appropriate for the requirement to reject a date or identifier that violates business constraints before a service call because even syntactically correct generated inputs can violate account scope or allowed values, so execution must validate both levels; the other step instead aims to ensure an agent obtains explicit authorization before updating a customer record because an irreversible or sensitive write must be permitted by trusted application logic, not merely because the model selected a tool, which does not meet the second requirement to let Claude distinguish a failed database lookup from an empty successful result.

D:

The second step meets the requirement 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; the first step would only help to let an MCP client invoke a business capability through a standard server interface because MCP tools represent callable operations with typed parameters; the server executes authorized behavior rather than only providing reference text, leaving the separate requirement to reject a date or identifier that violates business constraints before a service call unmet.

Question 559

The team responsible for a latency-sensitive model gateway needs to prevent a tool_use block from being displayed as if it were natural-language text. What is the most direct engineering change?

  1. Check each response block's type before extracting its fields.
  2. Branch on HTTP status and decode the provider's error structure.
  3. Parse structured payloads with explicit failure handling.
  4. Budget total context for instructions, history, tools, and output.

Explanation

Correct Answer

A:

To prevent a tool_use block from being displayed as if it were natural-language text in this latency-sensitive model gateway, typed response objects can contain several block families; assuming every block has a text field causes logic errors; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

The proposed alternative helps to stop interpreting non-2xx API responses as normal assistant messages because transport errors are not regular model completions, so application control flow must treat them separately; that mechanism does not meet the different requirement to prevent a tool_use block from being displayed as if it were natural-language text.

C:

The proposed alternative helps to reject incomplete or malformed response data before business logic consumes it because JSON parsing validates syntax, while separate schema and semantic checks verify types and permitted values; that mechanism does not meet the different requirement to prevent a tool_use block from being displayed as if it were natural-language text.

D:

The proposed alternative helps to know why a long prompt plus a proposed response may exceed the model's accepted context because a context window bounds what can be processed in one request; large tool results consume it along with user messages; that mechanism does not meet the different requirement to prevent a tool_use block from being displayed as if it were natural-language text.

Question 560

A test for a multi-stage support automation fails because it cannot prevent a research assistant from unexpectedly making production changes. Which change fixes the identified failure?

  1. Give the research subagent read-only tools and a narrow instruction contract.
  2. Run side-effect-free tool calls concurrently when their inputs are independent.
  3. Catch tool failures and report typed errors into the agent loop.
  4. Use isolated branch state and a controlled reconciliation step.

Explanation

Correct Answer

A:

To prevent a research assistant from unexpectedly making production changes in this multi-stage support automation, capability isolation prevents a specialist from acting outside its delegated role even if it encounters persuasive untrusted instructions; the proposed implementation directly supplies that capability.

Incorrect Answers

B:

The proposed alternative helps to speed up independent data lookups without causing write-order races because read-only independent calls can safely overlap; mutating operations need explicit ordering or concurrency control; that mechanism does not meet the different requirement to prevent a research assistant from unexpectedly making production changes.

C:

The proposed alternative helps to keep a failed tool from being mistaken for successful completion of an objective because explicit failure messages let the model or controller choose recovery; swallowing exceptions makes later actions rely on results that never existed; that mechanism does not meet the different requirement to prevent a research assistant from unexpectedly making production changes.

D:

The proposed alternative helps to stop two parallel branches from overwriting the same mutable record because explicit merge rules are required when outputs converge; concurrent mutation without arbitration causes nondeterministic results; that mechanism does not meet the different requirement to prevent a research assistant from unexpectedly making production changes.

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