Final-Week Playbook & Exam Day Strategy

T-minus 7 days

Day 7 Baseline assessment

Take a full 75-question timed practice exam (Tutorials Dojo or equivalent) under real conditions: 170 min, no notes, no pauses.
Score honestly. Don't look up answers mid-exam.
Log every missed question in a weak-spots tracker: domain, skill, why missed, correct concept.

Day 6 Domain 1 deep review (31% of exam)

Re-read the Domain 1 page + Bedrock / Knowledge Bases / OpenSearch sections.
Work through all Domain 1 weak spots from Day 7.
Hands-on: build or review a Knowledge Base end-to-end if not already done.

Day 5 Domain 2 deep review (26%)

Re-read the Domain 2 page.
Focus: Bedrock Agents, action groups, tool use, Prompt Flows, streaming patterns.
Hands-on: build or review a Bedrock Agent with one action group.

Day 4 Domain 3 + Patterns (20%)

Re-read Domain 3 and the Architecture Patterns page.
Focus: Guardrails configurations, defense-in-depth, data residency, IAM patterns.
CISSP strength, but watch for trap #4 — security over-engineering.

Day 3 Domains 4 & 5 + Traps (23%)

Re-read Domain 4, Domain 5, and the Traps & Patterns page.
Work through every ordering/matching practice question you can get.
Focus: cost-optimization decision tree, troubleshooting flowcharts.

Day 2 Practice exam #2 + weak-spot hammer

Second full 75-question timed practice exam.
Compare to Day 7 baseline. You should see ≥10 point improvement.
Spend the remainder on anything still missed. Convert gaps to flashcards.

Day 1 Light review only

Read only: Glossary, Traps & Service Decision Matrix.
Do 10–15 quick ordering/matching questions for format warmup.
Sleep 8+ hours. No cramming past 8pm. Cramming the night before costs more than it gains on an exam this dense.

Exam day morning

Eat a real breakfast with protein. 170 minutes is a long time to run on nothing.
Hydrate but don't flood — bathroom breaks eat into exam time.
Arrive 30 min early (or set up proctoring environment with buffer).
Home proctoring: clear workspace, close everything, test webcam before start time.

During the exam · 170 min / 85 questions = 2 min/question

Pacing checkpoints

Q25

~50 min mark

If behind, speed up

Q50

~100 min mark

Halfway check

Q75

~150 min mark

Leaves 20 min for review

3 min

Per-question cap

Flag & move on if stuck

Question triage — three passes

Pass 1 Answer every question you can in under 90 seconds. Flag anything needing more thought. Never leave blank — compensatory scoring, no wrong-answer penalty, always answer.

Pass 2 Work through flagged questions with remaining time. Take the time you need.

Pass 3 If time remains, re-verify the flagged ones you were least sure about. Don't second-guess answers you were confident in — first instinct is usually right.

Reading strategy (for dense scenarios)

Read the last sentence first — it contains the actual question ("Which solution minimizes cost?" vs. "Which solution provides strongest security?").
Read the answer choices to know what dimensions matter.
Read the full stem, highlighting constraints.
Eliminate answers that fail ANY stated constraint.
Choose between remaining options based on AWS preference patterns (managed > self-built, least operational overhead, etc.).

Red-flag words that change the answer

Full list on the Traps page. The high-impact ones to watch for:

"Existing"

Don't replace unnecessarily

"Minimize operational overhead"

Managed services win

"Lowest cost"

Cascading · caching · right-sized

"Real-time"

Streaming · low-latency

"Current data" / "frequently changing"

RAG, not fine-tuning

"Must not leave AWS network"

VPC endpoints

"No downtime"

Blue/green · canary · parallel

When you're genuinely stuck

Eliminate the 2 clearly-wrong answers first.
Between remaining 2, pick the one that uses the more managed AWS service.
If both equally managed, pick the one with fewer moving parts.
If still 50/50, pick the one that explicitly addresses the most prominent constraint in the scenario.

Ordering / matching — extra caution No partial credit. Worth the same points as other questions. Don't rush — spend 3 minutes on a matching if you need to. Double-check by reading your answer back as a narrative ("First I would do X, then Y…") to sanity-check order.

Mental approach

Compensatory scoring implications

You do not need to pass each domain. You need 750/1000 total.
A weak domain is offset by a strong domain.
Don't panic if you feel uncertain on 30% of the exam — that's normal for this test. Keep moving.

When you hit a topic you've never seen

This will happen. It's a Professional exam with a broad service surface.
Apply first principles: what is AWS's default pattern? (managed, least overhead, defense-in-depth, cost-aware).
Eliminate out-of-scope answers (e.g., "fine-tuning" when the question says "dynamic data").
Pick the most AWS-native answer and move on.

If you leave feeling uncertain

That's the design. Dense scenario exams are meant to make experts feel uncertain.
Multiple passers report leaving thinking they failed, then passing comfortably.
Score comes in ~5 business days.

Post-exam

Immediately after: note topics you want to review regardless of pass/fail (while the questions are fresh in your mind).
If pass: apply for the Early Adopter badge if still eligible.
If fail: 14-day waiting period before retake. Use it to target specific domain weaknesses. Your weak-spots tracker + exam report gives a precise map of what to work on.

You've got this You've passed SAP-C02 at 81%. You hold CISSP and CCSP. You've built this study system from scratch. If you hit the playbook, you'll walk in calibrated, paced, and ready.