Skip to content
CertLabs

CCAR-F

Five free CCA-F practice questions with worked answers

Key takeaways

  • Read five original worked examples across the CertLabs study topics, without an account.
  • These single-answer teaching examples are not official questions, a full exam simulation, or a readiness assessment.
  • Explain your choice before reading the answer; use the source links to investigate mistakes.

How to use these free samples

Choose an answer and explain your reasoning before reading the worked answer. These five original examples illustrate one decision in each CertLabs study topic. They are separate from the paid question bank and do not establish its coverage or quality. They are not official exam items, calibrated questions, a timed mock, or a prediction of passing. Real exam formats and requirements must be checked with Anthropic. No account or purchase is needed to read this sample.

Anthropic’s official exam guide includes multiple-choice and multiple-response items within scenario-based assessment. These five single-answer examples do not reproduce that full format. Source review: October 11, 2026.

Sample 1: Agentic architecture

A billing assistant uses the Messages API with a client-executed read_invoice tool. Claude returns stop_reason: "tool_use" and a tool request. The application has not executed it. What should happen next? Select one answer.

  • A. Treat the tool request as evidence that the invoice was read.
  • B. Wait for the API to execute this client tool automatically.
  • C. Check authorization, run the read, and return its result to Claude.
  • D. Discard the assistant response and ask Claude to guess the invoice.

Answer: C. Client tools run in your application. After checking caller and invoice access, preserve the assistant response and append a user message containing a tool_result with the matching tool_use_id, then continue. A confuses selection with execution; B assumes server execution; D loses the tool-call context and substitutes a guess. Handle failures and subsequent stop reasons explicitly.

Source: How tool use works.

Sample 2: Tool authorization

A refund tool receives schema-valid arguments for order 42. The authenticated caller may view this order but may not issue refunds. Which control must reject the action before a refund occurs? Select one answer.

  • A. The application’s authorization check for caller, order, and refund action.
  • B. A tool description asking Claude to use refunds responsibly.
  • C. A JSON schema checking that the order ID is an integer.
  • D. A model explanation saying the request appears reasonable.

Answer: A. This scenario’s policy belongs at the execution boundary, including any backend authorization service. B is guidance; C checks input shape; D is generated reasoning. None establishes the caller’s refund authority. Returning a denial lets the assistant explain the outcome without performing the prohibited action.

Source: Tool-use execution contract. The authorization placement is an application-design conclusion from the stated policy.

Sample 3: Claude Code workflows

A team puts “do not read deployment credentials” in a Markdown rule under .claude/rules/, scoped with paths. They need an enforced restriction on access to those credentials. Which approach addresses that requirement? Select one answer.

  • A. Repeat the sentence in every path-scoped rule.
  • B. Rename the rule so it sorts after all other rules.
  • C. Expand the rule’s paths to match the credential files.
  • D. Configure access restrictions and keep credentials outside the agent’s accessible environment.

Answer: D. Path-scoped rules control when instructions load; they do not grant or deny file access. Use the relevant permission controls and a credential-isolation boundary appropriate to the environment. A and B change instruction presentation. C changes rule scope. None turns prose into an enforced access restriction; check all tools and execution paths when configuring a boundary.

Sources: Project memory and scoped rules, Claude Code permissions. Credential isolation is a design recommendation.

Sample 4: Prompt design and structured output

A shipping extractor returns schema-valid JSON containing a delivery date, but the supplied receipt has no delivery date. The application must preserve missing information rather than invent it. Which change addresses the problem? Select one answer.

  • A. Require every date value to be a string.
  • B. Allow an explicit unknown value and validate extracted dates against source evidence.
  • C. Repeat the field name at the end of the prompt.
  • D. Accept any result produced with strict schema constraints.

Answer: B. Make the output contract admit missing information, such as null, and check whether a claimed date is supported. A constrains type without establishing a fact. C may influence the response but adds no evidence check. D confuses structural validity with source support. Structured output helps enforce the supported schema; the application still needs semantic validation.

Source: Structured outputs. The evidence check follows the scenario’s extraction requirement.

Sample 5: Context management and reliability

After conversation compaction, an assistant’s summary says a spare part was available yesterday. Before offering it today, business policy requires a current inventory check. Which next step satisfies the policy? Select one answer.

  • A. Use yesterday’s quantity because it survived compaction.
  • B. Increase the context window to make the old quantity current.
  • C. Perform an authorized inventory read and handle a failed read as unresolved availability.
  • D. Rewrite the summary to describe the quantity as confirmed today.

Answer: C. Compaction summarizes conversation history; it does not refresh inventory. A retains stale evidence, B changes capacity, and D changes wording without observation. A successful read reporting no stock differs from a failed read that establishes nothing about stock. This freshness requirement comes from the stated business policy, not an automatic compaction feature.

Sources: Compaction overview, Tools for fresh external data.

Put the concepts into practiceReview course access

What practice can tell you

A practice session gives evidence about the questions you answered in that session. It can reveal a topic to revisit, an unfamiliar term, or an assumption you should test in a small project. It does not measure everything that may appear on a certification exam. CertLabs does not claim that its question bank reproduces the official exam or that a particular percentage guarantees passing.

A useful way to review each answer

Before viewing the explanation, write down why you chose the answer and how confident you are. After reviewing it, compare the assumptions behind your choice with the scenario. Ask whether an alternative would work under a different constraint.

Check the linked primary documentation when the question depends on a changing product feature. For example, distinguish an application-managed client-tool loop from an Agent SDK workflow. Do not treat a remembered answer letter as evidence that you understand that distinction.

Turn errors into practical work

Choose one missed concept and design a short exercise that would expose the same mistake. If you confused missing data with an unavailable dependency, create both outcomes in a synthetic tool. If you relied on a prompt for access control, inspect the application’s actual authorization boundary.

Repeat a changed version of the exercise after a delay. Keep a record of the concept and the evidence that resolved it, rather than copying an answer key. This gives you a more useful study log than a list of percentages alone.

Understand the study experience

CertLabs schedules reviews using your recorded practice history. A saved review and its schedule are confirmed together, and uncertain submissions can be retried. Placement may be unavailable when a course lacks suitable assessment data; in that case you can continue into ordinary study.

Practice progression uses course/domain evidence, coverage, and review history. A quiet week is not automatically poor performance. These measures help organize practice; they do not predict an official exam result. Review current availability, price, and access duration on the order-review page before purchasing.

Sources and review

Source links checked 2026-10-11. These exercises are independent CertLabs preparation, not official exam questions or a prediction of passing.

Continue exploring