CCAO-F Practice Questions

Under the objective Differentiate between Claude model types (e.g., Haiku, Sonnet, Opus) and foundational AI capabilities, generative models are specifically optimized for natural language understanding, cross-document synthesis, and nuanced stylistic drafting.

Drafting audience-tailored, empathetic customer communications for human review (Option C) and synthesizing large volumes of complex source text into concise executive summaries (Option E) leverage Claude's extensive context window and linguistic fluency. Conversely, tasks requiring millisecond real-time event-driven streaming detection (Option A) or high-frequency deterministic quantitative financial settlement calculations on live feeds (Option D) are poorly suited for general LLMs and require specialized, deterministic streaming engines. Additionally, delegating final binding legal rulings entirely to an AI (Option B) represents an inappropriate governance risk.

Options A, B, and C are correct. The source document incorrectly instructed the reader to select two and omitted Option B, even though Anthropic explicitly recognizes tone and style as valid evaluation dimensions. The question has therefore been corrected to “Select three.”

Factual accuracy measures whether claims faithfully reflect the supplied sources. Style consistency evaluates whether the brief follows the organization’s established voice, terminology, and audience expectations. Format and length compliance determine whether Claude followed explicit deliverable constraints. Together, these criteria cover factual fidelity, audience suitability, and instruction adherence.

Option D is not a sound criterion because an external industry word-count benchmark may have no relationship to the actual business need. The relevant measure is compliance with the requested length and sufficient coverage of the required material. Option E is also invalid as written: an executive summary is required only if the task specification, template, or audience needs call for one. Automatically demanding it would evaluate an unstated requirement.

Anthropic’s evaluation documentation identifies task fidelity, relevance, tone and style, context utilization, and other task-specific success criteria as valid dimensions. It also stresses that criteria should be specific, measurable, achievable, and relevant. See Anthropic’s official evaluation guidance .

================

Under the objective Apply data, privacy sensitivity, regulatory policies, and privacy considerations , managing confidential or market-sensitive figures requires controlling memory persistence and data retention settings.

Pre-announcement financial figures represent material non-public information (MNPI) that must not persist beyond the immediate analytical session. Option E applies privacy controls by utilizing Incognito mode, which ensures the session does not contribute to long-term memory or persist in chat history. Option B achieves the same data protection control in standard chat by explicitly toggling off Memory contributions, ensuring the sensitive number is not saved into persistent memory where it could leak into future unrelated prompts. Conversely, proceeding with default settings (Option A), assuming brief discussions avoid retention (Option C), or enabling persistent memory retention for confidential figures (Option D) creates serious compliance and insider data exposure risks.

Under the objective Align model selection with task requirements (e.g., cost, speed, quality) , deploying models effectively requires matching model cognitive capacity to task complexity and throughput requirements.

Option C correctly routes complex, multi-layered tasks—such as synthesizing intricate legal precedents, statutory compliance, or multi-step policy analysis—to high-capability models (e.g., Claude 3 Opus or Sonnet) where deep reasoning is essential. Option E correctly routes simple, high-frequency, low-complexity tasks—such as standard FAQ lookups—to light, fast models (e.g., Claude 3 Haiku) to achieve ultra-low latency and minimal cost per request. Conversely, choosing models purely based on cost (Option A) is inefficient, deploying large frontier models for simple keyword extraction (Option B) wastes financial and rate-limit budgets, and assigning complex strategic synthesis across many documents to lightweight models (Option D) leads to shallow analysis and missed nuances.