Claude Certified Associate - Foundations (CCAO-F) Flashcards¶

120 minutes

60 multiple-choice and multiple-response

720 / 1000

$99 USD

12 months

Pearson VUE - online proctored or test center

people, companies, products. Claude can misattribute or misspell.

statistics, percentages, financial figures, dates. Verify against the source, and re-derive any arithmetic.

anything in quotation marks. Claude may paraphrase and present it as verbatim.

Claude can produce plausible-looking references to documents or pages that do not exist. Every citation gets clicked or looked up.

anything after the training cutoff needs a live source.

always confirm with the actual text or a qualified person.

which outputs need peer review, which need expert review, before they leave the team.

so reviewers know to check facts, not just style.

a summary shared without its source documents cannot be verified by the next person.

for regulated or high-stakes work, note who checked what. This connects to Domain 3 (auditability).

Claude drafts and checks, humans confirm (Domain 1).

hiring, firing, pricing approval, legal sign-off. Claude can prepare the analysis; a person decides.

unless a connector or upload provides it, Claude does not know your pipeline, inventory, or this morning's numbers.

use the analysis tool (real code execution) or a spreadsheet, not mental math in a chat response.

some client contracts and regulated processes do. Check first (Domain 3).

one-off tasks. If you notice the same chat being repeated weekly, that is a signal to promote it.

the home for any recurring workflow: standing instructions (how we write status reports), knowledge files (the template, last quarter's examples, the style guide), and shared access for the team on Team/Enterprise plans.

when the output is a document, a formatted report, or a small interactive tool that you iterate on. The Artifact panel keeps the deliverable separate from the conversation about it.

when the work already happens in another tool and copy-paste is the friction. Summarizing a channel discussion, drafting a reply where the thread lives.

when the workflow depends on live files or systems (a drive folder, a ticketing tool). Connectors let Claude read current data rather than stale uploads.

conceptually: the developer-focused agentic tool. If a scenario involves a software team automating engineering work, that is Claude Code territory; a business analyst writing a client summary does not need it.

hours per deliverable, turnaround time, backlog size.

review pass rate, edits required per draft, error escapes.

who uses the workflow, and whether usage sticks after week one.

verification steps completed, incidents (e.g., data pasted where it should not be).

some engagements require disclosure or prohibit AI use for certain work products. Check the contract or ask the engagement lead.

many organizations set disclosure rules for external content.

academic, journalistic, and regulatory contexts often have explicit rules.

what data classes may be used, on which plan, for which tasks; who approves exceptions.

work happens in the organization's Team/Enterprise workspace, not personal accounts. Admins manage access centrally.

people get the basics of prompting, validation, and data rules before heavy use.

defined in the workflow (Domain 2): what needs human review, what needs expert review.

for regulated or high-stakes work, keep a record: what was AI-assisted, what sources were used, who verified it. Enterprise-grade plans support organizational oversight; the team supplies the habit.

people know what to do if data goes somewhere it should not have (report it, do not hide it). Speed of reporting is what limits damage.

upload PDFs, Word docs, spreadsheets, slides; Claude reads and works over them. Long documents work, but focused inputs get more focused attention.

screenshots, whiteboard photos, charts. Claude can read, describe, and extract from them.

for real computation over uploaded data (sums, trends, charts), the analysis tool runs actual code. Prefer it over asking for arithmetic in prose.

for current information, ask Claude to search and cite sources; then verify the load-bearing ones.

ask for the output "as a document/artifact" when you want a deliverable to iterate on beside the chat.

the same prompting principles apply in every Claude app.

a fill-in-the-blanks version of a proven prompt, stored where the team works.

the durable parts of a prompt (role, style, process, format rules) moved into a Project so nobody retypes them.

the "what good looks like" samples stored once, applied to every chat in the Project.

"You help the Meridian account team produce weekly client status reports."

the steps to follow, what to ask for if inputs are missing.

the template to follow, length limits, section order.

audience and voice, with a line or two of example.

what not to do: "Never include internal cost figures in client-facing drafts."

this week's numbers go in the chat (or come via a connector); a stale file in knowledge produces confidently outdated answers.

knowledge is a curated shelf, not an archive. Irrelevant files dilute attention and can surface in answers where they do not belong.

the Domain 3 rules apply to knowledge files exactly as they apply to pasted text, and knowledge files persist and are shared, which raises the stakes.

one well-built Project (instructions + curated knowledge) raises the floor for the whole team; new members inherit the working setup on day one.

shared configuration is how a team gets consistent tone and format across ten authors.

a shared Project deserves a short "how to use this Project" note - itself a good first knowledge file.

"You help the team draft QBR narratives for client executives. Follow the structure in qbr-template. Tone: direct, evidence-led, no superlatives. Every metric must come from the data provided in the chat - if a number is not provided, mark it TBD rather than estimating. Never include internal margin data."

the QBR template, two exemplary past narratives, the client glossary.

monthly metrics (change every month - provided per chat), the client's raw contract (not needed - governance minimization).

provide the actual documents and instruct "use only these; say so if the answer is not in them".

ask Claude to summarize the current state, decisions, and constraints; carry that summary into a fresh chat.

if every draft needs the same three corrections, move those corrections into the prompt template or project instructions. The goal is a first draft that needs one review, not four rounds.

repeated context-pasting is a signal to create a Project (Domain 6).

a workflow running fine on the balanced tier does not need the flagship; a high-volume simple task may run better and cheaper on the fast tier (Domain 5).

it helps hard reasoning tasks and adds latency to easy ones; it is a dial, not a default.

focused excerpts often beat dumping entire documents; attention is a budget.

instructions like "flag any figure you could not find in the source" make outputs partially self-auditing, cutting review time (Domain 1).

time per deliverable and edits per draft before and after a change tell you whether an "optimization" actually helped (Domain 2).