A few months ago, I picked up Web Scalability for Startup Engineers. It was full with real-world systems discussion, and alongside it, there was a few mention of AWS services ranging from EC2, Lambda to SQS. While reading it, I understood the general idea of them, but I kept wishing I had a stronger grounding in the actual ecosystem talked about.
Fast forward to now: I’ve just passed the AWS Cloud Practitioner (CLF-C02) exam! 🎉 And suddenly those buzzwords feel less abstract and a lot more practical.
Reading that book was a starting point for me. But the more I looked, the more I realise how discussions are leaned on AWS. It made me wonder: why is AWS always the backdrop, and what makes it the go-to reference point in tech?
Why AWS? #
I think us engineers are all too familiar with the name. AWS is the first big player in the cloud game, and it was the pioneer in that sense. When people say “the cloud,” half the time what they really mean is AWS. Sure, Azure, GCP, and even Alicloud are huge contenders now, but AWS still holds the largest market share and remains the reference point in most cloud conversations. In other words, learning AWS is like learning English in tech; you don’t have to love it, but it opens doors everywhere.
Why does that matter? It’s because a lot of cloud engineering chatter is just… AWS centric.
DevOps folks throw around terms like S3, RDS, or VPC without stopping to explain, because for them it’s shorthand. If you know that lingo, you’re instantly in the loop. That’s where something like the AWS Certified Cloud Practitioner (CLF-C02) comes in handy. By learning through the exam, you get a map general cloud concepts to concrete AWS services and join the conversation without feeling like an outsider.
Who is this for? #
In general, I see two groups could greatly benefit from taking the Cloud Practitioner cert: the new engineers and the seasoned folks.
New engineers #
If you’re just kicking off your cloud journey, CLF-C02 is a solid starting point. It’s approachable, it forces you to pick up the fundamentals, and it gives you a clear mental map of how the cloud actually works. Think of it as training wheels. You’ll outgrow it, sure, but it’s way better than wobbling around with no guidance.
Experienced engineers #
Maybe you’ve already got an Azure or GCP Professional cert under your belt. Great. Adding AWS into the mix shows you’re not locked into a single ecosystem. It’s proof you’re familiar with the AWS ecosystem too, which makes you instantly more versatile when switching teams, projects, or even companies. The biggest perk is how low-stress it is if you already know cloud basics. The exam is straightforward, quick to prep for, and gives you a high ROI credential without the grind of a heavier cert.
It’s the most cost-effective choice #
The Cloud Practitioner exam is also one of the cheapest major cloud certs at just $100. On top of that, AWS regularly hands out 50% discount voucher you can apply to your next exam. That means you can stack certs without torching your wallet. For example:
| Path | Exam(s) | Cost |
|---|---|---|
| With CLF + Voucher | CLF-C02 ($100) + DVA-C02 ($75 after 50% off) | $175 for 2 certs |
| Skipping CLF | DVA-C02 ($150 full price) | $150 for 1 cert |
So with AWS, you’re basically getting two certs for barely more than the cost of one. And you can get it even cheaper if you take the exam on top of AWS’s event discount promos.
Add to that a massive ecosystem of docs, tutorials, and free-tier playgrounds, and you’ve got a training ground that’s hard to beat (overwhelming at times, sure, but hey, that’s a problem worth having!)
What to Expect (Scope & Difficulty) #
CLF-C02 is foundational. The intent of the exam is to check whether you understand the vocabulary and core concepts of cloud, and understand the tradeoff you’re making when you pick one set of technologies over the other.
The exam consists of:
- Format: 65 questions, 90 minutes*
- Scoring: scaled 100–1000; pass at 700
- Scored vs. unscored: 50 count, 15 are unmarked questions
- Domains:
- Cloud Concepts (24%)
- Security & Compliance (30%)
- Tech & Core Services (34%)
- Billing & Pricing (12%)
In other words, if you can explain why EC2 is different from Lambda, why IAM matters, and how AWS bills you, you’re already halfway there.
*If English isn’t your first language, AWS lets you request an extra 30 minutes before booking your exam.
The Strat #
Alright, so you’ve decided AWS Cloud Practitioner (CLF-C02) is worth your time. Nice. Now comes the real question: how do you prep without drowning in the AWS ocean of docs, courses, and “top 10 hacks” clickbait contents? The trick is to pick your strategy up front.
To start, let’s set expectations first and foremost.
Two Paths: MVP vs DLP #
This is where you choose your adventure.
-
MVP (Minimum Viable Path) → the speedrun.
- Goal: Pass fast, don’t overthink it.
- Recipe: one full video course → skim a whitepaper → official sample questions.
- Timeline: ~1–2 weeks if you’re consistent.
-
DLP (Deeper Learning Path) → the slow-but-sure.
- Goal: Actually learn AWS, not just scrape by.
- Recipe: course → flashcards → hands-on labs → docs/whitepapers → multiple practice sets → patch weak spots.
- Timeline: 3–6 weeks depending on how much you tinker.
Both work. It just depends on whether you want a credential or a foundation. Personally, I went DLP because I wanted the knowledge to stick.
MVP (Speedrun) #
If you just want that badge:
- Watch the free 14h CLF-C02 course on freeCodeCamp (ExamPro), and just absorb.
- Read one whitepaper (Well-Architected Framework or Cloud Adoption Framework).
- Skim the official exam guide and do the official sample questions.
That’s it. Community folks on r/AWSCertifications swear by this recipe. You’ll probably score mid-700s to low-800s if you stick to it.
DLP (Slow but Sure) — What I Did #
-
Video course
First pass: absorb, don’t stress
Same as MVP, but don’t worry if you zone out. First pass is for exposure; understanding deepens later. The tutorial contains follow-alongs, you can just watch and learn. A lot of the GUI is outdated, but the concepts are solid. -
Anki flashcards
Services, roles, and ‘this vs that’
-
Hands-on labs
Small, real projects
Build tiny but realistic setups:
- S3 static site → CloudFront (OAC), custom domain, HTTPS.
- EC2 + ALB + Auto Scaling → with CloudWatch alarms.
- Serverless CRUD → API Gateway → Lambda → DynamoDB → CloudWatch Logs.
- IAM + Audit → least-privilege roles/policies, CloudTrail enabled; compare logs vs CloudWatch metrics.
- Storage contrasts → S3 vs EFS vs EBS.
-
Play to your strengths
Reuse proven exam habits
If you’ve done structured exams (IELTS, HSK, CFA, etc.), reuse those habits here:- Timed practice sets to simulate the 90-minute pace.
- Spaced repetition for service names and tricky contrasts.
- Post-mortems on wrong answers to fix patterns.
-
Practice-exam strategy
Aim ~80% before booking
You can try a mix of banks (quality varies):
- ExamPro — one free practice exam; paid for more.
- Tutorials Dojo — widely recommended; strong explanations.
- Udemy — many options; check reviews/updates.
- Kananinirav — free mock exams, albeit a bit outdated.
Resource Shortlist (Save These) #
- Official:
- Whitepapers:
- Practice exams:
- Paid:
- Free:
- Cheat sheets: (not a substitute for real study, but good for last-minute reviews)
When to Book? #
Here’s the million-dollar question: when should you stop “cramming” and actually commit to exam prep? Imo, the sweet spot is when you can consistently hit ~80% on practice exams. That’s the point where you’ve built enough familiarity to handle curveballs and the pressure of the real thing. Some people push for 90%+, but honestly that can be overkill. You risk burning out or memorising answers instead of understanding.
- If you dip below that, reschedule (up to 24h before, max twice per appointment).
- If you fail the real exam, 14-day cooldown, unlimited retakes (no refunds tho).
Test Centre vs. Home Testing #
| Option | Pros | Cons | Best For… |
|---|---|---|---|
| Test Centre | Minimal setup, reliable, breaks ok | Commute, fixed schedules | Those who like structure + zero setup |
| At Home (Remote) | Flexible, comfy, no commute | Strict setup, no breaks, possible delay | Those wanting flexibility / remote prep |
When it’s time to book, AWS (via Pearson VUE) gives you two options:
- Test Centre: Show up, sit down, and let them handle everything. Stable setup, toilet breaks allowed, minimal stress. Downside: Schedules might be limited, and you have to commute. (And I live in a congested city 😢)
- At Home (Online Proctored): More flexible. You take the exam on your own computer, with a webcam + mic, in your own space. But the tradeoff: no breaks, strict setup rules, and any hiccup (Wi-Fi drop, sudden outage, background noise, cat walking across keyboard) could ruin your day.
If you’re leaning towards a remote-first career (or even dreaming about going digital nomad), taking the exam at home can actually be good practice. You’ll get used to the quirks of online proctoring, and it’s a nice low-stakes way to build comfort with the remote setups you’ll probably face again in the future.
What to Expect with Home Testing #
If you go the online route, here’s the reality:
- Start check-in 30 minutes early: identity and room sweep required.
- No toilet breaks allowed. Leaving the camera view = instant fail.
- Desk must be clean. no phones, no paper, no external monitors.
- No multi monitor setup. If you use an external monitor for your laptop, you can close your laptop and use an external webcam, or discard your monitor altogether.
- Do the OnVUE system test a few days before, and make sure your Wi-Fi is stable.
- Expect a queue during check-in. You’ll sit waiting for a proctor to connect. And since you’re already on camera, you can’t step away for the toilet while you wait. Basically, treat your home like a sterile test lab for two hours and plan ahead so you don’t need a bathroom break mid-queue.
Language & Timing #
- AWS offers exams in multiple languages (English, Bahasa Indonesia, Japanese, Spanish, more coming like Arabic).
- If English isn’t your first language, you can request +30 minutes ESL accommodation, but you must request it before booking.
- Personal tip: morning slots are gold if you’re in Asian time zones because queues and lag are minimal.
Do keep in mind that your exam proctor may not share your language background either. For example, when I took the English exam, my invigilator had a very strong accent I wasn’t used to, and I found myself asking him to repeat instructions 3–4 times. It wasn’t a problem in the end, but it added stress I hadn’t anticipated.
If this happens, don’t be shy about politely asking them to repeat or slow down. Make sure you understand the rules before starting.
My Prepping Strategy #
When my date was locked in, I stopped cramming. Instead, I shifted into prep mode:
- Reviewed weak spots and flashcards (my Anki “confusing pairs” deck: CloudWatch vs CloudTrail, GuardDuty vs Inspector).
- Did quick refreshers on core whitepapers (Well-Architected vs Cloud Adoption Framework). Not memorizing, just reminding myself of the “why.”
- Use study notes and one last Tutorials Dojo review session. The focus now isn’t more knowledge, but rather it was to reinforce what I already knew.
D-1: No Cramming #
On the day before the exam, just light review of your notes or flashcards. Get proper rest; avoid the temptation of an all-nighter. Fatigue won’t help you.
If you’re testing remotely, double-check your setup: laptop, webcam, microphone, internet connection. Clear your workspace and let housemates or family know you’ll be “off-limits” during your exam window. Mental freshness matters more than squeezing in one last whitepaper.
On the Exam Day #
Morning of the Exam (Remote Proctored) #
- Log in 30 minutes early to complete the proctoring check-in.
- Re-run the OnVUE system test (even if you already did it days before). There might be surprise software update, and it won’t run unless you bump it to the latest version.
- Have your government-issued ID ready; it must exactly match the name on your AWS Certification profile.
Room Scan & Proctor Interaction #
The invigilator will:
- Verify your ID.
- Ask you to pan your webcam for a 360° room scan—desk, walls, and any potential distractions.
- Require you to clear your test space of notes, extra devices, or visible screens.
During the Exam #
- No bathroom breaks (remote only), so be ready beforehand.
- Keep your eyes on the screen. Frequent glances away can raise red flags.
- Pace yourself. Don’t get stuck on a single hard question; flag it and move on.
- Use the comment and flagging feature if you want to jot context for later when you review flagged items.
- Take a few minutes at the end to scan through flagged questions and confirm you’ve answered everything.
- Expect a quick feedback survey (~5 minutes) after finishing—difficulty, confidence, overall experience.
Mindset Reminders During the Exam #
- Treat the exam like a knowledge check, not a repeat of practice banks.
- Watch out for multi-select questions (“Select TWO”).
- Flag questions you’re unsure of and circle back at the end.
- Before submitting, pause. Double check your answers.
- Don’t fuss over one question, if it’s too hard, it’s probably those experimental, unmarked questions anyway.
Results & Score Report #
The exam result will immediately be shown after the test, and you’ll get a simple pass/fail screen. Older screenshots you might find online don’t mention it, but the newer version of this screen now explicitly states that sharing it violates AWS’s Terms of Service.
Because of that, I won’t post the exact screen here (you can still look it up if you’re curious). You’ll also get the score breakdown (though not very detailed) within about 5 working days, though in my case it arrived just an hour after the exam.
If you pass, congrats! You can take a breath, celebrate, and start thinking about your next step (or just enjoy the win for a while). If not, then don’t sweat it. Treat the score report as a roadmap showing exactly where you need to improve, adjust your study plan, and come back stronger on the retake.
Once everything clears, you can download your digital badge from Credly, which you can share on LinkedIn, your resume, or portfolio. Or write it on your own blog, like I do! 😉
After Thoughts #
Well, going through this cert didn’t just give me a badge, it gave me a starting point. It helped me understand the cloud landscape better, and now I can actually follow along when colleagues talk about AWS services without feeling lost.
And it goes beyond work, too. A colleague of mine recently had a nasty server outage and started exploring the cloud as a way to build more reliability into their setup. To my surprise, I was able to point them towards what to consider, what AWS services might help, how to think about trade-offs, and cost optimisation. I wasn’t their consultant or anything, but I wasn’t so clueless anymore and that felt huge.
So yeah, the benefits go deeper than passing an exam. Even if the exam itself sometimes makes you feel like you’re moonlighting as an AWS salesman.
