Capstone Exam Simulation (AIF-C01)
Simulate the real AWS Certified AI Practitioner exam: official logistics and question formats, a 90-minute clock strategy, distractor decoding, a 15-item Set A with a domain-organized answer key, a scoring rubric, a weight-driven 40-hour study plan, and a synthesis of lessons 01-15.
100 min
Answer every question, you can navigate freely and the timer counts down.
Fifteen lessons gave you the content. This one gives you the container: how the AIF-C01 is actually built, how it is scored, how the clock behaves, and how AWS-style distractors are engineered. Everything before this lesson was domain knowledge; everything here is test craft, and on a compensatory 100-1,000 scale with 700 to pass, test craft is worth as much as another hour of revision.
=====================================================================
AIF-C01 EXAM AT A GLANCE (verified 06 Oct 2026)
=====================================================================
FORMAT ....... 65 questions = 50 scored + 15 unscored (never marked)
TIME ......... 90 minutes = 5,400 s -> ~83 s per item (derived)
SCALE ........ 100-1,000, pass at 700, COMPENSATORY, no section cut
GUESSING ..... no penalty for a wrong guess; BLANK = wrong
TYPES ........ multiple choice / multiple response / ordering /
matching (the current guide lists four types)
WEIGHTS ...... D1 20% | D2 24% | D3 28% | D4 14% | D5 14%
COST ......... 100 USD (local table applies; tax may apply)
VALIDITY ..... 3 years; retake after a fail waits 14 days, no cap
DELIVERY ..... Pearson VUE test center or online proctored
RESULTS ...... official ceiling 5 business days
=====================================================================How to use this lesson. Read sections 1 to 6 once, then sit Set A (section 7) under a 15-minute timer with no notes. Grade yourself with section 8, convert the raw score with the rubric in section 9, and let section 10 tell you which lessons to reopen. Anything this lesson could not verify against a first-party AWS page is listed in section 12: treat those as do not assert, not as facts to memorize.
By the end of this lesson you will be able to:
- state every published logistics fact (question count, time, scale, cost, validity, retake rules) with its source;
- explain the four official question types and what each one demands of your time budget;
- run a 90-minute clock plan that never leaves an item blank;
- decode the six distractor families AWS uses on this exam;
- allocate 40 study hours across the five domains by their published weights;
- grade Set A honestly, fix the weakest domain first, and defend the comparative verdict on domain weighting;
- say what the exam does not publish, so you never assert an invented number.
1. Exam logistics: what AWS publishes
1.1 The facts, each with its source
Nothing in this table is folklore. Each row comes from the current exam guide (v1.1, published 30 April 2026), the AIF-C01 certification page, or the AWS certification policies and FAQ pages as retrieved in October 2026.
# | Fact | Source |
|---|---|---|
1 | 65 questions: 50 scored + 15 unscored pretest items, and the unscored items are not identified | Exam guide v1.1 |
2 | 90 minutes to complete the exam | Cert page + exam guide |
3 | Pass/fail result on a scaled 100-1,000 range; minimum passing score 700 | Exam guide |
4 | Scoring is compensatory; there is no per-domain pass mark; the report may show section classifications | Exam guide |
5 | Unanswered items are scored as incorrect. There is no penalty for guessing. | Exam guide |
6 | Question types: multiple choice (1 correct, 3 distractors), multiple response (all correct required), ordering (order matters), matching (all pairs) | Exam guide |
7 | Domain weights: D1 20 %, D2 24 %, D3 28 %, D4 14 %, D5 14 % | Exam guide |
8 | Cost 100 USD; local table (EUR 85, AUD 150, JPY 15,000, KRW 131,525, CNY 704, INR 8,553); tax may apply; prices reset each April | Cert page + before-testing policy |
9 | Certification is valid 3 years; recertify by re-passing or by earning ML Engineer - Associate (which auto-recertifies) | Cert page + FAQ |
10 | Delivery: Pearson VUE test center or online proctored; English proctoring is offered 24x7 | Cert page + before-testing policy |
11 | 12 languages listed (AR, EN, FR, DE, IT, JA, KO, PT-BR, ES-LatAm, ES-ES, zh-Hans, zh-Hant); Italian and German retire after 15 Oct 2026 | Cert page |
12 | After a fail: wait 14 days, no attempt cap, full fee each attempt; after a pass, the same exam is locked for 2 years | After-testing policy + FAQ |
13 | Results published within 5 business days (official ceiling) | FAQ + before-testing policy |
14 | Reschedule up to 24 hours before, maximum 2 changes (a third means cancel and rebook) | Before-testing policy |
15 | Target candidate: up to 6 months of AI/ML exposure; uses AI/ML but does not necessarily build it | Exam guide |
16 | Guide versions: v1.0 26 Mar 2026, v1.1 30 Apr 2026; guide updates reach the exam about 1 month after publication | Revision page |
17 | English exam plus ESL accommodation = +30 minutes (wording conflicts across pages; see section 12) | FAQ |
18 | The in-scope services list is non-exhaustive and subject to change; only domain weights are published | In-scope page + exam guide |
- π Did you know? The 15 unscored items look exactly like the 50 scored ones. AWS does not tag them, colour them or otherwise separate them; which means the only rational strategy is to treat every item as scored. A pretest item you answer badly costs you nothing, and a scored item you skip costs you the full marks, so the incentive never points toward "leaving it for later and never coming back".
1.2 The four mechanics that decide your score
Read these four sentences as the operating system of the exam:
- Compensatory scoring means a brilliant Domain 3 cannot rescue a weak Domain 4. You do not need to be great everywhere; you must not be bad anywhere.
- No guessing penalty means a blank is strictly worse than a guess: guessing is never a risk, it is free expected value.
- Hidden pretest items mean your raw count of "obviously right" answers maps to a scaled score you cannot see, so never compute a pass from "X of 50".
- Only domain weights are published: per-objective weights do not exist, so any study plan built on "this topic is 8 %" is built on a guess.
1.3 Booking, delivery, retake and results
The administrative half of the exam is examinable in the sense that it changes how you plan your attempt, so treat it as a small checklist rather than trivia:
Situation | The rule | Practical consequence |
|---|---|---|
Choosing a venue | Pearson VUE test center or online proctored | Online English proctoring runs 24x7; a test center needs a slot and a valid ID |
Rescheduling | Up to 24 h before, maximum 2 changes | A third change means cancel and rebook: decide before the final day |
Failing | Wait 14 days, no attempt cap, full fee every time | Budget the second attempt before you take the first |
Passing | Same exam locked 2 years; earning ML Engineer - Associate recertifies | You cannot re-sit the same exam to "refresh" it early |
Results | Published within 5 business days | Plan a quiet week; do not refresh the dashboard hourly |
Validity | 3 years from the pass date | Diary the expiry date on the day you pass |
Accommodations | English exam + ESL accommodation = +30 min (wording differs across pages; see section 12) | Apply well in advance, not the week of the exam |
Price changes | Costs are re-published around each April | Re-check the official price page before paying |
A scheduling detail candidates forget: the exam is delivered as 65 questions in 90 minutes regardless of venue, and the proctor rules (no scratch paper policy variants, camera rules, room scans) apply before the clock starts. Arriving with two minutes to spare costs you nothing; arriving flustered costs you the first three items.
2. Question formats and what each one costs you
2.1 The official types
Type | Structure | All-or-nothing rule | Typical time | Where it hurts |
|---|---|---|---|---|
Multiple choice | 1 correct + 3 distractors | Pick the single best answer | 45-75 s | Distractor engineering |
Multiple response | 2+ correct among 5+ options | All correct must be selected; no partial credit | 75-120 s | Missing a fifth option |
Ordering | 3-5 items in the correct sequence | Correct and in order or zero credit | 60-100 s | One swap ruins the item |
Matching | 3-7 prompts, each with its partner | All pairs correct | 90-150 s | Slowest format; errors compound |
All 15 items in Set A are multiple choice, which is the format you can drill fastest. The live exam adds the other three in unpublished counts (see section 12), so practice them as skills, elimination, sequencing, pair-checking, rather than as a predictable quota.
2.2 The arithmetic of the clock
Against scored items only, the budget looks like s, but you cannot tell which 50 are scored, so 83 s is the number you plan with. A first pass at 60 s per item leaves 25 minutes for flags, ordering and matching, which is where the slow formats and the second-guesses live.
- π Did you know? Two stalls of three minutes each erase six minutes; that is seven multiple-choice items you will have to answer in the last third of the exam at double speed. The exam does not reward depth on one item; it rewards coverage of all 65, because coverage is the only way to guarantee you never convert a knowable item into a blank.
2.3 Attacking the three formats Set A does not contain
Set A trains the single-best-answer muscle. The live exam adds three formats whose failure modes are different, so practise the procedure even though you cannot predict the quota:
Format | The procedure that maximises credit | The mistake that zeroes it |
|---|---|---|
Multiple response | Read every option, mark each as definitely yes / definitely no / maybe, then submit only when every "maybe" has been resolved: all correct options are required | Selecting two obvious answers and skipping the fifth correct one; assuming partial credit exists |
Ordering | Fix the anchors first (the step that must be first, the one that must be last), then arrange the middle; re-read the sequence as a sentence | Rearranging after you have a valid order "because it looks better" |
Matching | Eliminate the pairs you are certain about first: each settled pair shrinks every remaining option list | Starting with the hardest prompt, which leaves all distractors in play |
A useful habit: in matching, the longest right-hand side is often the most specific and therefore the least likely to be a distractor, but verify it against the domain knowledge rather than guessing from length alone. In ordering, if two adjacent steps could swap without changing meaning, the stem is usually telling you the criterion (by time, by dependency, by cost): find it and apply it consistently.
3. Exam-day strategy: the 90-minute clock
3.1 The phase plan
Phase | Clock | Minutes | Rule you must not break |
|---|---|---|---|
First pass (all 65) | 0:00 - 1:05 | 65 | ~60 s per item; flag anything over 90 s; answer every item |
Flagged review | 1:05 - 1:18 | 13 | Re-read the stem and confirm you answered the asked question, not the adjacent one |
Ordering / matching buffer | 1:18 - 1:27 | 9 | Do these after single-answer items; they are slower and all-or-nothing |
Submit sweep | 1:27 - 1:30 | 3 | Confirm zero blanks: a blank is a guaranteed zero |
Guess rule (any time) | any | - | Down to two? Pick the most specific, AWS-native, least absolute option |
Trap rule (any time) | any | - | "Always", "never", "guarantees", "eliminates hallucination" absolutes usually lose |
Cost rule (any time) | any | - | Prefer the simplest managed answer unless the stem demands control |
How to answer
Ordering exercise with 4 items. Move them into the correct order, then check your answer.
Order the four timed phases of the 90-minute AIF-C01 clock:
3.2 Worked example 1: where the time goes
5,400 seconds across 65 items is about 83 seconds each. Plan 60 seconds for the first pass (65 minutes), which leaves 25 minutes: 13 for flagged items, 9 for ordering and matching, 3 for the final sweep. If two items consume three minutes each, you have spent six minutes of your review budget, so the correct move is always flag, guess, move, never "one more careful read".
3.3 Worked example 2: the guess protocol
There is never a reason to leave an item blank. The protocol that keeps guessing disciplined:
- Predict the answer from the stem before you read the options; it stops the distractors from anchoring you.
- Eliminate two options and write a one-line reason for each (wrong layer, wrong rung, wrong family, over-scoped, absolute wording).
- If two remain, choose the one that is most specific, most AWS-native and least absolute.
- Move within 60 seconds. Four minutes on one item is four items lost elsewhere.
4. Decoding the distractors
AWS does not write random wrong answers. It writes plausible near-misses that punish a specific confusion, and the same six families repeat across all five domains.
Distractor family | The pattern | Your counter-move |
|---|---|---|
Wrong layer | Config / CloudTrail / Artifact offered as a protective control | Ask: must this prevent, detect or prove? |
Wrong rung | "Fine-tune the model" for fresh facts or a formatting tweak | Walk the ladder: prompt β RAG β fine-tune |
Wrong family | Textract for sentiment, Comprehend for OCR | Map the verb to the service before reading the rest |
Over-scoped | AdministratorAccess, s3:*, "share one key with the team" | Demand resource-ARN scoping and least privilege |
Absolute wording | "guarantees", "100 %", "eliminates hallucinations" | Prefer hedged, evidence-based wording |
Out-of-scope service | A legacy service presented as the answer | Check the current in-scope list; never build a key on it |
4.1 Worked example 3: elimination that survives contact with the options
A fraud model's false negatives cost 50x a false alarm. Which metric do you prioritize?
- Accuracy dies: majority-class inflation makes it meaningless under heavy imbalance.
- Precision dies: it penalizes the cheaper error, so it optimizes the wrong side of the ledger.
- R-squared dies: it is a regression metric and this is a detection problem.
- Recall survives: , and minimizing false negatives is exactly what the stem asks for.
Test every option against the stem's pain, not against general goodness: each option must answer the specific thing that hurts.
4.2 Worked example 4: what "700" actually means
Exam forms are equated, so AWS never publishes how many of the 50 scored items equal 700: any "35 of 50 = pass" claim is unsourced (section 12). What you can act on: compensatory scoring means a soft Domain 4 still sinks you, so target >= 80 % on mixed practice with zero blanks, then use the report's section classifications to pick what to revise.
4.3 Three questions for every option
Slow candidates read options; fast candidates interrogate them. Ask the same three questions of each choice, in this order:
- What does this measure or do?: name the mechanism in one clause. If you cannot, the option is a distractor you have not yet recognized.
- Does that mechanism answer the stem's pain?: the stem, not the topic. An option can be true and still irrelevant.
- Is it scoped, hedged and AWS-native?: the narrowest true answer beats the broadest true answer, and a hedged statement beats an absolute one.
4.4 The trap map, domain by domain
Domain | Trap the exam repeats most often | The correct reflex |
|---|---|---|
D1 | Reaching for a metric that does not match the error cost (accuracy under imbalance, R-squared for detection) | Translate the cost of the error into a metric before reading the options |
D2 | Confusing the billing unit (per call, per GPU-hour, per token) or the customization trigger | Ask "what am I buying?": tokens, hours, or capacity |
D3 | Jumping to fine-tuning for facts or formatting | Walk the ladder: prompt β RAG β fine-tune, then evaluate |
D4 | Mistaking AWS's own documentation (AI Service Cards) for documentation of your model | Model Cards = yours; AI Service Cards = AWS's |
D5 | Treating a detective or evidentiary tool as a preventive control | Prevent (Guardrails, IAM) / detect (Config, CloudTrail) / prove (Artifact): pick the verb the stem uses |
5. Domain weighting and the simulation blueprint
5.1 The only weights AWS publishes
Domain | Weight | Scored items on the real exam (derived) | Set A items here | Study hours of a 40 h plan | Priority cue |
|---|---|---|---|---|---|
D1 Fundamentals of AI and ML | 20 % | 10 | 3 (items 1-3) | 8.0 h | Metrics, lifecycle, service matching |
D2 Fundamentals of Generative AI | 24 % | 12 | 4 (items 4-7) | 9.6 h | Tokens, pricing, limits, AWS infrastructure |
D3 Applications of Foundation Models | 28 % | 14 | 4 (items 8-11) | 11.2 h | Prompting, RAG, agents, evaluation |
D4 Guidelines for Responsible AI | 14 % | 7 | 2 (items 12-13) | 5.6 h | Only 2 task statements: the densest return per hour |
D5 Security, Compliance, Governance | 14 % | 7 | 2 (items 14-15) | 5.6 h | Injection, IAM, shared responsibility, Artifact |
Total | 100 % | 50 | 15 | 40 h | "Scored items" column is arithmetic, not an AWS figure |
How to answer
Matching exercise with 5 pairs. Match each item on the left with its answer on the right.
Match each AIF-C01 domain to its published weight and the number of scored items it should receive on a 50-item exam:
Drag answers from here:
Comparative Verdict: Domain 3 (28 %) vs Domain 2 (24 %) vs Domain 1 (20 %) vs Domains 4 and 5 (14 % each)
- Domain 3, Applications of Foundation Models (28 %), is the largest single block and the one you should over-prepare. It carries roughly 14 scored items and it is the domain where procedure beats recall: prompting technique, the prompt β RAG β fine-tune ladder, agent action groups with Lambda, retrieval-vs-generation failure diagnosis, and evaluation modes. If you only re-read one domain the night before, re-read this one; it is also where the live exam's multiple-response and ordering items are cheapest to lose.
- Domain 2, Fundamentals of Generative AI (24 %), is the numbers domain. Tokens in vs tokens out, on-demand vs batch vs provisioned throughput, context windows, temperature, prompt caching, prompt routing and MCP. Marks here are fast and binary: you either know the billing unit or you do not. It is the best domain to convert from "shaky" to "solid" in two sittings.
- Domain 1, Fundamentals of AI and ML (20 %), is the classic ML core: supervised vs unsupervised, precision/recall/F1, overfitting, drift, the ML lifecycle and the prebuilt service map (Comprehend vs Textract vs Translate vs Polly). Candidates who arrive from a GenAI-only background under-weight it and pay for that at the end.
- Domains 4 and 5 (14 % each) look small and are not. Domain 4 has only 2 task statements yet 14 % of the score, which makes it the densest return per study hour on the entire exam: NIST AI RMF, ISO, the EU AI Act tiers, fairness and explainability (Clarify), transparency (Model Cards, AI Service Cards) and human oversight. Domain 5 is equally concentrated: prompt injection, least privilege, the shared responsibility split and AWS Artifact. Because scoring is compensatory, a weak 14 % domain is the classic reason a candidate fails with an otherwise strong report.
- Rule of thumb: allocate hours in proportion to weight (8 / 9.6 / 11.2 / 5.6 / 5.6 for a 40-hour plan), but spend your last week on D4 and D5; they are the cheapest marks to add back and the most expensive to lose.
- π Did you know? Domain 4 is worth 14 % of the exam from just two task statements, while Domain 1 spreads 20 % across a much longer list of objectives. That means each individual Domain 4 objective carries far more expected score than the average Domain 1 objective, and it is why a candidate who "knows ML well but never read the NIST AI RMF" can lose a passing margin in only a handful of items.
6. The customization ladder, and the drills that decide Set A
6.1 The ladder you must never skip
The single most repeated decision on this exam: given a problem with a foundation model, which lever comes next?
RAG changes what the model knows; fine-tuning changes how it behaves. Answer every "what should we do next?" question by asking which of those two is broken.
6.2 Worked example 5: the two-hour fix vs the two-week fix
"Answers must cite current internal policy documents the model has never seen." A better prompt will not help, because the model has no access to those documents. The correct next step is RAG (Bedrock Knowledge Bases: retrieved context plus citations). Only if the style of the answers is still wrong after retrieval do you consider fine-tuning, and then you need Provisioned Throughput to invoke the customized model at all. Candidates who jump straight to fine-tuning answer a question nobody asked.
6.3 Worked example 6: weight-driven hour allocation
Multiply weight by total hours: h (D1), h (D2), h (D3), h (D4), h (D5). Split D4's 5.6 hours into about six dense sessions (NIST, ISO, EU AI Act, fairness, transparency, oversight) and D3's into prompting 3 / RAG 3 / agents 3 / evaluation 2.
6.4 Stem keywords and the first move they demand
The fastest way to lose Set A is to start reading options before you have decided what the stem is asking. Train this lookup table until the first move is automatic:
The stem says⦠| The stem is really asking | Your first move |
|---|---|---|
"which metric / how should performance be evaluated" | Which error cost matters? | Convert the stated cost into precision, recall, F1 or accuracy |
"cheapest / most cost-effective / reduce cost" | Which lever lowers tokens, hours or commitment? | Prompt caching, routing, batch, output limits, then re-read |
"fresh data / internal documents / citations" | Does the model know it? | RAG via Knowledge Bases; fine-tuning is the wrong rung |
"consistent style / tone / format at scale" | Is it behaviour or knowledge? | Prompt for format, fine-tune for behaviour |
"least privilege / which policy" | Narrowest true scope | Correct action on a resource ARN, plus scoped iam:PassRole |
"prove / evidence / auditor / report" | Is this about proof? | AWS Artifact, Config history, Model Cards, Clarify |
"should be reviewed / approved by a person" | Is accountability preserved? | Human-in-the-loop oversight, not full automation |
"blocks or flags ungrounded content" | Which guardrail filter? | Contextual grounding check for facts, sensitive-info filter for PII |
6.5 Trap Patterns & How to Beat Them
Sections 4 and 6 gave you the six distractor families and the stem lookup table. This section compresses the rest of the strategy material into three artefacts you can rehearse in the final week: a twelve-row trap map, a pacing plan keyed to the item ranges you can actually see on screen, and a short drill that punishes the reflexes most candidates bring into the exam hall. The map is deliberately wider than section 4's six families because the live exam recombines them: one item can bait you with a pricing unit and an absolute claim at the same time, and only one of the four options will fail on both counts.
6.5.1 The twelve trap families and the reflex that beats each one
# | Trap family | How the distractor baits you | Defensive technique | Spot-check you ask yourself |
|---|---|---|---|---|
T1 | Service selection | A plausible service with the wrong core job ( Rekognition for sentiment, Textract for translation) | Map verb to service first; prefer the AWS-native answer, then check the current scope list | "What is this service's core job?" |
T2 | Pricing units | One option list mixes per-token, per-hour, per-GB and per-1,000-text-unit rates | Write the unit beside every cost option before comparing any of them | "Billed per what, per what period?" |
T3 | "Serverless" misdirection | Implies serverless is free, instant, always-on and unlimited in payload | Recall the documented ceilings (serverless inference: 4 MB payload, 60 s) and the shape of the traffic | "Is the traffic bursty or sustained?" |
T4 | Parameter direction | Reverses the effect ("raise temperature so answers stay consistent") | Low temperature = deterministic; high temperature adds variance. top-k and top-p size the candidate pool | "Which knob, and which direction?" |
T5 | RAG vs fine-tuning | Offers fine-tuning for fresh, cited facts, or retrieval for tone and style | Facts, citations, freshness β RAG; behaviour, style, task β fine-tune | "New knowledge or new behaviour?" |
T6 | Inference-option matrix | Real-time offered for 1 GB payloads, batch offered for an interactive load | Key off payload, latency and persistence (25 MB / 60 s, 4 MB / 60 s, 1 GB / 1 h, offline) | "Payload size? Latency? Scale to zero?" |
T7 | Absolute wording | "always", "never", "must", "only", "guarantees", "100 %" | Red flag by default: prefer the hedged, evidence-based option, unless the rule genuinely is absolute ("never leave an item blank") | "Is this literally true with no exceptions?" |
T8 | Near-identical options | Two options that differ by a single qualifier | Choose the one that satisfies the stem's exact constraint: cost, latency, region, least privilege | "Which constraint does only this option satisfy?" |
T9 | Responsible-AI term swaps | Clarify, Model Monitor, Ground Truth and A2I offered interchangeably | Bias pre-deployment = Clarify; drift = Model Monitor; labels = Ground Truth; human routing = A2I | "Before, during or after deployment, and who acts?" |
T10 | Complexity bait | A hand-built pipeline where a managed feature already exists | Managed, least operational overhead, not over-engineered | "Can a managed service do the whole job?" |
T11 | Metric mismatches | BLEU for summarisation, R-squared for text, accuracy on imbalanced data | Match the task type: n-gram overlap, classification, regression or drift | "What kind of output is being scored?" |
T12 | Legacy / out-of-scope service | An old-guide favourite presented as the answer | Confirm against the current in-scope appendix; unlisted services are never the key | "Is this on the 2026 scope list?" |
Two rows do most of the damage to a first attempt: T2 (you know the service but not what it bills for) and T5 (you know both levers but not which one this stem needs). If you only rehearse two rows of this table before exam day, rehearse those two.
How to answer
Fill-in-the-blank exercise with 4 blanks. Type the missing words, then check your answer.
Complete the four trap-defence reflexes from section 6.5:
1) Write the blank beside every cost option before comparing anything. 2) Map the stem's verb to the service's blank before reading the remaining options. 3) Treat blank words such as 'always' and 'guarantees' as a red flag. 4) When two options survive elimination, take the most blank and least absolute one.
Word Bank, drag words into the blanks above:
6.5.2 The pacing plan, keyed to item ranges
Section 3.1 splits the clock into phases; the plan below splits the same 90 minutes into item ranges, which is what you can actually count on screen. The two are compatible: ranges S1 to S4 are your first pass with ordering and matching handled where they appear, S5 is the flagged review, and both plans reserve the final three minutes exclusively for the no-blank check.
Segment | Items | Elapsed clock | Cumulative minutes used | Rule you must not break |
|---|---|---|---|---|
S1 Warm-up | 1-10 | 0:00 β 0:12 | 12 | Read fully, decide fast; flag anything over 90 s |
S2 Core | 11-30 | 0:12 β 0:37 | 37 | 60 s per item; eliminate two before you choose |
S3 Slog | 31-50 | 0:37 β 1:02 | 62 | Matching and ordering live here: do them whole, never partially |
S4 Long tail | 51-65 | 1:02 β 1:17 | 77 | Slower stems and case sets; still flag rather than stall |
S5 Flag sweep | all flagged | 1:17 β 1:27 | 87 | Re-read the stem, re-run elimination once |
S6 Buffer | : | 1:27 β 1:30 | 90 | Confirm zero blanks, then submit |
Derived check-points (arithmetic, not an AWS figure): the ceiling is 83 s per item; more than three minutes on one item costs you two items elsewhere; a sustainable flag budget is about one flag in every six items (roughly ten in total); and if S2 runs five minutes over, you cut time from S5: never from S6's blank check.
- π Did you know? Because the average budget is 83 seconds, three minutes spent re-reading one stem is not three minutes lost; it is two whole items pushed into your last ten minutes. Working backwards from that ceiling, the derived flag allowance is about one flagged item in six, roughly ten flags across the exam. Flag twenty and you have not identified the hard items; you have quietly scheduled a third of the paper for a review window that cannot hold it.
6.5.3 Trap mini-drill: four items that punish the usual reflexes
These four are deliberately short, because the trap usually resolves in the first five seconds: the moment you notice which unit, which direction or which window is in play. Answer all four before reading the explanations.
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
An extraction pipeline must return the same factual answer on every run. Which change is most appropriate?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Which statement about Amazon Bedrock Guardrails pricing is CORRECT?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A candidate fails the AIF-C01 on 1 October. What is the earliest they can sit the exam again, and on what terms?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
What does compensatory scoring mean on the AIF-C01?
6.5.4 Where each trap already lives in this course
You do not need new material for these traps; you need to reconnect them to the lesson that owns them. Read this as your revision routing table: if a row surprises you, that lesson is your next stop.
Trap family | Where you already met it | The Set A item it imitates | The reflex to rehearse |
|---|---|---|---|
T1 Service selection | Lesson 07, prebuilt AI services | 11, 12 | Verb to service, core job first |
T2 Pricing units | Lessons 09 and 15, Bedrock pricing and cost levers | 5, 6, 7 | Write the unit before comparing |
T4 Parameter direction | Lesson 08, tokens, temperature, context | 4 | Low temperature = deterministic |
T5 RAG vs fine-tuning | Lessons 10 and 11, knowledge bases and agents | 8, 9 | Knowledge or behaviour? |
T7 Absolute wording | Lesson 12, safety and guardrails | 4 | Hedged beats absolute |
T9 Responsible-AI swaps | Lesson 12, responsible AI and oversight | 12 | Before, during or after; who acts? |
T10 Complexity bait | Lessons 13 and 15, MLOps and optimization | 8 | Simplest managed option wins |
T11 Metric mismatches | Lesson 04, algorithms and evaluation | 1, 2, 3 | What kind of output is scored? |
Over-scoped IAM | Lesson 14, security and least privilege | 14 | Narrowest action on the narrowest ARN |
Evidence vs assertion | Lessons 14 and 15, governance and evidence | 15 | Artifact, Config, CloudTrail, Model Cards |
6.5.5 2025 to 2026 Updates Quiz
The trap map has one more family worth its own check: material that changed while you were studying. Guide v1.1 (30 April 2026) added objectives, added services to the in-scope list and removed one, and several services moved into maintenance or closed to new customers during 2025 to 2026. Both items below come from verified 2025 to 2026 changes: answer them before you read the explanations.
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Exam guide v1.1 (published 30 April 2026) added seven objectives to the AIF-C01. Which of these is one of them?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Amazon Kendra no longer accepts new customers. An organisation needs managed enterprise search with generative question answering over its S3 content. Which service does AWS direct new workloads to?
- π Did you know? Seven objectives were added when the guide moved from v1.0 (26 March 2026) to v1.1 (30 April 2026): traditional ML vs foundation models, token-based pricing, context engineering, agentic AI, prompt versioning, business-alignment metrics, and hallucination detection with grounding. AWS also states that guide updates reach the live exam about one month after publication, so an item that feels "too recent to be examined" is precisely the item v1.1 was written to test.
Exam-day pitfall: stale facts and last-minute second guesses:
- A distractor can be true and still wrong because the service behind it moved during 2025 to 2026. Kendra no longer accepts new customers (maintenance 30 June 2026, closed 30 July 2026) and AWS points new search workloads at Bedrock Managed Knowledge Base.
- SageMaker Model Monitor and SageMaker Clarify closed to new customers on 30 July 2026. Their status is maintenance, not shutdown and not a rebrand into Bedrock Model Evaluations, but if a stem describes a new project, check whether the documented successor is the answer the item wants before you commit.
- Amazon MemoryDB was removed from the in-scope list on 30 April 2026. Never key an item on a service the current guide does not list (trap T12, section 12).
- Do not "fix" a correct answer during the submit sweep. Re-read the stem, confirm you answered the asked question, and change an option only if you can state the reason in one clause.
7. Practice Questions, Set A: 15 single-best-answer items
Set A mirrors the real exam's dominant format: one correct response, three distractors. It is deliberately weighted like the published domains: 3 items for D1, 4 for D2, 4 for D3, 2 for D4 and 2 for D5. Set a 15-minute timer, answer every item, and never leave one blank. The answer key, organized by domain, follows in section 8.
7.1 How to sit Set A
Setting | The rule | Why it matters |
|---|---|---|
Timer | 15 minutes flat (60 s per item, the first-pass budget) | It trains the rhythm you will use for 65 items, not just 15 |
Materials | No notes, no search, no section 8 visible | Open-book scoring measures your notes, not you |
Pacing | Answer every item; flag anything over 90 seconds and keep moving | A blank is a guaranteed zero: the rule never changes with set size |
Second pass | Only after the timer stops, revisit flagged items | Simulates the 1:05-1:18 review window |
Grading | By domain first, total second (section 8.7) | Compensatory scoring punishes the dip, not the average |
Re-sit | 72 hours later, from memory | Shorter gaps measure recognition, not retention |
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Unlabelled transaction records must be grouped into natural segments so that analysts can inspect each segment separately. Which machine-learning approach fits this requirement?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A fraud-detection model has false negatives that cost 50 times as much as a false alarm. Which metric should the team prioritise during evaluation?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A model reports 99% training accuracy and 72% validation accuracy. What is the best FIRST action?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Which statement BEST describes a hallucination in a generative AI system?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Which statement about Amazon Bedrock on-demand pricing is CORRECT?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A team has just fine-tuned a customised model in Amazon Bedrock. What is required before that customised model can be invoked?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A workload mixes simple FAQ-style prompts with complex reasoning prompts against the same model family. Which Bedrock capability reduces cost WITHOUT any retraining?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A summarisation bot returns correct content but an inconsistent JSON structure across calls. What is the cheapest reliable fix?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Employees must ask questions of 200,000 internal documents that the foundation model never trained on, and answers must include citations. What is the BEST approach?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
An assistant must check inventory in one system and then place an order in another system. What is the core of the correct design?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Before launch, a team needs automated scores AND human side-by-side ratings of model outputs on a labelled dataset. Which capability should they use?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A credit-scoring model must be tested for bias across demographic groups and must produce feature attributions for auditors. Which service should the team use?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Which set lists the four core functions of the NIST AI Risk Management Framework 1.0?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
A service role must be able to invoke exactly one foundation model in one AWS account. Which policy design is CORRECT?
How to answer
Multiple-choice question with 4 options. Select one option, then choose Check Answer.
Leadership needs continuous, auditable evidence that resources stayed in the required configuration (for example, encryption enabled) over time. Which service provides it?
8. Answer key and explanations, organized by domain
8.1 Domain 1: Fundamentals of AI and ML (Set A items 1-3)
Item | Answer | Why it is right: and why the alternatives fail |
|---|---|---|
1 | C: Unsupervised clustering | Segmentation of unlabelled data is textbook unsupervised learning. Supervised classification presupposes labels you do not have, reinforcement learning presupposes a reward loop, and a rules engine learns nothing. |
2 | C: Recall | Recall = TP/(TP+FN); with false negatives 50x costlier, minimising them is the goal. Accuracy is inflated by imbalance, precision optimises the cheap error, R-squared is regression-only. |
3 | B: Regularization + more representative data | A 99 % / 72 % gap is overfitting. More epochs and looser regularization deepen it; deploying defers a cheap fix. |
8.2 Domain 2: Fundamentals of Generative AI (Set A items 4-7)
Item | Answer | Why it is right: and why the alternatives fail |
|---|---|---|
4 | B, Fluent but unverifiable output | That is the published definition of hallucination. Injection, throttling and drift are three different risk classes with three different controls. |
5 | D, Input and output tokens, by model | On-demand Bedrock billing is per token and per model provider; the other three describe flat-per-call, GPU-hour and latency billing models that Bedrock on-demand does not use. |
6 | A: Provisioned Throughput | Customised models are invoked through Provisioned Throughput, billed hourly. Nothing moves to EC2 and no retraining is implied. |
7 | C: Intelligent Prompt Routing | Routing picks the right model in the family per request, about 30 % cheaper for simple prompts, with no retraining. Distillation is training, Provisioned Throughput is a commitment, guardrails are safety. |
8.3 Domain 3: Applications of Foundation Models (Set A items 8-11)
Item | Answer | Why it is right: and why the alternatives fail |
|---|---|---|
8 | A: Few-shot examples + explicit schema | Format instability is fixed in-context at no training cost. Fine-tuning, vector stores and Provisioned Throughput answer different problems. |
9 | B: Bedrock Knowledge Bases (RAG) | Retrieval at query time over a corpus the model never saw, with citations. Fine-tuning does not ground facts, longer instructions cannot invent content, higher temperature reduces reliability. |
10 | C: Agent with action groups + Lambda | Agents orchestrate multi-step tool use; action groups execute real actions. A one-shot prompt, a static FAQ or a nightly batch cannot place an order interactively. |
11 | D: Bedrock Model Evaluation | Automated metrics plus human side-by-side rating on a labelled dataset is exactly what Model Evaluation provides; RUM, Macie and Cost Explorer measure other things entirely. |
8.4 Domain 4: Guidelines for Responsible AI (Set A items 12-13)
Item | Answer | Why it is right: and why the alternatives fail |
|---|---|---|
12 | A: SageMaker Clarify | Bias detection (pre- and post-training) plus feature attributions. Polly and Transcribe are speech services; Artifact holds AWS's compliance reports, not your model's bias evidence. |
13 | B: Govern, Map, Measure, Manage | The AI RMF 1.0 core functions. A is the NIST CSF, C is PDCA, D is a RAG pipeline. |
8.5 Domain 5: Security, Compliance and Governance (Set A items 14-15)
Item | Answer | Why it is right: and why the alternatives fail |
|---|---|---|
14 | C - bedrock:InvokeModel on the model ARN | Least privilege = narrow action, narrow resource, scoped iam:PassRole. Wildcards, AdministratorAccess and shared keys all violate it. |
15 | D: AWS Config | Config stores configuration history, evaluates compliance and proves drift over time. CloudTrail proves who acted, Budgets prove what you spent, and prompt flows do neither. |
8.6 Rapid key for the rest of the 40-item bank (Sets B and C)
Set A is your graded simulation; these 25 items are your ungraded reinforcement set. Cover the answer column, recall the key, then check.
Bank # | Domain | Recall hook | Key |
|---|---|---|---|
4 | D1 | Managed API for sentiment and key phrases on support tickets | Amazon Comprehend |
5 | D1 | Detect that live inputs no longer match training data | SageMaker Model Monitor |
6 | D1 | Regulated credit model that must be explainable to auditors | Traditional supervised ML + SageMaker Clarify |
7 | D1 | Best definition of generative AI | Creates new content learned from data patterns |
8 | D1 | Labelling 50,000 images with your own taxonomy | SageMaker Ground Truth |
10 | D2 | Near-identical answers to identical inputs | Lower the temperature |
11 | D2 | Definition of the context window | Max tokens per request, input + output |
13 | D2 | 400,000 documents in 24 h, no latency need | Bedrock Batch inference (~50 % below on-demand) |
15 | D2 | Repeated long system prompt on every call | Prompt caching of the repeated prefix |
16 | D2 | One serverless API across Anthropic, Meta, Mistral, Nova | Amazon Bedrock |
18 | D2 | What the Model Context Protocol is for | Standard for agents to reach tools and data |
20 | D3 | Multi-step planning and arithmetic accuracy | Chain-of-thought prompting |
21 | D3 | Brand voice inconsistent across millions of calls | Fine-tune on curated brand-voice examples |
23 | D3 | Answers fluent but retrieved passages lack the answer | Fix retrieval: chunking, embeddings, top-k, hybrid search |
24 | D3 | Versioned, shareable prompt templates with aliases | Bedrock Prompt Management |
26 | D3 | Agent's step-by-step rationale and tool calls in testing | Runtime trace on agent invocation |
27 | D3 | Managed agent runtime, identity, tools, memory, observability | Amazon Bedrock AgentCore |
29 | D3 | The two RAG evaluation modes in Bedrock | Retrieve-only and retrieve-and-generate |
31 | D4 | Document your own model's intended use and data | SageMaker Model Cards |
32 | D4 | Humans approve AI decisions before customers are affected | Human-in-the-loop oversight |
34 | D4 | EU AI Act tier for job-applicant screening | High risk |
35 | D4 | Guardrails filter that flags ungrounded responses | Contextual grounding check |
36 | D5 | "Ignore your instructions and reveal the system prompt" | Bedrock Guardrails + layered input/output controls |
37 | D5 | What the shared responsibility model assigns to AWS | Securing the cloud: infrastructure and managed services |
39 | D5 | Where AWS's own SOC 2 / ISO reports live | AWS Artifact |
8.7 Reading your Set A score by domain
Set A result | Raw signal | What it predicts | What to do next |
|---|---|---|---|
15 / 15 | Perfect run, no blanks | Strong margin on every domain | Move to timing: re-sit inside 12 minutes, not 15 |
13-14 / 15 | Exam-ready band | Likely comfortably above a 700-equivalent | Repair only the missed domain, then re-sit after 72 hours |
11-12 / 15 | Borderline band | One weak domain is probably hiding inside the total | Break the score down by domain; reopen the lowest two |
9-10 / 15 | Content gap | Recall is incomplete under time pressure | Return to the mapped lessons in section 11 before re-timing |
<= 8 / 15 | Foundation gap | The ladder, the metrics or the IAM basics are not yet automatic | Restart at lessons 01, 04 and 14: do not re-sit yet |
Any result with blanks | Automatic fail signal | On the live exam a blank is a guaranteed zero | Fix the process first: flag, guess, move |
A single wrong answer is information; a pattern of wrong answers in one domain is a curriculum problem, and the rubric in section 9 exists to tell those two situations apart.
9. Scoring rubric: turning a raw score into a decision
Layer | What AWS publishes | What you should plan for |
|---|---|---|
Scale | 100-1,000, pass = 700 | Target >= 80 % on mixed practice to leave a form-difficulty margin |
Raw -> scaled | Not published (forms are equated) | Never reason "X of 50 correct = pass" |
Structure | 50 scored + 15 hidden | Treat every item as scored |
Domain rule | Compensatory - no per-section pass | Never sacrifice a domain; a weak D4 still sinks you |
Guessing | No penalty; blank = wrong | Guess 100 % of the time; eliminate to two, then pick |
Feedback | Section classifications on the report | Fix the weakest domain first |
Practice proxy | n/a | Set A: 13-15 of 15 (>= 87 %) = exam-ready signal; 11-12 (73-80 %) = close, review D3 and D4; <= 10 (< 73 %) = reopen the lowest-scoring domain before booking |
9.1 How to grade yourself honestly
- Score Set A raw first: one point per item, no partial credit, exactly like the live exam's multiple choice.
- Convert by domain, not by total. A 13/15 that hides two Domain 4 misses is more dangerous than an 11/15 spread evenly, because compensatory scoring punishes the dip, not the average.
- Categorize every miss as knowledge gap (you did not know) or reading error (you knew it and picked the distractor). Knowledge gaps go to the study plan in section 10; reading errors go to the distractor table in section 4.
- Re-sit Set A in 72 hours. Score inflation on an immediate re-sit is memory, not mastery; a 48-72 hour gap is the shortest honest interval.
- Convert confidence, not luck. If you guessed between two options and got it right, you are at risk: re-run that item until the reason is correct, not just the letter.
10. Study plan: 40 hours, driven by the published weights
10.1 Hours per domain
Domain | Weight | Hours (weight x 40 h) | Sessions (~1.5 h) | Drill focus | Checkpoint before exam day |
|---|---|---|---|---|---|
D1 | 20 % | 8.0 h | 5-6 | Metrics, overfitting, drift, service map | Explain recall vs precision out loud in 30 s |
D2 | 24 % | 9.6 h | 6-7 | Tokens, pricing tiers, context window, MCP | Name the cost lever for three given workloads |
D3 | 28 % | 11.2 h | 7-8 | Prompting 3 h, RAG 3 h, agents 3 h, evaluation 2 h | Justify prompt vs RAG vs fine-tune for five stems |
D4 | 14 % | 5.6 h | 4 | NIST RMF, EU AI Act tiers, Clarify, Model Cards | Recite GOVERN/MAP/MEASURE/MANAGE + 4 AI Act tiers |
D5 | 14 % | 5.6 h | 4 | Injection, least privilege, shared responsibility, Artifact | Write a least-privilege Bedrock policy from memory |
Total | 100 % | 40 h | 26-29 | Mixed sets weekly | Set A >= 13/15 twice, 72 h apart |
10.2 The six-week sequence
Week | Focus | Deliverable |
|---|---|---|
1 | Lessons 01-03: exam guide, lifecycle, data engineering | Domain 1 flash deck; know the five domain weights |
2 | Lessons 04-07: algorithms, training, deployment, prebuilt services | Confusion-matrix math without notes |
3 | Lessons 08-10: GenAI fundamentals, Bedrock, RAG | Token arithmetic and the pricing-tier table |
4 | Lessons 11-12: agents, workflows, safety and guardrails | One traced agent run; guardrail filter inventory |
5 | Lessons 13-15: MLOps, security/IAM, cost and governance | Least-privilege policy written once from memory |
6 | Lesson 16: Set A under time, rubric, weak-domain repair | Set A >= 13/15, zero blanks, twice |
- π Did you know? Because the exam guide updates reach the live exam roughly one month after publication (guide v1.1 was published 30 April 2026), a candidate testing in the same month as a revision may face items drawn from either version. The safe behaviour is to re-read the revision page for your course about a month before your date, and to refuse to build any answer on a service that only appears in older guides (section 12).
10.3 The last 48 hours, and the morning itself
When | Do | Do not |
|---|---|---|
T-48 h | Re-sit Set A under time; grade by domain with section 8.7 | Start a new topic: nothing learned in 48 hours survives stress |
T-24 h | Re-read sections 3, 4 and 5: the clock, the distractors, the weights | Re-read anything you have never seen; it will feel familiar and be wrong |
T-12 h | Write out the five weights, the four question types, NIST's four functions and the ladder from memory | Cram unverified facts: if it is in section 12, it is not yours to assert |
Morning of | Eat, arrive early or log in 20 minutes early, ID ready, room clear | New flashcards, forum panics, or a "quick" full practice exam |
Minute 0 | Read the first stem twice; start the 60-second-per-item rhythm immediately | Spend five minutes admiring the interface |
The goal of the last 48 hours is not new knowledge; it is retrieval practice on what you already have, so that the four decision rules (guess protocol, ladder, least privilege, evidence-over-assertion) fire automatically at item 1.
11. Synthesis of lessons 01-15
11.1 The whole course on one page
Lesson | Title | Domain weight it feeds | What Set A / the live exam tests from it |
|---|---|---|---|
01 | AIF-C01 Exam Guide and AI/ML Fundamentals | D1 20 % | What the exam is, ML vs AI vocabulary, problem-type selection |
02 | End-to-End ML Lifecycle on AWS | D1 | Where overfitting, drift and monitoring sit in the lifecycle |
03 | Data Engineering for AI on AWS | D1 | Labeling, training-data quality, Ground Truth-style workflows |
04 | ML Algorithms and Model Evaluation on AWS | D1 | Recall vs precision vs accuracy; the metric that answers the stem |
05 | Training and Hyperparameter Tuning on Amazon SageMaker | D1 | Regularization as the fix for a train/validation gap |
06 | Deployment and Inference on Amazon SageMaker | D1 / D5 | Endpoint choice, monitoring, Model Monitor for drift |
07 | Prebuilt AWS AI Services: Vision, Language, Speech and Conversation | D1 | Verb-to-service mapping: Comprehend, Textract, Translate, Polly |
08 | Generative AI Fundamentals: Tokens, Transformers, Prompting and Foundation Models | D2 24 % | Hallucination, temperature, context window, token behaviour |
09 | Amazon Bedrock Foundations: APIs, Model Access, Pricing, Inference Types and Evaluations | D2 | Token pricing, batch, Provisioned Throughput, model access |
10 | RAG and Knowledge Bases on Amazon Bedrock | D3 28 % | Citations, retrieval failure vs generation failure |
11 | Amazon Bedrock Agents, Flows and Orchestration | D3 | Action groups, Lambda tools, traces, MCP |
12 | Generative AI Safety, Guardrails and Responsible AI | D3 / D4 14 % | Grounding checks, prompt-attack filters, human oversight |
13 | MLOps and Scaling on AWS | D1 / D3 | Pipelines, registry, scaling, evaluation cadence |
14 | Security, IAM and Compliance for AI Workloads | D5 14 % | Least privilege, shared responsibility, AWS Artifact |
15 | Cost Optimization and Governance for AI/ML | D2 / D5 | Token cost levers, budgets, tags, governance evidence |
16 | Capstone Exam Simulation (this lesson) | All | Logistics, clock, distractors, Set A, rubric, study plan |
11.2 The five threads that run through every domain
- Choose the smallest sufficient tool. Prompt before RAG, RAG before fine-tuning, managed before DIY, scoped ARN before wildcard: the same instinct appears in D1 (prebuilt vs custom), D3 (prompt vs train), D4 (documented control vs aspiration) and D5 (least privilege).
- Know the billing unit. D2 bills in tokens, batch is ~50 % below on-demand, Provisioned Throughput is hourly, and prompt caching can cut repeated-prefix cost dramatically. Cost questions are usually just unit questions.
- Evidence beats assertion. Compliance evidence lives in AWS Artifact, model evidence in Model Cards, bias evidence in Clarify, configuration evidence in Config, action evidence in CloudTrail. An option that promises a result with no artifact behind it is usually wrong.
- Humans stay accountable. Human-in-the-loop oversight, human evaluation, approval gates in MLOps, and the shared responsibility split all say the same thing: automation proposes, accountability does not transfer.
- Language discipline. "HIPAA-eligible", not "HIPAA certified"; "reduces hallucination risk", not "eliminates hallucinations"; "in scope", not "compliant". The least absolute, most specific option wins.
11.3 Final integration drill
Take any stem from Set A and name the lesson that owns it. Items 1-3 belong to lessons 01-05, items 4-7 to lessons 08-09 and 15, items 8-11 to lessons 10-11 and 13, items 12-13 to lesson 12 (with the NIST framing from lesson 01), items 14-15 to lesson 14. If you cannot place an item, you do not yet have a revision target; you have a recognition gap, which is the more dangerous kind, because it feels like knowledge.
12. What this lesson does not assert
To keep an unverified claim from becoming a wrong answer, these points are deliberately flagged rather than taught:
- Case-study items. The current guide lists four question types; an older AWS document also mentions case study. Whether case studies appear live is unconfirmed.
- Language counts and ESL wording. The product page lists 12 languages while parts of the FAQ describe 8 plus +30 minutes for ESL accommodation. The two pages are not reconciled for AIF-C01.
- On-screen pass/fail. The FAQ says most AWS exams do not display a result on screen; AIF-C01's specific behaviour is unstated and community reports conflict.
- Raw-to-scaled conversion. AWS never publishes how many of the 50 scored items equal 700. Any "35/50 = pass" claim is unsourced.
- Per-topic weights. Only domain percentages exist; objectives carry no published weight.
- Live-form composition. The number of multiple-response, ordering and matching items is unpublished; Set A is 15 single-best-answer items by design.
- Items per domain. The "scored items" column in section 5 is arithmetic from weights, not an AWS figure.
- Legacy services as keys. Services absent from the current in-scope list are avoided as correct answers in this lesson.
- Actual result timing. Five business days is the official ceiling; faster anecdotal releases are unverified.
- Time-bound promotions. Any voucher or discount offer is not re-checked here and must be confirmed on the official page before you rely on it.
- Official practice-exam contents. Skill Builder practice exams sit behind sign-in; their counts, formats and difficulty were not retrieved for this lesson.
Exam-day traps: the mistakes that cost marks on this exact material:
- Leaving an item blank. Blank = incorrect, and there is no guessing penalty. An unanswered item is the only guaranteed zero on the exam.
- Treating 15 items as free. The unscored pretest items are unidentified; you cannot skip them, so every item gets your full attention.
- Computing a pass. The raw-to-scaled conversion is not published: plan for >= 80 % in practice, not for "35 of 50".
- Sacrificing a domain. Scoring is compensatory: a strong Domain 3 never rescues a weak Domain 4. Fix the dip, not the average.
- Ignoring Domain 4 because it is "only 14 %". It is 14 % from two task statements: the densest marks on the exam, and the easiest to lose without noticing.
- Falling for absolutes. "Guarantees", "always", "never", "eliminates hallucination": prefer the hedged, evidence-backed option.
- Buying the expensive answer. A longer prompt, a fine-tune or Provisioned Throughput is wrong when few-shot examples, RAG or prompt caching would do; choose the simplest managed option unless control is explicitly demanded.
- Mis-sequencing the clock. Ordering and matching are all-or-nothing and slow: do them after single-answer items, inside the 1:18-1:27 buffer.
- Asserting the unverified. If a fact is not on a current AWS page (section 12), do not state it as recall material on exam day.
Key Takeaways:
- The container: 65 items (50 scored + 15 hidden), 90 minutes (~83 s each), scaled 100-1,000 with 700 to pass, compensatory scoring, no guessing penalty, 100 USD, valid 3 years, 14-day wait after a fail, results within 5 business days.
- The four formats, multiple choice, multiple response, ordering, matching, all-or-nothing in different ways; plan the clock as 65 min first pass + 13 min review + 9 min ordering/matching + 3 min no-blank sweep.
- Never leave a blank, and when stuck apply the protocol: predict β eliminate two β most specific, AWS-native, least absolute β move within 60 seconds.
- Distractors are engineered, not random: wrong layer, wrong rung, wrong family, over-scoped, absolute wording, out-of-scope service: read the stem's pain before reading the options.
- Weights rule your hours: D1 20 %, D2 24 %, D3 28 %, D4 14 %, D5 14 % β 8 / 9.6 / 11.2 / 5.6 / 5.6 hours of a 40-hour plan, with the last week spent on the dense 14 % domains.
- Set A benchmark: 13-15 of 15 twice, 72 hours apart, with zero blanks; grade by domain, not by total, because compensatory scoring punishes the dip.
- The customization ladder never changes: prompt for format, RAG for facts the model never saw, fine-tune for behaviour in the weights, and evaluate before and after with Bedrock Model Evaluation.
- Evidence beats assertion: Artifact for AWS's compliance, Model Cards for your model, Clarify for bias and attributions, Config for configuration over time, CloudTrail for who acted, and if a claim is not on a current AWS page, do not assert it.