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

Question 590

A technical specification for a document processing application assigns two jobs to separate modules: module A must let Claude request a read-only inventory lookup with typed arguments, and module B must return an answer to a short user request through a backend service. Which two-part solution is appropriate?

  1. First component: Supply a tool definition with input schema. Second component: Call the Messages API with explicit model and max_tokens.
  2. First component: Read the HTTP error status before retrying. Second component: Call the Messages API with explicit model and max_tokens.
  3. First component: Supply a tool definition with input schema. Second component: Include an image content block.
  4. First component: Include an image content block. Second component: Read the HTTP error status before retrying.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because a declared tool name, description, and schema constrain the interface offered to the model, while the second proposal fits its assigned role because a message request identifies the target model, a message list, and an output-token ceiling; their respective acceptance criteria are to let Claude request a read-only inventory lookup with typed arguments and to return an answer to a short user request through a backend service.

Incorrect Answers

B:

The first proposal serves the different purpose to distinguish an invalid request from a temporary provider or rate-limit failure instead of the assigned first role because status codes and structured errors guide correction versus bounded retry, while the second proposal fits its assigned role because a message request identifies the target model, a message list, and an output-token ceiling; their respective acceptance criteria are to let Claude request a read-only inventory lookup with typed arguments and to return an answer to a short user request through a backend service.

C:

The first proposal fits its assigned role because a declared tool name, description, and schema constrain the interface offered to the model, while the second proposal serves the different purpose to analyze a photographed shipping label with the supported multimodal Messages input instead of the assigned second role because image inputs are supplied as typed content with appropriate source data or references; their respective acceptance criteria are to let Claude request a read-only inventory lookup with typed arguments and to return an answer to a short user request through a backend service.

D:

The first proposal serves the different purpose to analyze a photographed shipping label with the supported multimodal Messages input instead of the assigned first role because image inputs are supplied as typed content with appropriate source data or references, while the second proposal serves the different purpose to distinguish an invalid request from a temporary provider or rate-limit failure instead of the assigned second role because status codes and structured errors guide correction versus bounded retry; their respective acceptance criteria are to let Claude request a read-only inventory lookup with typed arguments and to return an answer to a short user request through a backend service.

Question 591

A backend integration review requires two independent, explicitly defined outcomes: the first workstream must identify rising error rates and latency after launch; a second must test whether document classification quality is viable on representative files. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Use a proof of concept before production commitment
  2. Instrument production observability
  3. Assign an owner to every integration
  4. Perform a threat review before go-live
  5. Implement automated regression tests

Explanation

Correct Answers

A:

A small pilot reduces feasibility risk before funding a complete integration; this directly supports task 2 to test whether document classification quality is viable on representative files, not the separate task or tasks to identify rising error rates and latency after launch; a presentation-only prototype cannot establish real input coverage.

B:

Logs, metrics, traces, and alert thresholds reveal operational failures at the right layer; this directly supports task 1 to identify rising error rates and latency after launch, not the separate task or tasks to test whether document classification quality is viable on representative files; user feedback alone arrives too late for timely diagnosis.

Incorrect Answers

C:

Ownership enables rotation, monitoring, change approval, and retirement decisions; this implements the different outcome to prevent abandoned connectors from retaining access after an application is transferred rather than the required tasks to test whether document classification quality is viable on representative files and to identify rising error rates and latency after launch, and an undocumented connector can remain privileged beyond its operational need, so it is not a direct solution to any of the assigned workstreams.

D:

Reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss; this implements the different outcome to uncover prompt-injection paths through retrieved webpages and connected tools rather than the required tasks to test whether document classification quality is viable on representative files and to identify rising error rates and latency after launch, and a post-incident review cannot prevent the initial exposure, so it is not a direct solution to any of the assigned workstreams.

E:

Repeatable cases compare changes against documented acceptance criteria; this implements the different outcome to catch schema and policy failures after a model or tool update rather than the required tasks to test whether document classification quality is viable on representative files and to identify rising error rates and latency after launch, and a single successful demonstration provides little protection against regressions, so it is not a direct solution to any of the assigned workstreams.

Question 592

An agent governance application is approaching release, but the team still needs to prevent an unnoticed local edit from disabling a team's protection of secret files. What is the most appropriate implementation?

  1. Use a post-tool hook to record outcomes
  2. Fail closed when a required safety hook fails
  3. Test hook input and exit handling
  4. Keep hook scripts under change control

Explanation

Correct Answer

D:

Versioning and review make guardrail behavior inspectable and reproducible; this behavior directly supports the need to prevent an unnoticed local edit from disabling a team's protection of secret files. Unreviewed workstation-local scripts can drift across developers.

Incorrect Answers

A:

Post-execution events are useful for audit, metrics, and follow-up checks once the tool has run; despite being useful when a service must capture which files an approved agent operation actually modified, it is not a solution to prevent an unnoticed local edit from disabling a team's protection of secret files; they cannot serve as the only prevention mechanism for an irreversible action.

B:

For the alternate objective to prevent a tool action from proceeding when its authorization service is unreachable, a fail-closed gate treats missing approval as denial for sensitive operations; the feature here must prevent an unnoticed local edit from disabling a team's protection of secret files, and fail-open behavior favors availability at the expense of an important security boundary.

C:

Hook contracts specify the event, supplied data, and supported control response; integration tests verify expected enforcement; this applies to the different goal to ensure a policy block is interpreted correctly by the Claude Code runtime, not the requirement to prevent an unnoticed local edit from disabling a team's protection of secret files; a script printing a warning does not necessarily block the tool.

Question 593

A release plan for a document processing platform has two acceptance checks: component one must produce a user-facing answer after a successful inventory lookup; component two must return an answer to a short user request through a backend service. Which proposal passes both?

  1. First component: Send tool_result content back to Claude. Second component: Process tool_use responses in the application.
  2. First component: Handle the tool_use stop_reason. Second component: Call the Messages API with explicit model and max_tokens.
  3. First component: Send tool_result content back to Claude. Second component: Call the Messages API with explicit model and max_tokens.
  4. First component: Process tool_use responses in the application. Second component: Handle the tool_use stop_reason.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because a result block tied to the tool call returns the external observation to the model for synthesis, while the second proposal fits its assigned role because a message request identifies the target model, a message list, and an output-token ceiling; their respective acceptance criteria are to produce a user-facing answer after a successful inventory lookup and to return an answer to a short user request through a backend service.

Incorrect Answers

A:

The first proposal fits its assigned role because a result block tied to the tool call returns the external observation to the model for synthesis, while the second proposal serves the different purpose to actually retrieve a customer's order status requested by Claude instead of the assigned second role because client tools execute in application code; the model emits structured requests but does not invoke external functions itself; their respective acceptance criteria are to produce a user-facing answer after a successful inventory lookup and to return an answer to a short user request through a backend service.

B:

The first proposal serves the different purpose to continue the agent loop when Claude is waiting for external observations instead of the assigned first role because this stop reason means tool calls need to be executed and their results returned before synthesis, while the second proposal fits its assigned role because a message request identifies the target model, a message list, and an output-token ceiling; their respective acceptance criteria are to produce a user-facing answer after a successful inventory lookup and to return an answer to a short user request through a backend service.

D:

The first proposal serves the different purpose to actually retrieve a customer's order status requested by Claude instead of the assigned first role because client tools execute in application code; the model emits structured requests but does not invoke external functions itself, while the second proposal serves the different purpose to continue the agent loop when Claude is waiting for external observations instead of the assigned second role because this stop reason means tool calls need to be executed and their results returned before synthesis; their respective acceptance criteria are to produce a user-facing answer after a successful inventory lookup and to return an answer to a short user request through a backend service.

Question 594

A technical lead requests a solution that can prevent the frontend from parsing an incomplete JSON chunk as a complete response within an output validation project. Which design should be chosen?

  1. Validate required schema fields
  2. Check evidence alignment after extraction
  3. Separate a partial streaming fragment from a finished object
  4. Use bounded repair or regeneration
  5. Escape generated content in the UI

Explanation

Correct Answer

C:

Stream consumers must buffer and recognize completion before strict object validation; this behavior directly supports the need to prevent the frontend from parsing an incomplete JSON chunk as a complete response. An arbitrary content delta may end halfway through a field.

Incorrect Answers

A:

Schema checks enforce field presence, types, and enumerations before the result enters a database; the supported outcome is to reject a response that omits a mandated account identifier, whereas this scenario requires the ability to prevent the frontend from parsing an incomplete JSON chunk as a complete response; syntactically valid JSON may still be contract-invalid.

B:

This approach serves the separate need to detect plausible dates or amounts that are absent from the provided document because semantic verification compares fields to authoritative source spans; it does not establish the outcome to prevent the frontend from parsing an incomplete JSON chunk as a complete response, and a high-confidence generated value is not proof that it was present.

D:

For the alternate objective to recover malformed data without entering an infinite prompt-retry loop, a limited correction attempt can use validation errors as feedback before escalating; the feature here must prevent the frontend from parsing an incomplete JSON chunk as a complete response, and unbounded retries can consume budget without resolving a defective input.

E:

Output encoding or sanitization protects display contexts from untrusted markup; this applies to the different goal to show model-produced HTML snippets without allowing browser script injection, not the requirement to prevent the frontend from parsing an incomplete JSON chunk as a complete response; a correct JSON wrapper does not make embedded HTML safe.

Question 595

A production-readiness check for a data pipeline component requires the service to prevent a malicious help article from ordering the model to reveal secrets. Which approach passes this check?

  1. Treat retrieval results as untrusted data
  2. Handle empty and partial model responses
  3. Place durable behavior instructions in the system parameter
  4. Deduplicate application events

Explanation

Correct Answer

A:

Retrieved content should be framed as evidence, never upgraded to new tool or system authority; this behavior directly supports the need to prevent a malicious help article from ordering the model to reveal secrets. A trustworthy source URL does not make embedded commands authorized.

Incorrect Answers

B:

This approach serves the separate need to keep a downstream parser from crashing when a request returns no usable text block because content-aware response handling checks block types, stop reasons, and required values before proceeding; it does not establish the outcome to prevent a malicious help article from ordering the model to reveal secrets, and assuming every message contains a single complete text string is unsafe.

C:

System-level guidance supplies application-wide instruction context, separate from each user's task content; despite being useful when a service must ensure an API assistant consistently uses a defined support role across requests, it is not a solution to prevent a malicious help article from ordering the model to reveal secrets; a string placed in retrieved documents has no authority to redefine the application policy.

D:

For the alternate objective to avoid starting two extraction jobs for the same uploaded document after repeated browser submissions, an idempotent job key lets the server recognize duplicates at its request boundary; the feature here must prevent a malicious help article from ordering the model to reveal secrets, and model prompting cannot identify all retries arriving from outside the conversation.

Question 596

An architecture review of a prompt engineering product lists two distinct outcomes: the first subsystem must avoid accepting malformed generated objects because they resemble JSON to a reader, and a second subsystem must recover malformed data without entering an infinite prompt-retry loop. Which pair delivers these outcomes?

  1. First component: Handle refusal and empty content explicitly. Second component: Escape generated content in the UI.
  2. First component: Parse JSON with a real parser. Second component: Use bounded repair or regeneration.
  3. First component: Escape generated content in the UI. Second component: Use bounded repair or regeneration.
  4. First component: Parse JSON with a real parser. Second component: Handle refusal and empty content explicitly.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds, while the second proposal fits its assigned role because a limited correction attempt can use validation errors as feedback before escalating; their respective acceptance criteria are to avoid accepting malformed generated objects because they resemble JSON to a reader and to recover malformed data without entering an infinite prompt-retry loop.

Incorrect Answers

A:

The first proposal serves the different purpose to prevent a parser crash when the model returns no ordinary text instead of the assigned first role because response handling must branch on stop reason and content block types before decoding data, while the second proposal serves the different purpose to show model-produced HTML snippets without allowing browser script injection instead of the assigned second role because output encoding or sanitization protects display contexts from untrusted markup; their respective acceptance criteria are to avoid accepting malformed generated objects because they resemble JSON to a reader and to recover malformed data without entering an infinite prompt-retry loop.

C:

The first proposal serves the different purpose to show model-produced HTML snippets without allowing browser script injection instead of the assigned first role because output encoding or sanitization protects display contexts from untrusted markup, while the second proposal fits its assigned role because a limited correction attempt can use validation errors as feedback before escalating; their respective acceptance criteria are to avoid accepting malformed generated objects because they resemble JSON to a reader and to recover malformed data without entering an infinite prompt-retry loop.

D:

The first proposal fits its assigned role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds, while the second proposal serves the different purpose to prevent a parser crash when the model returns no ordinary text instead of the assigned second role because response handling must branch on stop reason and content block types before decoding data; their respective acceptance criteria are to avoid accepting malformed generated objects because they resemble JSON to a reader and to recover malformed data without entering an infinite prompt-retry loop.

Question 597

A technical lead requests a solution that can maintain multiple Claude entry points without drifting retry and logging behavior within a Claude application project. Which design should be chosen?

  1. Refactor duplicated request orchestration
  2. Version APIs and response schemas
  3. Use feature flags for risky behavior changes
  4. Avoid retrying non-idempotent writes blindly

Explanation

Correct Answer

A:

A shared, tested client layer centralizes cross-cutting concerns and reduces inconsistent fixes; this behavior directly supports the need to maintain multiple Claude entry points without drifting retry and logging behavior. Copying the same networking code into every route magnifies defects.

Incorrect Answers

B:

Compatibility-aware contracts and versioned behavior protect consumers from surprise breaking changes; this applies to the different goal to allow older application clients to keep working while a new extraction field is introduced, not the requirement to maintain multiple Claude entry points without drifting retry and logging behavior; silently removing required fields can fail deployments that were not upgraded.

C:

When an application needs to activate a new tool execution path for only internal testers, runtime controls can segment rollout and permit quick disabling without a code rebuild; the current capability must instead maintain multiple Claude entry points without drifting retry and logging behavior, while hard-coded unconditional activation exposes every tenant simultaneously.

D:

Retries of side-effecting actions need idempotency keys or transaction reconciliation; the supported outcome is to keep an interrupted invoice-creation request from generating duplicate invoices, whereas this scenario requires the ability to maintain multiple Claude entry points without drifting retry and logging behavior; network timeouts do not prove the first write failed.

Question 598

A team maintaining an engineering productivity needs to manage a complex migration that requires checkpoints after several tool actions. Which implementation most directly satisfies the requirement?

  1. Use retrieval before generation
  2. Delegate narrow subtasks with a separate context
  3. Use a plan-execute-review loop
  4. Use a framework only when its primitives fit

Explanation

Correct Answer

C:

Separating plan, execution, and review makes deviations visible before a final outcome is accepted; this behavior directly supports the need to manage a complex migration that requires checkpoints after several tool actions. A one-shot response cannot verify environmental effects.

Incorrect Answers

A:

When an application needs to answer questions from changing internal documentation with traceable source excerpts, retrieval grounds a model answer in current authoritative text rather than hoping parametric knowledge is current; the current capability must instead manage a complex migration that requires checkpoints after several tool actions, while the retrieved text remains untrusted as instructions and needs relevance checks.

B:

Each subagent can work in a bounded context and return a concise, verified artifact; the supported outcome is to protect a coordinator's window from huge specialist tool outputs, whereas this scenario requires the ability to manage a complex migration that requires checkpoints after several tool actions; copying every intermediate trace into the parent inflates context and cost.

D:

Frameworks can help with graphs, retries, and checkpoints but create maintenance and integration costs; despite being useful when a service must select orchestration dependencies for a project that already has a stable task engine, it is not a solution to manage a complex migration that requires checkpoints after several tool actions; adopting a framework solely for fashionable abstraction is not a technical requirement.

Question 599

A release plan for an engineering productivity platform has two acceptance checks: component one must preserve evidence and data lineage when one agent delegates a subtask to another; component two must coordinate separate billing, compliance, and engineering analyses under one final decision. Which proposal passes both?

  1. First component: Use parallel fan-out and a reconciliation step. Second component: Adopt a supervisor with specialist workers.
  2. First component: Use a deterministic workflow. Second component: Use parallel fan-out and a reconciliation step.
  3. First component: Pass structured handoff artifacts between workers. Second component: Adopt a supervisor with specialist workers.
  4. First component: Pass structured handoff artifacts between workers. Second component: Use a deterministic workflow.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff, while the second proposal fits its assigned role because a managing agent delegates bounded subtasks to specialists and reconciles their outputs against a common objective; their respective acceptance criteria are to preserve evidence and data lineage when one agent delegates a subtask to another and to coordinate separate billing, compliance, and engineering analyses under one final decision.

Incorrect Answers

A:

The first proposal serves the different purpose to analyze several independent document sections concurrently and combine the results instead of the assigned first role because parallel tasks reduce critical-path latency when they do not depend on one another; a join step resolves conflicting findings, while the second proposal fits its assigned role because a managing agent delegates bounded subtasks to specialists and reconciles their outputs against a common objective; their respective acceptance criteria are to preserve evidence and data lineage when one agent delegates a subtask to another and to coordinate separate billing, compliance, and engineering analyses under one final decision.

B:

The first proposal serves the different purpose to execute an unchanged sequence of extraction, validation, and publishing steps instead of the assigned first role because a fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit, while the second proposal serves the different purpose to analyze several independent document sections concurrently and combine the results instead of the assigned second role because parallel tasks reduce critical-path latency when they do not depend on one another; a join step resolves conflicting findings; their respective acceptance criteria are to preserve evidence and data lineage when one agent delegates a subtask to another and to coordinate separate billing, compliance, and engineering analyses under one final decision.

D:

The first proposal fits its assigned role because defined input and output schemas make it possible to attribute conclusions and detect missing fields at the handoff, while the second proposal serves the different purpose to execute an unchanged sequence of extraction, validation, and publishing steps instead of the assigned second role because a fixed pipeline keeps control flow in application code, making execution order reproducible and easy to audit; their respective acceptance criteria are to preserve evidence and data lineage when one agent delegates a subtask to another and to coordinate separate billing, compliance, and engineering analyses under one final decision.

Question 600

After pilot feedback, an agent platform group needs two independent improvements. The first is to branch between remediation and escalation based on the result of a security scan; the second is to coordinate multiple specialists working on interdependent evidence without losing changes. Which engineering proposal handles both?

  1. First component: Use a graph with conditional edges. Second component: Use bounded memory with explicit provenance.
  2. First component: Use bounded memory with explicit provenance. Second component: Prefer a finite state machine for regulated steps.
  3. First component: Use a graph with conditional edges. Second component: Adopt a blackboard of shared task state.
  4. First component: Prefer a finite state machine for regulated steps. Second component: Adopt a blackboard of shared task state.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal fits its assigned role because a controlled shared workspace holds versioned observations and ownership metadata for collaborators; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

Incorrect Answers

A:

The first proposal fits its assigned role because conditional graph transitions encode known branches while allowing model reasoning within selected nodes, while the second proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned second role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

B:

The first proposal serves the different purpose to preserve customer preferences across permitted sessions while distinguishing facts from assumptions instead of the assigned first role because typed, attributable records prevent outdated or unverified memories from becoming unquestioned instructions, while the second proposal serves the different purpose to enforce approval, execution, and confirmation order in a compliance workflow instead of the assigned second role because explicit states and transitions control who may advance a case independently of generated language; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

D:

The first proposal serves the different purpose to enforce approval, execution, and confirmation order in a compliance workflow instead of the assigned first role because explicit states and transitions control who may advance a case independently of generated language, while the second proposal fits its assigned role because a controlled shared workspace holds versioned observations and ownership metadata for collaborators; their respective acceptance criteria are to branch between remediation and escalation based on the result of a security scan and to coordinate multiple specialists working on interdependent evidence without losing changes.

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