Scoring, question types, and exam-day logistics

From 75 answers to a pass

1. 75 items answered

   Blanks score as wrong and guessing carries no penalty — answer everything, flag what you want to revisit.

2. 10 unscored items dropped

   The unlabeled pilot questions are removed before scoring; only 65 items count. You cannot tell which were which, so every question deserved full effort.

3. Statistical equating

   AWS equates across exam forms of slightly different difficulty — 750 never literally means 75% of questions.

4. Scaled to 100–1,000

   One compensatory total across all five domains; the score report may break down sections, but only the total decides.

5. 750 or above?
6. Pass — valid 3 years

   Full validity from the day you pass.

7. Fail — section table guides the retake

   Section-level feedback is coarse by design — AWS itself says to use caution interpreting it. It steers study; it never changes the result.

An associate stem

"A company wants a chatbot to answer questions from its internal documents with minimal operational overhead. Which service should it use?"

One requirement, one qualifier, one obviously right altitude. Recall plus a reflex — this is the bar the MLA-C02 path trains.

A professional stem

"A financial-services company runs a RAG assistant on Bedrock. Compliance requires EU data residency; P95 latency must stay under 900 ms during 10× traffic bursts; the knowledge base refreshes hourly from SharePoint; and the team wants to swap models without redeploying. Which combination of changes meets ALL requirements MOST operationally efficiently?"

Four constraints in tension, four options that each satisfy some of them. Professional stems are longer, every option looks production-plausible, and the winner is the one that violates nothing — then wins the qualifier.

How to read one

1. Inventory the hard constraints (residency, latency, freshness, no-redeploy) — they are filters, not preferences.
2. Eliminate any option that breaks one, however elegant the rest of it is.
3. Only then apply the qualifier — "MOST operationally efficient", "LEAST development effort" — to whatever survives.

Train the habit now; every drill on this path is written to this shape.