💡 TL;DR: The biggest mistake AWS candidates make is binge-watching video courses and thinking they've "covered the material." Watching Stephane Maarek explain S3 bucket policies isn't the same as knowing them under exam pressure. The fix: build a hands-on lab habit early, use service comparison tables to cut through the breadth, and drill scenario-based questions until you can spot the correct answer before you've finished reading the wrong ones.
AWS certification exams — whether you're targeting the AWS Solutions Architect Associate, AWS Developer Associate, or AWS SysOps Administrator — are notorious for two things: sheer breadth and scenario-based questions designed to trip up rote memorizers.
The breadth problem is real. AWS has over 200 services. Even the associate-level exams test meaningful knowledge of 30–50 services. Students respond by going wide: they watch every lecture, read every FAQ page, take every note. This feels productive but is passive learning at scale. Dunlosky et al. (2013) ranked re-reading and highlighting as among the least effective study strategies — they create familiarity without durable memory. The AWS exam doesn't ask "have you seen this?" It asks "given this architecture, what breaks under load, and what's the cheapest fix?"
The theory-vs-practice gap compounds the problem. It's possible to memorize that DynamoDB uses partition keys without ever having queried a DynamoDB table. On exam day, those memorized facts fall apart when a scenario asks you to choose between DynamoDB, ElastiCache, and RDS based on query patterns. You need the mental model, not the bullet points.
The good news: the AWS exams are passable — and passable with high marks — if you replace passive study with deliberate retrieval, hands-on labs, and scenario drilling. Here's exactly how.
After each course section, close the video and write (without notes) every service, feature, or use case you remember. Be specific: not just "EC2" but "EC2 instance types, when to pick compute-optimized vs memory-optimized, On-Demand vs Reserved vs Spot pricing."
This is retrieval practice — one of the most reliably effective learning strategies in cognitive science. The struggle of recalling imperfectly is what builds durable memory. Don't re-watch a section until you've tried to recall it first.
AWS-specific tip: After covering a new service, try to answer: What problem does this solve? What's a scenario where this is the right choice? What's a scenario where it's wrong?
Don't make flashcards for AWS service definitions ("What is S3?"). Make them for decision points ("When should I use S3 Glacier Instant Retrieval vs S3 Glacier Flexible Retrieval?"). These are the exact trade-offs the exam tests.
Space your reviews: review new cards the next day, then 3 days later, then weekly. Upload your study notes to Snitchnotes and it will auto-generate comparison flashcards and practice questions in seconds — this is especially powerful for service-dense subjects like AWS.
Target spaced repetition toward: IAM permission boundaries, VPC networking concepts, storage class trade-offs, and database selection criteria — the highest-yield decision trees on associate exams.
This is the single biggest differentiator between candidates who pass on the first attempt and those who don't. AWS provides a free tier with generous monthly limits. Use it.
Build a static website on S3 + CloudFront. Set up an EC2 instance, attach an EBS volume, then take a snapshot. Create an RDS instance, connect to it, enable Multi-AZ. Deploy a Lambda function triggered by an S3 upload. These aren't optional extras — they're the hands-on context that turns abstract service knowledge into intuition.
Research by Kornell & Bjork (2008) on interleaved practice shows that switching between conceptual study and applied tasks accelerates learning faster than staying in one mode. Labs and lectures should alternate, not stack.
AWS exams love questions where three services all sound like they'd work, but one is clearly best for the described scenario. The solution: build your own comparison tables.
Example: SQS vs SNS vs EventBridge — when to use each, max message size, delivery guarantees, fan-out support, ordering. Do this for every cluster of similar services: Aurora vs RDS vs DynamoDB, CloudWatch vs CloudTrail vs Config, NAT Gateway vs NAT Instance.
Writing these tables forces you to identify differences, not just recognize them. It's elaborative interrogation — asking "why?" and "compared to what?" — which research shows produces significantly better retention than re-reading alone.
Jon Bonso's practice exams (sold via Tutorials Dojo) are the gold standard for AWS exam prep. They're harder than the real exam, and the explanations for why each wrong answer is wrong are worth as much as the right answer.
Do not use practice exams passively. For every question you get wrong: read the explanation, build a flashcard for the underlying concept, and note which service cluster the question came from so you can target your weak areas.
Shoot for 80%+ on practice exams before scheduling your real exam. The actual exam tends to be easier than Tutorials Dojo, which means 80% there typically translates to a pass with margin.
Timeline: 8–12 weeks for associate-level exams (shorter if you have hands-on cloud experience, longer if you're starting fresh).
Weekly framework:
Hours per week: 8–12 hours for a focused but sustainable pace. Crammers who try 20+ hours/week for 3 weeks consistently underperform candidates who spread it out.
When to introduce practice exams: Start at week 6–7, once you've covered the full curriculum. Don't start earlier — it builds bad patterns around guessing without knowledge.
Final week: 65-question timed practice exam each day. Review every wrong answer. Re-read weak-area notes (not re-watch videos). Sleep well before exam day.
Treating course completion as exam readiness. Finishing a Udemy course is week 3, not week 10. The course is a starting point. Practice exams, labs, and flashcard drilling are where learning actually happens.
Skipping hands-on labs. "I'll understand the concepts without building anything" is the most common path to a second attempt. Scenario questions require architectural intuition that only comes from doing.
Memorizing instead of understanding. Memorizing that "DynamoDB is NoSQL" won't help. Understanding when DynamoDB outperforms RDS — and specifically why (key-value access patterns, auto-scaling, global tables for multi-region) — is what the exam tests.
Ignoring the exam guide. AWS publishes a free exam guide for each certification listing every domain and its weighting. Solutions Architect Associate, for example, weights "Design Resilient Architectures" at 26%. Students who don't check the guide spend equal time on all topics — which means under-preparing for the highest-value domains.
Official resources:
Third-party:
Flashcards and active recall:
Most candidates need 8–12 weeks studying 8–10 hours per week. With hands-on cloud experience, 6 weeks is realistic. Without any cloud background, budget 12 weeks. Consistency beats cramming — AWS exams test understanding, not memory dumps, and that takes time to build.
Build service comparison tables: SQS vs SNS vs EventBridge, Aurora vs RDS vs DynamoDB, CloudWatch vs CloudTrail vs Config. Write these yourself — don't just read someone else's table. The act of building the comparison forces you to understand the distinctions the exam will test. Pair with hands-on labs to make the differences concrete.
The pass rate is around 70–75% for first-time candidates who prepare properly. The exam is challenging because it tests architectural judgment, not trivia. Questions present realistic scenarios with multiple plausible answers. Candidates who struggle are usually those who watched courses but skipped practice exams and hands-on labs. With 8+ weeks of structured prep, a passing score is very achievable.
Start with Solutions Architect Associate. It covers the broadest set of AWS services and builds the foundational architectural knowledge that makes every other certification easier. Developer Associate assumes some Solutions Architect knowledge and overlaps significantly. Solutions Architect is also the most widely recognized certification by employers for cloud roles.
Absolutely. AI tools are particularly useful for AWS because the subject involves so many services with subtle differences. Upload your notes or course summaries to Snitchnotes and it generates flashcards and practice questions tailored to your material. Use AI to quiz yourself on scenario-based questions — it's like having a study partner who knows every AWS service.
Passing AWS Certification — whether it's the Solutions Architect Associate, Developer Associate, or SysOps Administrator — comes down to three non-negotiables: hands-on labs, service comparison mastery, and aggressive practice exam drilling. Passive video watching gets you familiar with AWS. Active recall, real projects, and scenario practice are what get you certified.
Start with the AWS exam guide, pick a structured course, and commit to at least one hands-on lab per study session. Use Snitchnotes to turn your course notes into flashcards and practice questions — it's the fastest way to identify which services you actually understand versus which ones you've just heard of.
Eight to twelve weeks. Consistent effort. Hands on keyboard. You've got this.
Apuntes, quizzes, podcasts, flashcards y chat — con solo subir un archivo.
Prueba tu primer apunte gratis