Ranked Breakdown
The same questions come up on r/AWSCertifications every week. Here are honest, nuanced answers to the seven most common ones — from whether to skip CLF to how long SAA prep really takes.
Checking sign-in status...
If you've spent any time on r/AWSCertifications, you've seen the same threads appear week after week. New candidates asking the same questions, getting a mix of helpful responses and contradictory opinions, and leaving more confused than when they arrived.
Related: SAA-C03 Study Plan
Some of those questions deserve better answers than the average Reddit thread provides. Not because the community is wrong, but because the answers depend on context that brief comments rarely account for.
Here are the seven questions that come up most often, with the kind of nuanced answers they deserve.
This is probably the single most debated question on the subreddit, and the answer genuinely depends on who you are.
Skip CLF if:
Do CLF first if:
There's also a practical financial angle the community often mentions: CLF costs around $100 and passing it gives you a 50% discount voucher on your next exam. Associate exams cost $150. Hold the voucher for a Professional or Specialty exam ($300) and the savings become meaningful.
The bottom line: if you're a technical professional targeting cloud engineering or architecture roles, start with SAA. CLF is not a prerequisite and for technical candidates it's mostly a warm-up lap.
Related: AWS Solutions Architect Associate vs Professional: What Actually Changes?
Every thread on this topic gets wildly different answers, ranging from "two weeks" to "six months," and both can be true depending on the person.
Here's a more useful framework:
2 to 4 weeks: Candidates who use AWS daily in their current role, have existing infrastructure or networking knowledge, and need to fill specific gaps rather than build from scratch. These are the stories that create unrealistic expectations for everyone else.
6 to 8 weeks: The most common realistic timeline for candidates with some cloud or IT background who are studying consistently (one to two hours daily on weekdays, more on weekends).
10 to 14 weeks: Candidates coming from non-cloud backgrounds, or those with limited daily study time. This is not a failure timeline. It's the realistic one for a lot of working professionals.
The variable that matters most isn't calendar weeks. It's how many quality study hours you accumulate and how much of that time involves scenario-based practice rather than passive content consumption. Consistent daily practice over eight weeks is more effective than three weeks of cramming, regardless of total hours.
Both instructors have passionate advocates on the subreddit. The honest answer is that they serve slightly different learners.
Stephane Maarek is exam-focused, efficient, and well-paced. His courses cover exactly what you need for the exam without going much beyond it. If your primary goal is to pass the certification and move on, Maarek is the more direct path. His courses are consistently updated and his teaching style is clear and structured.
Adrian Cantrill goes deeper. His courses teach AWS at a conceptual level that extends beyond the exam into real-world implementation. If you want to genuinely understand AWS rather than pass a specific exam, Cantrill's approach produces more durable knowledge. The trade-off is length — his courses are significantly longer.
The community consensus that comes up repeatedly: Cantrill to learn, Maarek to get exam-ready. Some candidates use Cantrill's course to build genuine understanding, then use Maarek's as a focused pre-exam review. For candidates with limited time who need the credential by a specific date, Maarek alone is sufficient.
For practice exams, Tutorials Dojo (Jon Bonso) is the near-universal recommendation across the subreddit. The quality of the explanations is what distinguishes it: wrong answers are explained as thoroughly as correct ones.
This comes up constantly, usually from candidates who are genuinely unsure whether to pull the trigger.
The score itself matters less than what it represents. A 78% on a high-quality scenario-based practice set under timed conditions is a meaningfully different signal than a 78% on an easy question bank with unlimited time.
Ask yourself these questions before treating any score as a readiness indicator:
If your scores are stable above 75% across multiple timed attempts on quality scenario-based practice, you're likely ready. The real SAA-C03 passing score is 720 out of 1000, which doesn't map directly to a percentage of questions correct because of weighted scoring.
One practical benchmark: if you're consistently clearing 80% or above on Legend mode on ExamOS, where the scenarios are long, layered, and specifically designed to surface reasoning gaps, that's a strong signal that your architectural judgment is where it needs to be.
This question gets polarized answers on Reddit. Some people say certifications are essential. Others say they're meaningless without experience. Both camps are partially right and talking about different situations.
Where the SAA genuinely helps:
Where the SAA matters less:
The nuanced answer: the certification is a door opener, not a career definer. It gets you the interview. Your actual judgment and ability to reason through architectural problems gets you the offer and keeps you in the role. Preparing properly for the certification, in a way that builds genuine architectural reasoning rather than exam-passing skills, is what makes it worth the investment.
Both are Associate-level exams, but they test different things and serve different career trajectories.
SAA-C03 (Solutions Architect) covers AWS broadly: architecture decisions, networking, storage, compute, databases, and security from a design perspective. It's the wider exam and generally considered the stronger signal for cloud architecture and infrastructure roles.
DVA-C02 (Developer Associate) goes deeper on serverless, CI/CD, deployment patterns, and how developers interact with AWS services from code. It's the more relevant exam for software engineers who want to validate their AWS development skills.
The community consensus that comes up repeatedly: start with SAA. It covers a broader foundation that makes the Developer Associate easier to study for afterward. The overlap between the two exams is significant enough that having SAA first reduces your net preparation time for DVA-C02.
If your role is primarily application development and you have no interest in infrastructure or architecture work, DVA-C02 first is a reasonable case to make. But for most candidates trying to establish AWS credibility broadly, SAA is the right starting point.
This question gets the most varied advice on the subreddit, and a lot of that advice optimizes for passing the exam quickly rather than building knowledge that lasts.
Here's what the preparation approach that produces durable results actually looks like:
Phase 1: Conceptual foundation (weeks 1 to 3) Work through a structured video course. Take notes on services you don't know well. Focus on understanding what each service solves and when you'd use it over alternatives, not on memorizing feature lists.
Phase 2: Hands-on practice Use the AWS free tier to build things. Create a VPC with public and private subnets. Set up an S3 bucket with lifecycle policies. Deploy a Lambda function with an API Gateway trigger. The exam's scenario questions are significantly more approachable when you've encountered the services in a real environment.
Phase 3: Daily scenario practice This is where most candidates underinvest. Fifteen to thirty minutes of focused scenario-based practice every day for four to six weeks builds the architectural reasoning the exam tests far more effectively than periodic practice test marathons.
The key discipline: review wrong answers at the reasoning level. Don't just note the correct answer. Ask why your reasoning led to the wrong option, what you missed in the scenario, and what principle the correct answer reflects. That analysis is what improves your next attempt.
ExamOS is built around this daily practice model: short scenario-based sessions that develop the reasoning patterns the SAA-C03 tests, with difficulty levels that tell you objectively where your preparation is solid and where it has gaps.
Phase 4: Timed full-length simulations In the two weeks before your exam, run two or three full-length timed practice exams under real conditions. No phone, no breaks, same time of day as your scheduled exam. Your score under these conditions is the most reliable predictor of your actual exam performance.
Underneath all seven of these questions is the same underlying anxiety: am I doing this right, and will it be enough?
The candidates who pass and feel genuinely prepared afterward are usually the ones who prepared actively, practiced with quality scenario-based material consistently, and booked the exam when their reasoning was stable rather than when their confidence peaked.
That combination, active preparation over passive consumption, consistency over cramming, scenario reasoning over answer memorization, is what the subreddit's most useful advice always comes back to.
Looking for daily scenario-based AWS practice that builds the reasoning the SAA-C03 actually tests? Explore AWS Solutions Architect Associate practice on ExamOS and track your progress across difficulty levels.
Related: Are IT Certifications Still Worth It in the AI Era?