CCAO-F Anthropic Claude Certified Associate - Foundations Free Practice Exam Questions (2026 Updated)

Answer A is correct. The pattern shows inconsistent compliance with requirements that should have been stated explicitly: the audience, tone, output structure, and mandatory sections. If those requirements are vague or implied, Claude may emphasize different aspects of the request across runs, especially as the weekly source content changes. The first troubleshooting step should therefore be to inspect the prompt and convert each expectation into a clear, testable instruction.

Option B is incomplete. Model outputs can vary, but non-determinism should not be used to excuse recurring failures to satisfy defined requirements. Strong prompts and evaluation criteria can substantially reduce unacceptable variation. Option C is less likely because the weekly inputs follow the same structure; changing facts alone should not cause required sections or tone instructions to disappear. Option D adds unnecessary workflow complexity. Claude can follow tone and structural requirements within one prompt when those requirements are clearly separated and explicitly defined.

The prompt should identify the intended audience, prescribe the tone, list every required section, specify the output format, and state that no section may be omitted. Anthropic recommends clear, direct instructions and precise output constraints, particularly when order or completeness matters. Anthropic prompting best practices

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

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.

Option C is correct because an Artifact is designed for substantial, self-contained output that users need to inspect, edit, preview, and refine separately from the surrounding conversation. A landing-page prototype—particularly one containing HTML, CSS, JavaScript, or an interactive component—is more usable in a dedicated Artifact workspace than as code buried inside a chat response.

Artifacts support iterative development. The product manager can ask Claude to change the layout, copy, colors, component behavior, or responsive structure while maintaining a recognizable working version. The resulting prototype can also be reviewed or shared more effectively because it is presented as a distinct deliverable rather than as part of the conversation transcript.

Option A is a research workflow and would be appropriate for gathering sourced information about competitors, not for producing the prototype itself. Option B provides no dedicated editing or preview environment and makes repeated revisions harder to manage. Option D could preserve recurring instructions and reference materials, but a Project is a contextual workspace rather than the output format for the prototype.

A Project and an Artifact can be used together: the Project supplies persistent product requirements and design references, while the Artifact contains the actual prototype that the team iterates on.

Answer C is correct. Increasing use of outdated terminology, sources, or guidance directly indicates that the Project’s configuration or knowledge base no longer represents current business practice. Claude Projects use uploaded documents, contextual material, and Project instructions to guide responses across chats. When those inputs become obsolete, the resulting outputs can remain internally consistent while still being operationally inaccurate. The manager should review the Project instructions, replace outdated knowledge files, remove conflicting material, and test the revised configuration against representative workflow tasks.

Option A may reflect seasonal demand, reduced workload, or declining adoption; it does not directly demonstrate a configuration defect. Option B is also inconclusive because longer responses may result from changing task complexity or user preferences. Option D deserves investigation because users may be bypassing the Project due to usability or quality concerns, but it could equally result from habit, convenience, or insufficient training. By contrast, outdated references provide direct evidence that the Project’s grounding information needs maintenance. Anthropic describes Projects as self-contained workspaces whose uploaded knowledge and instructions provide context and tailor Claude’s responses. Those resources must therefore be reviewed and updated when organizational practices change. Anthropic: What are Projects?

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

Under the objective Adjust approach based on feedback and results, iterative refinement requires tight, closed feedback loops characterized by concrete observation, targeted modification, and empirical evaluation.

Option A details the gold-standard iteration cycle: capturing specific, granular defects immediately following an execution run (e.g., tone misalignment, omitted edge cases, formatting errors), translating those observations into targeted, discrete adjustments in prompt instructions or workflow logic, and validating whether subsequent outputs resolve the issue without regressions. In contrast, deferring feedback collection across multiple unmonitored cycles (Option B) delays error detection. Relying solely on high-level aggregate numerical ratings (Option C) lacks the actionable diagnostic detail needed to locate root causes. Applying sweeping, unfocused prompt overhauls (Option D) obscures cause-and-effect relationships and frequently introduces new failure modes.

The phrase “well-known industry standard” is not evidence. Without the name of the standard, its issuing body, version, publication date, or an authoritative citation, the statement cannot be independently verified. Option D correctly treats the assertion as unsupported and requires either authoritative substantiation or removal.

Claude can produce fluent, confident language that appears credible even when the underlying claim is incomplete, inaccurate, or fabricated. Adding stronger language, as proposed in Option A, would amplify the unsupported claim rather than correct it. Options B and C confuse plausibility and confidence with verification. A claim does not become reliable merely because it sounds familiar or uses reassuring terminology.

The reviewer should identify the purported standard, locate the original issuing organization or official publication, confirm that the standard applies to the subject and jurisdiction, and cite the relevant section. If those checks cannot be completed, the claim should be deleted or rewritten to disclose uncertainty. Anthropic recommends grounding factual statements in direct source material, using citations to make claims auditable, and retracting claims for which supporting evidence cannot be found. This approach directly addresses hallucination risk while preserving the brief’s credibility. Anthropic’s hallucination-reduction guidance

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

Under the objective Identify, diagnose, and resolve issues with underperforming prompts and/or poor outputs, workflow optimization must be rooted in evidence-based diagnostics before making modifications to system instructions or prompt chains.

The diagnostic phase requires two prerequisite steps: establishing a quantitative baseline by measuring quality metrics, latency, token spend, and human intervention frequency across recent historical runs (Option D), and conducting a bottleneck analysis to pinpoint the exact sub-steps responsible for performance degradation, excessive token cost, or quality defects (Option B). Implementing changes without these baseline diagnostics leads to blind iterations. Deployment (Option C) and SOP updates (Option E) are downstream execution phases, while leadership notifications (Option A) occur after solutions are verified.

Option C is correct because a Claude Project is a persistent workspace whose instructions and knowledge influence multiple chats. Anthropic explains that Project instructions tell Claude how to behave and respond across the Project, while uploaded knowledge is made available as context across its chats. Consequently, outdated policies, terminology, templates, or reference documents can systematically influence future outputs even when the degradation is not immediately obvious.

A sensible maintenance practice is to review the configuration periodically and whenever a meaningful source, policy, workflow, audience requirement, or organizational standard changes. Updates should then be tested against representative tasks and defined success criteria. Option A is too reactive because waiting for visible failure may allow inaccurate or obsolete outputs to circulate. Option B is incorrect because chat-level corrections do not reliably repair the persistent instructions or knowledge used in other Project chats. Option D is also too rigid: review can occur on a schedule, but changes should be evidence-based rather than made automatically when nothing relevant has changed.

Therefore, the best practice is controlled, periodic review combined with change-triggered maintenance and validation. This keeps the Project aligned without introducing unnecessary configuration churn. See Anthropic’s guidance on creating and managing Projects and building evaluations.

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

Answer A follows the strongest ethics-review dependency order. First identify the audience and the potential consequences of the deliverable (3), because ethical risk depends on who receives the material and how it may affect them. Next examine the content for unsupported generalizations, fairness problems, and accuracy defects (5). With the audience and substantive risks understood, confirm that the necessary transparency or disclosure requirements are met (1). Then correct the deliverable or escalate concerns that exceed the reviewer’s authority (4). Finally, record the review result and all changes made (2), preserving accountability and traceability. The resulting sequence is 3, 5, 1, 4, 2. Option B checks transparency before completing the substantive ethics assessment; Options C and D begin without first establishing the affected audience and impact. Anthropic’s AI Fluency framework treats Discernment as critical assessment of AI output and Diligence as responsible, ethical use with human accountability. Anthropic’s Usage Policy likewise emphasizes human review and disclosure for high-risk uses. Therefore, an ethics review should move from impact framing, through content assessment and transparency, to remediation and documentation—not merely confirm that an AI disclosure exists and assume the deliverable is safe. Anthropic AI Fluency course, Anthropic Usage Policy

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

Options B and E apply organizational governance and data-minimization requirements before the file enters Claude’s execution environment. The associate must first establish whether Code Execution is an approved processing method for the file’s classification. If the information exceeds the approved sensitivity level, the user must escalate to privacy, security, legal, or another designated authority rather than proceeding independently.

The file must also be inspected for customer identifiers, confidential fields, regulated information, credentials, or data unrelated to the calculation. Unnecessary fields should be removed, redacted, or anonymized. A sandbox limits interaction with the surrounding system, but it does not change the sensitivity of uploaded data, provide authorization, or override the organization’s handling rules. Therefore, Options C and D incorrectly treat technical isolation as a governance exemption. Option A allows urgency to displace mandatory review.

Anthropic explains that Code Execution runs in an isolated container, while also warning that file-processing configurations and network access create security considerations. Its privacy guidance recommends careful treatment of highly sensitive personal and confidential information. The correct control is to minimize and authorize the data before uploading it, not rely solely on the sandbox afterward. Anthropic’s Code Execution security guidance

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

Answers B and C are the two acceptable use cases as written. Drafting an internal training summary from approved documentation is a bounded synthesis task grounded in authorized sources. Synthesizing themes from approved customer feedback under established aggregation rules is likewise a controlled analysis task, provided the data handling follows organizational privacy requirements. Both activities support human work without assigning Claude a consequential decision about an individual. Option D feeds performance-review information into a promotion process, an employment-related high-risk domain requiring formal controls and accountable human judgment. Options A and E involve healthcare and legal work. Anthropic’s current Usage Policy does not categorically ban those domains, but it requires qualified professional review for high-risk advice or decisions and requires disclosure when outputs are presented directly to consumers. The brief wording in A and E mentions professional review but does not establish the complete safeguards, authorization, privacy handling, or disclosure needed to treat the workflow as approved. Therefore, they are not unconditionally acceptable “as stated.” Anthropic’s AI Fluency Delegation principle also requires considering consequences, reversibility, and the human capabilities that must remain in the process. B and C are the only choices that fully specify low-risk, policy-bounded knowledge work without relying on unstated safeguards. Anthropic Usage Policy

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

Options A and D are correct because Connector authorization creates a security and data-governance boundary. Before connecting a service, the team must confirm that the provider is trusted and approved under organizational vendor-management requirements. It must also determine what data Claude could access, how that data is classified, and whether the proposed users have legitimate permission to use it.

Anthropic explains that Connectors can retrieve data and take actions in connected services. Claude inherits the user’s source-system permissions, while custom Connectors may connect to services that Anthropic has not verified. Anthropic therefore advises users to connect only to trusted servers, carefully review requested permissions, minimize unnecessary scopes, and remain aware that connected tools may read, modify, or delete data. These considerations directly support approved-vendor and data-authorization checks.

Training may be necessary before rollout, but it does not have to be completed before the authorization decision itself. Decommissioning legacy Connectors and migrating reports are implementation or lifecycle activities that ordinarily follow approval and transition planning. They do not replace the initial trust, classification, and permission assessment. Therefore, A and D are the required pre-authorization controls. See Anthropic’s Connector overview and custom Connector security guidance.

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

Under the objective Leverage Claude for research, planning, and process optimization, effective AI-assisted research workflows follow structured problem decomposition principles.

Before interacting with the model or executing information retrieval prompts, the researcher must clearly frame the investigation by defining specific, bounded research questions and target hypotheses (Option D). Defining explicit dimensions—such as market size, competitor landscape, target customer personas, and regulatory barriers—provides the foundational framework needed to engineer targeted prompts. Submitting open-ended prompts without explicit research objectives (Option B) produces unfocused, verbose outputs. External validation (Option C) and final report synthesis (Option A) occur downstream after structured research has been executed.

Under the objective Manage uploaded knowledge and connectors (e.g., Google Drive, Gmail), establishing data connectors requires adhering to the principle of least privilege, strict scope boundary management, and robust data classification.

Option B is an authorized, safe integration: connecting Claude to an approved, bounded project management workspace with explicit scope controls allows the model to summarize tasks and sprint updates safely. Option D is an ideal read-only integration, granting access to public documentation and reference repositories where confidential data leakage risks are zero. Conversely, connecting AI tools to core payroll infrastructure (Option E) or sensitive personnel/HR databases (Option A) introduces severe compliance, privacy, and unauthorized access liabilities. Linking personal cloud storage repositories containing unvetted mixed personal data (Option C) violates data governance standards by risking unintentional exposure of private files.

Under the objective Evaluate Claude-generated outputs for accuracy and completeness, quality assurance involves auditing both macro-level structure (presence of required topics) and micro-level depth (thoroughness against detailed specifications).

The report successfully includes all five mandatory high-level headings, satisfying basic structural completeness. However, evaluating the internal substance of the renewal-risk section reveals an under-scoped deliverable: the specification required analyzing three distinct dimensions (pricing, product fit, and stakeholder change), but Claude addressed only one. Therefore, Option D is the accurate assessment: the artifact fulfills topical scope but lacks required operational depth and must be expanded prior to client delivery. Claiming it completely satisfies requirements (Option C) ignores explicit criteria, while labeling the entire section missing (Option B) or offloading internal QA to the customer (Option A) violates quality management standards.

Under the objective Understand ethical implications of AI usage and the AI Fluency Framework Delegation competency, determining autonomous task suitability depends on assessing human consequence, ethical responsibility, and legal accountability.

Hiring decisions directly impact individuals ' careers, livelihoods, and civil rights, carrying substantial legal, moral, and organizational consequences. Delegation principles strictly classify autonomous employment, promotion, and termination determinations as non-delegable tasks that must remain under human ownership (Option A). Human judgment, context discernment, and legal accountability cannot be offloaded to an algorithmic model. Sample-based after-the-fact reviews (Option B) or delegating fully in pursuit of processing efficiency (Option C) violate responsible AI governance. Furthermore, classifying the prohibition as merely an issue of system technical reliability (Option D) ignores the fundamental imperative of ethical and human accountability.

Under the objective Adapt prompting strategies based on task type (e.g., analysis, research, drafting, brainstorming), prompt architectures must be tailored to the exact analytical objective established during discovery.

Because the clarified objective is to generate an actionable, evidence-based competitor pricing briefing (rather than creative ideation), the workflow demands a structured research and synthesis strategy (Option C). This approach directs Claude to extract concrete pricing data across key competitors, explicitly attribute claims to named source documents or market reports, and transparently state confidence levels for each datapoint. Divergent brainstorming (Option A) produces speculative ideas when factual market intelligence is needed. Arbitrarily restricting analysis to a single competitor (Option B) ignores the broader competitive landscape. Relying on unstructured open conversation (Option D) produces inconsistent formatting unsuitable for executive decision-making.

Under the objective Create effective prompts for business and technical tasks, prompting Claude for complex analysis requires clear framing, explicit task decomposition, and structural schema constraints.

Transcripts from 90-minute interviews contain unstructured, conversational discussions spanning multiple priorities, assumptions, and debates. Providing the raw source material alongside a structured schema—specifying categories such as must-haves, nice-to-haves, unresolved open questions, and stakeholder conflicts (Option A)—enables Claude to parse and categorize information accurately without losing critical context. In contrast, forcing a single flat list (Option B) flattens priority nuances and obscures conflicts. Summarizing first (Option C) introduces unnecessary loss of detail and risks compounding omissions in the second pass. Parsing every statement containing a verb (Option D) creates extreme token noise and unworkable overhead.

An evaluation cannot be applied consistently until the organization defines what the output must achieve and what score constitutes an acceptable result. Therefore, the evaluator must first define task-specific criteria, such as factual accuracy, completeness, relevance, tone, format compliance, privacy preservation, or citation quality. The evaluator must then establish a threshold or decision rule that separates acceptable from unacceptable performance.

Anthropic’s evaluation guidance states that successful AI applications begin with clearly defined success criteria followed by evaluations that measure performance against those criteria. Effective criteria should be specific, measurable, achievable, and relevant to the application’s purpose. A threshold converts those criteria into an operational decision—for example, requiring all material claims to be supported or setting a minimum score across defined dimensions.

Options A, D, and E occur after evaluation. Promotion into production follows an acceptable result. Escalation to a senior reviewer occurs after an output fails or presents elevated risk. Recording the final score and reviewer comments also follows the scoring activity. Without B and C, different reviewers could apply inconsistent standards or approve an output without knowing what “acceptable” means. Anthropic’s evaluation guidance

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