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

Question 530

A Claude application build contains an upstream function and a separate downstream function. The upstream work must actually retrieve a customer's order status requested by Claude; the downstream work must match returned batch results to the right source documents despite varying completion order. Which configuration pair covers both?

  1. First component: Read the HTTP error status before retrying. Second component: Reconcile batch responses by custom_id.
  2. First component: Process tool_use responses in the application. Second component: Send tool_result content back to Claude.
  3. First component: Process tool_use responses in the application. Second component: Reconcile batch responses by custom_id.
  4. First component: Send tool_result content back to Claude. Second component: Read the HTTP error status before retrying.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because client tools execute in application code; the model emits structured requests but does not invoke external functions itself, while the second proposal fits its assigned role because a caller-assigned identifier links each result to the original request independently of result ordering; their respective acceptance criteria are to actually retrieve a customer's order status requested by Claude and to match returned batch results to the right source documents despite varying completion order.

Incorrect Answers

A:

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 caller-assigned identifier links each result to the original request independently of result ordering; their respective acceptance criteria are to actually retrieve a customer's order status requested by Claude and to match returned batch results to the right source documents despite varying completion order.

B:

The first proposal fits its assigned 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 produce a user-facing answer after a successful inventory lookup instead of the assigned second role because a result block tied to the tool call returns the external observation to the model for synthesis; their respective acceptance criteria are to actually retrieve a customer's order status requested by Claude and to match returned batch results to the right source documents despite varying completion order.

D:

The first proposal serves the different purpose to produce a user-facing answer after a successful inventory lookup instead of the assigned first 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 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 actually retrieve a customer's order status requested by Claude and to match returned batch results to the right source documents despite varying completion order.

Question 531

The current design of a credential management pipeline does not adequately limit the impact of a temporary worker credential being stolen. Which improvement resolves the gap?

  1. Load keys from a managed secret service
  2. Use short-lived scoped credentials where supported
  3. Rotate a compromised API key promptly
  4. Audit sensitive credential use

Explanation

Correct Answer

B:

Expiring identity grants reduce the time and permissions available to an attacker; this behavior directly supports the need to limit the impact of a temporary worker credential being stolen. Permanent shared administrator keys expand blast radius.

Incorrect Answers

A:

Secrets managers support controlled retrieval, rotation, and access logs; the supported outcome is to avoid committing provider credentials inside a shared repository, whereas this scenario requires the ability to limit the impact of a temporary worker credential being stolen; obscuring a literal string in source is not adequate key protection.

C:

Revocation plus replacement ends use of the leaked credential and requires checking for misuse; despite being useful when a service must cut off an exposed token discovered in CI logs, it is not a solution to limit the impact of a temporary worker credential being stolen; merely deleting a log message leaves the old token valid.

D:

For the alternate objective to detect unexpected API key activity from an unfamiliar process, usage and access logs support incident investigation and anomaly response; the feature here must limit the impact of a temporary worker credential being stolen, and a successful API call alone does not establish that use was authorized.

Question 532

A technical specification for a latency optimization application assigns two jobs to separate modules: module A must avoid rejecting tool schemas because serialized values are invalid, and module B must avoid unauthenticated model requests from a backend worker. Which two-part solution is appropriate?

  1. First component: Parse responses by content block type. Second component: Send the correct API authentication header.
  2. First component: Use the official SDK for standard requests. Second component: Parse responses by content block type.
  3. First component: Use JSON-safe types in request bodies. Second component: Use the official SDK for standard requests.
  4. First component: Use JSON-safe types in request bodies. Second component: Send the correct API authentication header.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations, while the second proposal fits its assigned role because the API validates the provided credential before accepting a request; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to avoid unauthenticated model requests from a backend worker.

Incorrect Answers

A:

The first proposal serves the different purpose to avoid treating a tool call or thinking block as user-visible answer text instead of the assigned first role because structured outputs can contain different block kinds that need type-aware handling, while the second proposal fits its assigned role because the API validates the provided credential before accepting a request; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to avoid unauthenticated model requests from a backend worker.

B:

The first proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned first role because maintained client libraries wrap the HTTP API and expose structured response objects, while the second proposal serves the different purpose to avoid treating a tool call or thinking block as user-visible answer text instead of the assigned second role because structured outputs can contain different block kinds that need type-aware handling; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to avoid unauthenticated model requests from a backend worker.

C:

The first proposal fits its assigned role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations, while the second proposal serves the different purpose to simplify authentication, serialization, and response typing in a Python service instead of the assigned second role because maintained client libraries wrap the HTTP API and expose structured response objects; their respective acceptance criteria are to avoid rejecting tool schemas because serialized values are invalid and to avoid unauthenticated model requests from a backend worker.

Question 533

A production-readiness check for a data pipeline component requires the service to prevent bursts of document jobs from overwhelming rate limits and memory. Which approach passes this check?

  1. Pin dependencies with lockfiles
  2. Use pull requests and focused code review
  3. Keep secrets out of source control
  4. Enforce concurrency limits

Explanation

Correct Answer

D:

A semaphore or bounded queue keeps in-flight work within measured capacity; this behavior directly supports the need to prevent bursts of document jobs from overwhelming rate limits and memory. Launching every request at once turns a throughput problem into throttling.

Incorrect Answers

A:

For the alternate objective to reproduce a working SDK installation across staging and production, locked versions and hashes constrain drift between build environments; the feature here must prevent bursts of document jobs from overwhelming rate limits and memory, and unbounded package updates can introduce new behavior during a routine rebuild.

B:

Peer review creates an explicit checkpoint for correctness, security, and maintainability; this applies to the different goal to detect unsafe permissions and schema changes before merging an agent tool, not the requirement to prevent bursts of document jobs from overwhelming rate limits and memory; running a linter alone cannot assess authorization intent.

C:

When an application needs to prevent API credentials from being exposed through shared repository history, secret stores or environment injection keep production tokens out of committed code; the current capability must instead prevent bursts of document jobs from overwhelming rate limits and memory, while deleting a secret from the latest commit may not remove it from earlier revisions.

Question 534

An architecture review of an application security product lists two distinct outcomes: the first subsystem must prevent a read-only support tool from modifying billing tables, and a second subsystem must stop an injected wiki page from asking an assistant to export credentials. Which pair delivers these outcomes?

  1. First component: Validate tool arguments server-side. Second component: Treat tool and retrieval text as untrusted.
  2. First component: Scope database credentials by tenant and operation. Second component: Use output escaping to prevent XSS.
  3. First component: Use output escaping to prevent XSS. Second component: Validate tool arguments server-side.
  4. First component: Scope database credentials by tenant and operation. Second component: Treat tool and retrieval text as untrusted.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because least-privilege identity limits the damage from a manipulated tool call, while the second proposal fits its assigned role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; their respective acceptance criteria are to prevent a read-only support tool from modifying billing tables and to stop an injected wiki page from asking an assistant to export credentials.

Incorrect Answers

A:

The first proposal serves the different purpose to block a generated database query that targets another tenant's records instead of the assigned first role because backend authorization checks must bind the requested operation to the caller's entitlements, while the second proposal fits its assigned role because lower-trust content is evidence only; control decisions remain with authenticated policy and tool gates; their respective acceptance criteria are to prevent a read-only support tool from modifying billing tables and to stop an injected wiki page from asking an assistant to export credentials.

B:

The first proposal fits its assigned role because least-privilege identity limits the damage from a manipulated tool call, while the second proposal serves the different purpose to display generated customer notes safely in a browser instead of the assigned second role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript; their respective acceptance criteria are to prevent a read-only support tool from modifying billing tables and to stop an injected wiki page from asking an assistant to export credentials.

C:

The first proposal serves the different purpose to display generated customer notes safely in a browser instead of the assigned first role because context-aware encoding prevents text from being interpreted as active HTML or JavaScript, while the second proposal serves the different purpose to block a generated database query that targets another tenant's records instead of the assigned second role because backend authorization checks must bind the requested operation to the caller's entitlements; their respective acceptance criteria are to prevent a read-only support tool from modifying billing tables and to stop an injected wiki page from asking an assistant to export credentials.

Question 535

A design review identifies a missing capability in a document processing project: it must debug where a request stalls between the web UI, queue, and Claude gateway. Which change meets that goal?

  1. Correlate distributed traces across services
  2. Version APIs and response schemas
  3. Use feature flags for risky behavior changes
  4. Pin dependencies with lockfiles

Explanation

Correct Answer

A:

A trace identifier links timing and errors through multiple process boundaries; this behavior directly supports the need to debug where a request stalls between the web UI, queue, and Claude gateway. Local logs with unrelated IDs cannot reconstruct the critical path reliably.

Incorrect Answers

B:

Compatibility-aware contracts and versioned behavior protect consumers from surprise breaking changes; the supported outcome is to allow older application clients to keep working while a new extraction field is introduced, whereas this scenario requires the ability to debug where a request stalls between the web UI, queue, and Claude gateway; silently removing required fields can fail deployments that were not upgraded.

C:

This approach serves the separate need to activate a new tool execution path for only internal testers because runtime controls can segment rollout and permit quick disabling without a code rebuild; it does not establish the outcome to debug where a request stalls between the web UI, queue, and Claude gateway, and hard-coded unconditional activation exposes every tenant simultaneously.

D:

Locked versions and hashes constrain drift between build environments; despite being useful when a service must reproduce a working SDK installation across staging and production, it is not a solution to debug where a request stalls between the web UI, queue, and Claude gateway; unbounded package updates can introduce new behavior during a routine rebuild.

Question 536

During an inference routing rollout, two different failure paths need remediation. The first component must lower spend for large scheduled classification jobs that do not need immediate responses; separately, the second must forecast cost for an application that sends long documents but returns brief classifications. Which changes should be adopted?

  1. First component: Use batch pricing where deadline permits. Second component: Track input and output usage separately.
  2. First component: Use batch pricing where deadline permits. Second component: Use model routing for simple versus hard cases.
  3. First component: Set maximum step counts for agents. Second component: Track input and output usage separately.
  4. First component: Use model routing for simple versus hard cases. Second component: Set maximum step counts for agents.

Explanation

Correct Answer

A:

The first proposal fits its assigned role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal fits its assigned role because metering by token category reveals the main cost driver and supports realistic forecasts; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to forecast cost for an application that sends long documents but returns brief classifications.

Incorrect Answers

B:

The first proposal fits its assigned role because asynchronous batch processing can offer a cost-effective throughput path under supported terms, while the second proposal serves the different purpose to spend high-capability tokens only when validation indicates complexity instead of the assigned second role because conditional routing improves blended cost without discarding an escalation path; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to forecast cost for an application that sends long documents but returns brief classifications.

C:

The first proposal serves the different purpose to contain cumulative token and tool cost across a recursive research session instead of the assigned first role because a bound on iterations prevents repeated generation and calls from growing without limit, while the second proposal fits its assigned role because metering by token category reveals the main cost driver and supports realistic forecasts; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to forecast cost for an application that sends long documents but returns brief classifications.

D:

The first proposal serves the different purpose to spend high-capability tokens only when validation indicates complexity instead of the assigned first role because conditional routing improves blended cost without discarding an escalation path, while the second proposal serves the different purpose to contain cumulative token and tool cost across a recursive research session instead of the assigned second role because a bound on iterations prevents repeated generation and calls from growing without limit; their respective acceptance criteria are to lower spend for large scheduled classification jobs that do not need immediate responses and to forecast cost for an application that sends long documents but returns brief classifications.

Question 537

An architecture review of a language-model integration product lists two distinct outcomes: the first subsystem must estimate model-token input demand before launching a large processing job, and a second subsystem must keep integration behavior aligned with a supported request contract. Which pair delivers these outcomes?

  1. First component: Use a queue for burst absorption. Second component: Use JSON-safe types in request bodies.
  2. First component: Use the Messages count_tokens capability. Second component: Send an API version header where required.
  3. First component: Use JSON-safe types in request bodies. Second component: Send an API version header where required.
  4. First component: Use the Messages count_tokens capability. Second component: Use a queue for burst absorption.

Explanation

Correct Answer

B:

The first proposal fits its assigned role because token counting helps check input budgets before generation and cost planning, while the second proposal fits its assigned role because explicit protocol versioning makes the caller's expected API semantics unambiguous; their respective acceptance criteria are to estimate model-token input demand before launching a large processing job and to keep integration behavior aligned with a supported request contract.

Incorrect Answers

A:

The first proposal serves the different purpose to smooth sudden ingestion spikes before workers call a capacity-limited model API instead of the assigned first role because queueing decouples producers from consumer throughput and enables controlled retries, while the second proposal serves the different purpose to avoid rejecting tool schemas because serialized values are invalid instead of the assigned second role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations; their respective acceptance criteria are to estimate model-token input demand before launching a large processing job and to keep integration behavior aligned with a supported request contract.

C:

The first proposal serves the different purpose to avoid rejecting tool schemas because serialized values are invalid instead of the assigned first role because structured request encoding enforces objects, arrays, strings, booleans, and numeric representations, while the second proposal fits its assigned role because explicit protocol versioning makes the caller's expected API semantics unambiguous; their respective acceptance criteria are to estimate model-token input demand before launching a large processing job and to keep integration behavior aligned with a supported request contract.

D:

The first proposal fits its assigned role because token counting helps check input budgets before generation and cost planning, while the second proposal serves the different purpose to smooth sudden ingestion spikes before workers call a capacity-limited model API instead of the assigned second role because queueing decouples producers from consumer throughput and enables controlled retries; their respective acceptance criteria are to estimate model-token input demand before launching a large processing job and to keep integration behavior aligned with a supported request contract.

Question 538

A technical specification for a token economics application assigns two jobs to separate modules: module A must avoid confusing allowable prompt size with maximum generated response length, and module B must distinguish borderline policy labels with examples of both allowed and disallowed cases. Which two-part solution is appropriate?

  1. First component: Reduce reasoning effort on trivial routing. Second component: Apply zero-shot instructions for a straightforward task.
  2. First component: Apply zero-shot instructions for a straightforward task. Second component: Use contrasting few-shot examples.
  3. First component: Distinguish input from output token limits. Second component: Reduce reasoning effort on trivial routing.
  4. First component: Distinguish input from output token limits. Second component: Use contrasting few-shot examples.

Explanation

Correct Answer

D:

The first proposal fits its assigned role because the context budget constrains total material considered while output ceilings bound what a single generation can emit, while the second proposal fits its assigned role because multiple representative cases help define a decision boundary and reduce ambiguity; their respective acceptance criteria are to avoid confusing allowable prompt size with maximum generated response length and to distinguish borderline policy labels with examples of both allowed and disallowed cases.

Incorrect Answers

A:

The first proposal serves the different purpose to shorten latency and spend on tasks that need only basic categorization instead of the assigned first role because lower effort can suit predictable work where deeper reasoning adds little measurable quality, while the second proposal serves the different purpose to classify a familiar support message where labels and criteria are already clear instead of the assigned second role because direct instructions can be sufficient when the task is simple and well specified; their respective acceptance criteria are to avoid confusing allowable prompt size with maximum generated response length and to distinguish borderline policy labels with examples of both allowed and disallowed cases.

B:

The first proposal serves the different purpose to classify a familiar support message where labels and criteria are already clear instead of the assigned first role because direct instructions can be sufficient when the task is simple and well specified, while the second proposal fits its assigned role because multiple representative cases help define a decision boundary and reduce ambiguity; their respective acceptance criteria are to avoid confusing allowable prompt size with maximum generated response length and to distinguish borderline policy labels with examples of both allowed and disallowed cases.

C:

The first proposal fits its assigned role because the context budget constrains total material considered while output ceilings bound what a single generation can emit, while the second proposal serves the different purpose to shorten latency and spend on tasks that need only basic categorization instead of the assigned second role because lower effort can suit predictable work where deeper reasoning adds little measurable quality; their respective acceptance criteria are to avoid confusing allowable prompt size with maximum generated response length and to distinguish borderline policy labels with examples of both allowed and disallowed cases.

Question 539

A retrieval pipeline team is evaluating two disjoint use cases. For one use case, it must solve a complex migration comparison that requires several distinct checks; for the other, it must let the model summarize a hostile email without obeying its embedded commands. Which paired choices are justified?

  1. First component: Use few-shot boundary cases. Second component: Delimit untrusted source material.
  2. First component: Use explicit refusal and escalation instructions. Second component: Use few-shot boundary cases.
  3. First component: Use a stepwise decomposition. Second component: Delimit untrusted source material.
  4. First component: Use a stepwise decomposition. Second component: Use explicit refusal and escalation instructions.

Explanation

Correct Answer

C:

The first proposal fits its assigned role because breaking the work into verifiable stages lets the application check intermediate artifacts, while the second proposal fits its assigned role because clear source boundaries and explicit treatment as quoted evidence help reduce instruction confusion; their respective acceptance criteria are to solve a complex migration comparison that requires several distinct checks and to let the model summarize a hostile email without obeying its embedded commands.

Incorrect Answers

A:

The first proposal serves the different purpose to distinguish near-duplicate support intents that a broad rule routinely confuses instead of the assigned first role because examples illustrating each side of a decision boundary communicate nuanced classification criteria, while the second proposal fits its assigned role because clear source boundaries and explicit treatment as quoted evidence help reduce instruction confusion; their respective acceptance criteria are to solve a complex migration comparison that requires several distinct checks and to let the model summarize a hostile email without obeying its embedded commands.

B:

The first proposal serves the different purpose to prevent a customer-facing assistant from making final legal determinations without review instead of the assigned first role because clear boundaries describe when to abstain or route to a qualified person, while the second proposal serves the different purpose to distinguish near-duplicate support intents that a broad rule routinely confuses instead of the assigned second role because examples illustrating each side of a decision boundary communicate nuanced classification criteria; their respective acceptance criteria are to solve a complex migration comparison that requires several distinct checks and to let the model summarize a hostile email without obeying its embedded commands.

D:

The first proposal fits its assigned role because breaking the work into verifiable stages lets the application check intermediate artifacts, while the second proposal serves the different purpose to prevent a customer-facing assistant from making final legal determinations without review instead of the assigned second role because clear boundaries describe when to abstain or route to a qualified person; their respective acceptance criteria are to solve a complex migration comparison that requires several distinct checks and to let the model summarize a hostile email without obeying its embedded commands.

Question 540

A backend integration review requires two independent, explicitly defined outcomes: the first workstream must trace a quality regression to the exact instruction revision used; a second must keep external tool connectors compatible after client upgrades. Which TWO actions directly provide these capabilities? Choose TWO.

  1. Track MCP server versions and contracts
  2. Put repository guidance in CLAUDE.md
  3. Use settings.json for Claude Code permissions
  4. Keep environment-specific settings external
  5. Version prompt templates alongside code

Explanation

Correct Answers

A:

Declared versions and integration tests expose resource or schema changes before deployment; this directly supports task 2 to keep external tool connectors compatible after client upgrades, not the separate task or tasks to trace a quality regression to the exact instruction revision used; automatically using the newest connector can alter behavior unexpectedly.

E:

Source-controlled prompt assets make rollbacks, diffs, and evaluations possible; this directly supports task 1 to trace a quality regression to the exact instruction revision used, not the separate task or tasks to keep external tool connectors compatible after client upgrades; editing prompts in an unversioned dashboard hides causal history.

Incorrect Answers

B:

Repository memory files provide persistent instructional context to coding sessions; this implements the different outcome to give Claude Code the project's build, test, and architecture conventions rather than the required tasks to trace a quality regression to the exact instruction revision used and to keep external tool connectors compatible after client upgrades, and they are not an application secrets manager or the API's global system prompt, so it is not a direct solution to any of the assigned workstreams.

C:

Permission settings define configurable controls for Claude Code rather than merely describing preferences; this implements the different outcome to constrain a repository coding assistant's allowed tools and execution behavior rather than the required tasks to trace a quality regression to the exact instruction revision used and to keep external tool connectors compatible after client upgrades, and a CLAUDE.md comment cannot be relied on as a hard execution gate, so it is not a direct solution to any of the assigned workstreams.

D:

Configuration injection separates environment differences from immutable application artifacts; this implements the different outcome to deploy the same application build to staging and production with distinct endpoints rather than the required tasks to trace a quality regression to the exact instruction revision used and to keep external tool connectors compatible after client upgrades, and hard-coded URLs require risky code changes for promotion, so it is not a direct solution to any of the assigned workstreams.

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