Prompt Engineering & Structured Output: CCAR-F Study Guide

Answer: D. Set tool_choice to {"type": "tool", "name": "classify_ticket"}

any only guarantees that at least one tool is called, leaving the choice of which tool to the model, while {"type": "tool", "name": ...} forces one specific tool. Tool ordering does not change any's behavior, auto makes tool use optional rather than forced, and none prevents tool calls entirely regardless of prompt instructions.

Answer: B. Give each subagent a single tool (for example report_findings) whose input_schema is the desired output schema, and force it with tool_choice {"type": "tool", "name": "report_findings"}

Forcing a single tool whose input schema mirrors the desired output makes the model emit one schema-shaped object in the tool_use input, which is the documented tool-based path to structured JSON. Per-field tools fragment the result across multiple calls, prompt instructions alone cannot guarantee validity, and a prefill only continues from the end of the provided text, so the model cannot go back and overwrite placeholders inside a prefilled skeleton.

Answer: B. Validate each response against the JSON schema and, on failure, send a follow-up request containing the invalid output plus the specific validation errors, asking Claude to return a corrected object

Schema validation plus an error-informed retry loop is the standard reliability pattern when hard output constraints are unavailable: the model sees exactly what was wrong and can fix it deterministically. Substituting empty objects silently drops data, raising temperature reduces consistency without targeting the schema violation, and regex renaming cannot repair missing fields or invalid enum values reliably.

Answer: B. Generation was cut off at the token limit, leaving the JSON incomplete; raise max_tokens or stream

Structured outputs guarantees the JSON conforms to the schema only when the model finishes generating; a max_tokens cutoff truncates the output mid-object, producing unparseable JSON. The fix is to increase max_tokens (and stream for large outputs). Schema compilation happens before generation and would not produce a truncated body, and the guarantee explicitly does not hold when stop_reason is max_tokens.

Answer: C. Prefill the assistant turn with "{" so Claude skips the conversational preamble and continues directly with the JSON object

Prefilling the assistant message with an opening brace is the documented way to skip the preamble and force direct JSON output, because the response must continue from the prefilled character. Temperature controls randomness, not whether a preamble appears. A "{" stop sequence would terminate generation at the start of the JSON, the opposite of the goal, and the API performs no XML-based post-processing that strips prose.

Answer: D. Enclose each review in <review>...</review> tags and tell Claude to treat tagged content as data to analyze, not instructions to follow.

Delimiting the untrusted content with XML tags and telling Claude the tagged text is data-to-analyze makes it far less likely to act on instructions embedded in that data. Moving instructions, changing temperature, or prefilling doesn't establish the data/instruction boundary.

Answer: C. Including a few well-crafted example inputs and outputs directly in the prompt to steer Claude's format, tone, and structure

Multishot (few-shot) prompting means placing a few well-crafted examples in the prompt itself, which the docs call one of the most reliable ways to steer output format, tone, and structure. Re-running a prompt and comparing outputs is best-of-N verification, splitting work across calls is prompt chaining, and the Messages API has no parameter that returns multiple candidate completions.

Answer: B. Claude must actually output its reasoning in the response; without outputting its thought process, no thinking occurs

Anthropic's chain of thought guidance stresses always having Claude output its thinking, because without the thought process appearing in the output, no thinking occurs. That rules out silent internal reasoning while emitting a one-word reply. Manual CoT is a prompting technique that works without the extended thinking API feature, and CoT instructions work in user messages as well as system prompts.

Answer: A. Refactoring a large module with many interacting constraints and edge cases.

Extended thinking pays off on complex, multi-constraint problems where deeper reasoning helps, like a constraint-heavy refactor. Trivial edits gain nothing and just cost more thinking tokens and latency.

Answer: D. Code grading is fast and reliable but lacks nuance; human is nuanced but slow; LLM scales but needs validation.

The docs rank code-based grading (exact match, string match) as fastest, most reliable, and extremely scalable but lacking nuance; human grading as most flexible and high quality but slow and expensive, to be avoided when possible; and LLM-based grading as fast, flexible, and suitable for complex judgment once reliability is validated. The other options invert these tradeoffs: humans are the slow path, LLM grading exists precisely for nuanced judgments, and code rules cannot capture every subjective assessment.

Answer: C. end_turn: the model reached a natural stopping point and finished its response on its own.

end_turn means the model completed its turn naturally and the response can be used as-is. max_tokens signals the output hit the requested token cap (safety declines surface as the refusal stop reason), and tool_use means the model is requesting that your application execute a tool, not that execution already finished. stop_sequence indicates one of your custom stop_sequences was generated; rate limiting is reported as an HTTP 429 error, never as a stop_reason.

Answer: C. Most batches complete in less than 1 hour, but processing can take up to 24 hours, after which the batch expires.

The system processes each batch as fast as possible: most batches finish in under 1 hour, and results become available when all requests complete or after 24 hours, whichever comes first. Batches that do not finish within 24 hours expire. There is no scheduled nightly window, no 1-hour guarantee, and no unbounded processing.