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

Question 110

An answer is being composed with several facts verified but one critical prerequisite still uncertain. What should the team do at this decision point?

  1. Track source timestamps or versions
  2. Keep unresolved questions explicit
  3. Attach source IDs to retrieved excerpts
  4. Keep pointers to source documents

Explanation

Correct Answer

B:

Recording open issues prevents compaction from converting uncertainty into an invented guarantee, subject to this requirement: suppressing gaps for a cleaner paragraph undermines factual reliability.

Incorrect Answers

A:

Version metadata allows the agent to prefer current evidence and flag historical material; in contrast, recording open issues prevents compaction from converting uncertainty into an invented guarantee, while timestamp alone does not establish which source is authoritative.

C:

Citation metadata lets downstream logic connect statements to original retrieved material; here, the controlling capability is that recording open issues prevents compaction from converting uncertainty into an invented guarantee, but without accurate source mapping, fabricated references can look convincing.

D:

References and identifiers enable later retrieval without copying the entire source into every prompt; the missing capability is more specific: recording open issues prevents compaction from converting uncertainty into an invented guarantee; pointers alone do not make an inaccessible document available at inference time.

Question 111

A failing agent sometimes submits wrong inventory filters and investigators need to reconstruct the sequence. Which solution matches the actual constraint?

  1. Track token and tool budgets per task
  2. Check tool arguments against a schema
  3. Persist failure checkpoints for resumability
  4. Record tool-call arguments and outcomes safely

Explanation

Correct Answer

D:

Structured traces capture call names, sanitized inputs, responses, timing, and error classification—with this limitation: logging must redact secrets and sensitive payload fields before persistence.

Incorrect Answers

A:

Metering links request usage and tool counts to the logical job or trace identifier; the needed capability is different—structured traces capture call names, sanitized inputs, responses, timing, and error classification—and a single final answer's length is not a complete measure of work performed.

B:

Typed validation rejects malformed or out-of-policy arguments before backend execution, whereas the requirement calls for another behavior: structured traces capture call names, sanitized inputs, responses, timing, and error classification; a model-generated JSON object can be syntactically valid while still violating business rules.

C:

Checkpoint records allow a restart to continue without re-running completed side effects; however, the critical mechanism here is that structured traces capture call names, sanitized inputs, responses, timing, and error classification, and replaying the whole conversation may duplicate irreversible changes without idempotency controls.

Question 112

A user requests a feature that the business integration does not implement. What is the right implementation response?

  1. Disable privileged tools during security incidents
  2. Reject unsupported operations explicitly
  3. Map model fields to application fields explicitly
  4. Queue nonurgent tasks during provider outages

Explanation

Correct Answer

B:

A clear capability boundary returns an accurate unsupported-action response; the implementation must still recognize that inventing a successful action would violate user trust and corrupt workflow state.

Incorrect Answers

A:

A feature flag or policy change can revoke risky execution paths while investigation continues; this addresses a separate concern, not the fact that a clear capability boundary returns an accurate unsupported-action response; a prompt-only warning cannot reliably disable an exposed backend permission.

C:

An adapter transforms and validates values at the boundary rather than assuming identical schemas; the missing capability is more specific: a clear capability boundary returns an accurate unsupported-action response; directly sending raw model content to a write endpoint creates avoidable coupling.

D:

Durable storage retains jobs for resumed processing once inference is available; by comparison, the intended solution relies on this: a clear capability boundary returns an accurate unsupported-action response; an in-memory list in a failed worker may lose pending work.

Question 113

An authenticated user asks to modify an invoice belonging to a different account. What change is best aligned with the goal?

  1. Validate generated tool parameters
  2. Audit committed business changes
  3. Authorize each requested resource operation
  4. Separate display text from operational commands

Explanation

Correct Answer

C:

Resource-level policy checks verify that the caller can execute that exact action on that object; a crucial qualification is that authentication alone does not confer access to all records.

Incorrect Answers

A:

Server-side validation constrains types, ranges, ownership, and supported operations; this addresses a separate concern, not the fact that resource-level policy checks verify that the caller can execute that exact action on that object; a well-described function schema does not replace authorization checks.

B:

An immutable audit trail records principal, approved action, object, time, and outcome; here, the controlling capability is that resource-level policy checks verify that the caller can execute that exact action on that object, but the final chat transcript is insufficient evidence of a backend write.

D:

The service distinguishes a human-readable recommendation from an authorized tool action; by comparison, the intended solution relies on this: resource-level policy checks verify that the caller can execute that exact action on that object; parsing ordinary prose to infer permission for a write is unsafe.

Question 114

A custom streaming client receives chunks that split JSON event payloads across network reads. Which implementation mechanism is needed?

  1. Parse SSE frames at event boundaries
  2. Associate deltas with their content block indices
  3. Negotiate supported content types properly
  4. Handle a disconnect during generation

Explanation

Correct Answer

A:

A buffered parser reconstructs complete event frames before decoding their data, subject to this requirement: treating every TCP chunk as one whole JSON object will fail unpredictably.

Incorrect Answers

B:

Block-index tracking assembles each text or tool input stream correctly; here, the controlling capability is that a buffered parser reconstructs complete event frames before decoding their data, but appending every delta to a single string can mix text with tool parameters.

C:

Content-type checks help the parser distinguish valid API data from an unexpected gateway body; the missing capability is more specific: a buffered parser reconstructs complete event frames before decoding their data; blind JSON parsing obscures transport failures.

D:

Stream lifecycle logic records interruption and avoids falsely marking partial output complete; by comparison, the intended solution relies on this: a buffered parser reconstructs complete event frames before decoding their data; the final message-stop signal has not been observed after a broken connection.

Question 115

A draft generator repeatedly confuses an executive summary with detailed action steps. Which mechanism should the team prioritize?

  1. Use application-controlled system instructions
  2. Give a correct representative example
  3. Include a counterexample with correction
  4. Provide contrastive edge-case examples

Explanation

Correct Answer

C:

Showing an unacceptable output and its corrected form highlights a specific formatting mistake; notably, a negative example without the correct alternative may create confusion.

Incorrect Answers

A:

The system-level field communicates application guidance separately from task content; however, the critical mechanism here is that showing an unacceptable output and its corrected form highlights a specific formatting mistake, and backend authorization still must be enforced in code and tools.

B:

A compact demonstration clarifies the intended input-to-output mapping; the requirement instead turns on this behavior: showing an unacceptable output and its corrected form highlights a specific formatting mistake; examples should match the required schema and not use private customer records.

D:

Distinct positive and near-miss cases teach the actual boundary between labels; in contrast, showing an unacceptable output and its corrected form highlights a specific formatting mistake, while repeating many easy cases offers little information about ambiguous ones.

Question 116

A tenant sends its same long template every hour, too slowly for some short-lived caches. What is the appropriate next design choice?

  1. Compare cache TTL with request arrival pattern
  2. Move unchanged long instructions into a shared prefix
  3. Read cache diagnostics when hit rate falls
  4. Include cache reads and writes in cost calculations

Explanation

Correct Answer

A:

Lifetime selection must account for actual reuse frequency and write overhead; its operational boundary is that a longer cache is not automatically economical for rarely repeated prompts.

Incorrect Answers

B:

Stable prefix design allows eligible prompt caching to amortize repeated input processing; this addresses a separate concern, not the fact that lifetime selection must account for actual reuse frequency and write overhead; putting request-specific content before a cache checkpoint defeats reuse.

C:

Cache usage metrics and prefix comparisons reveal the changed content causing misses; here, the controlling capability is that lifetime selection must account for actual reuse frequency and write overhead, but increasing the context window will not restore a mismatched cache prefix.

D:

Cache creation and cache retrieval have distinct billing treatment that affects economics; the missing capability is more specific: lifetime selection must account for actual reuse frequency and write overhead; treating every token as an uncached input misstates true spend.

Question 117

Engineers often trigger a specific changelog draft using the same prompt and arguments. Which production safeguard is most relevant?

  1. Use a custom client tool for a private business operation
  2. Create a project Skill for recurring checks
  3. Use a subagent for context-isolated auditing
  4. Use a custom command for a repeated invocation

Explanation

Correct Answer

D:

A command encapsulates a recognizable workflow entry point for interactive coding sessions, although it does not create a new callable external service by itself.

Incorrect Answers

A:

A user-defined tool schema plus local dispatcher safely bridges the model to that system; the missing capability is more specific: a command encapsulates a recognizable workflow entry point for interactive coding sessions; the developer must operate the function and enforce its permissions.

B:

Skill content packages reusable instructions and supporting guidance for the task; by comparison, the intended solution relies on this: a command encapsulates a recognizable workflow entry point for interactive coding sessions; the project must still provide actual tests and tools needed to perform the checks.

C:

A delegated worker returns focused findings while keeping its verbose exploration isolated; the needed capability is different—a command encapsulates a recognizable workflow entry point for interactive coding sessions—and separate context is not a substitute for least-privilege tool access.

Question 118

A server-sent event stream closes its logical response after all content blocks and message updates. How should this requirement be met?

  1. Inspect stop_reason before returning output
  2. Handle ping events without treating them as content
  3. Use message_stop as a stream completion signal
  4. Enable streaming to show output progressively

Explanation

Correct Answer

C:

The terminal event marks completion of the streamed message lifecycle, subject to this requirement: a ping or an individual content-block stop does not mean the entire response ended.

Incorrect Answers

A:

The completion reason tells the client whether to deliver, dispatch, or handle truncation; this cannot substitute for the behavior that the terminal event marks completion of the streamed message lifecycle, because treating all returned content as a complete final answer can hide partial results.

B:

Ping events maintain connectivity but do not represent assistant text to display; in contrast, the terminal event marks completion of the streamed message lifecycle, while showing keepalives as answer content would corrupt the rendered response.

D:

Streaming yields server-sent events as content is produced, improving time to first visible text; here, the controlling capability is that the terminal event marks completion of the streamed message lifecycle, but the client still needs to handle partial chunks and a final completion signal.

Question 119

A coding assistant is allowed to run commands unattended and the team needs to know which tools are permitted. Which engineering practice is the strongest match?

  1. Start a new session for an unrelated objective
  2. Limit shell command authority in automation
  3. Review effective settings before broad automation
  4. Use non-interactive print mode for CI automation

Explanation

Correct Answer

C:

Examining effective permission and hook configuration catches dangerous inherited allowances; in production, a printed prompt cannot override an enforced policy hierarchy.

Incorrect Answers

A:

A clean context prevents old task details from biasing the new investigation; here, the controlling capability is that examining effective permission and hook configuration catches dangerous inherited allowances, but shared persistent project guidance may still apply independently of session history.

B:

Restricted command/tool permissions reduce the possible effects of prompt errors or malicious code comments; the missing capability is more specific: examining effective permission and hook configuration catches dangerous inherited allowances; using a temporary checkout is helpful but does not itself revoke external credentials.

D:

Headless command-line invocation can run a prompt and return consumable output under controlled settings; the needed capability is different—examining effective permission and hook configuration catches dangerous inherited allowances—and CI still needs noninteractive credentials and appropriately limited permissions.

Question 120

An incident investigator uses vendor documents, some outdated and some containing embedded instructions to the assistant. Which TWO context-handling measures keep the documents useful as evidence without adopting their directives or stale claims? Choose TWO.

  1. Label external text as untrusted input
  2. Preserve immutable business facts in structured state
  3. Attach source IDs to retrieved excerpts
  4. Track source timestamps or versions
  5. Keep unresolved questions explicit

Explanation

Correct Answers

A:

Trust-boundary marking prevents source content from being promoted to application authority; labels should be backed by tool restrictions because prompts can be attacked.

D:

Version metadata allows the agent to prefer current evidence and flag historical material—with this limitation: timestamp alone does not establish which source is authoritative.

Incorrect Answers

B:

The application records authoritative facts outside model-generated summaries and supplies them when needed, whereas the requirement calls for another behavior: trust-boundary marking prevents source content from being promoted to application authority; conversation recollection can drift or omit earlier commitments.

C:

Citation metadata lets downstream logic connect statements to original retrieved material; however, the critical mechanism here is that trust-boundary marking prevents source content from being promoted to application authority, and without accurate source mapping, fabricated references can look convincing.

E:

Recording open issues prevents compaction from converting uncertainty into an invented guarantee; this cannot substitute for the behavior that trust-boundary marking prevents source content from being promoted to application authority, because suppressing gaps for a cleaner paragraph undermines factual reliability.

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