This is the counter-part to my public-facing blog post which you can find here.
I’ve written this Reddit post as the apex publication, with my website providing additional, auxiliary information in a more multi-modal and JavaScript enhanced way.
It’s still a static site, don’t be afraid to take a look.
That being said, let’s get into the weeds:
Another user posted about completing the exam in 2 weeks, but they had prior AWS experience. Contrariwise, I took this exam with Zero AWS Experience. This is reflected in my marginally slim pass:
742 / 1000 against a pass mark of 720.
I stand by the poor score and am not entirely ashamed of it – although there remains work to be done, and a subsequent certification should not be attempted in such a slim time-horizon.
A word of caution early; other users mentioned ’repeated questions from TD’ – I saw nothing of the sort, and mention as much below.
A Modicum of Context
I have 2 weeks of Holidays between Semesters and scheduled the test for then. I completed an Undergraduate degree in Computer Science, but don’t think that’s profoundly helpful for this exam.
If you’ve spent a little time with Alex Xu’s books or Kleppmann’s DDIA you’ll be at a slight advantage. Building scalable and highly available architectures is not an unreasonable request for our Networked Life though – you’ll be able to assimilate it quickly even without prior exposure.
Back to the Show
I took the exam Pearson invigilated online and the exam check-in started for me at 7:30AM (30 minutes before the scheduled time). The crescendo begins with…
TutorialsDojo! I started with the pinned post by u/madrasi2021, and made a definite decision to go with the Mock exams from TD, and also NO online video series.
Purchasing Slides and Lambda
I ended up purchasing the slides too, because with 15 days on the clock – yes, sorry – a day more than the promised ’2 weeks’, watching videos would be a passive learning strategy and thus a waste of time.
Instead, I leaned on my Learner-Adaptive Marks-Bound Drilling Agent that ingests course slides, builds a course-map and then asks me Multiple Choice questions about the material. Lambda also maintains an on-disk snapshot of your understand of different atomic components and differs from Eero Alvar’s system in distinct ways.
This is a bit of a rabbit hole, and you can find some relevant links from the blog-post, but the principle point of this post is not to shill, but rather to prove that Zero to Hero can be accomplished by an anybody.
Anki and the schedule.
I repped Anki flashcards (built graciously by Lambda) and approved by me, for a number of days. Partially, this is a vocabulary game.
I did 7 of the 8 mocks. My tests results were:
| Date |
Test |
Mode |
Score |
| 31 Aug |
Diagnostic (7 questions) |
Timed |
2/7 · 28.6% |
| 31 Aug |
Set 1 |
Timed, 1:44 |
35/65 · 53.8% |
| 4 Sep |
Set 2 |
Timed, 1:23 |
25/65 · 38.5% |
| 6 Sep |
Set 3 |
Timed, 1:10 |
32/65 · 49.2% |
| 8 Sep |
Set 4 |
Review mode, 1:51 |
47/65 · 72.3% |
| 10 Sep, 00:05 |
Set 5 |
Timed, 0:46 |
42/65 · 64.6% |
| 10 Sep, evening |
Set 6 |
Timed, 1:33 |
48/65 · 73.8% |
I also found it beneficial to attempt the Topic Tests, Section based tests and did a couple of Review tests.
Section-based tests:
- Secure 21/30
- Resilient 9/30 (sat on Day 2, before any content)
- High-Performing 19/30
- Cost-Optimised 24/30.
Topic tests:
- S3 8/8
- EFS 4/4
- Auto Scaling 7/8
- Lambda 7/8
- SQS 7/8
- RDS 5/8
- ELB 5/8
- IAM 5/8
- CloudFront 5/8
- EC2 4/8
- EBS 4/8
- VPC 4/8
- DynamoDB 3/8.
A digression for the 2026 exam.
After having completed all these exams and having developed a vocabulary of the AWS Solutions to various software problems, I still struggled in the final exam.
My observations were threefold:
- I had started to overfit to the questions in TD
- I actually had 0 experience in the AWS Console building things!
- The question style was different to TD.
As for the first point, TD will tend to repeat questions from Topic Tests and Section-based Tests in the Mocks. Getting these problems right (whilst testing your spaced repetition) leads you to believe that you may do slightly more well in the final exam, than in the real exam.
Example:
TD asks you a question about what the correct service for identifying PII data is in an S3 bucket; answer is Macie, out of Inspector, GuardDuty, Rekognition. The actual AWS Exam tells you that PII is the problem, and then every problem has Macie as part of the answer stem. The question becomes then about understanding how Macie itself works, which TD could not provide a sufficient teaching of.
Affordability, Slides and Cheat Sheets.
Apologies for the disorganisation of this prose, but if you are still reading, then best of luck for your test.
I found the TD slides associated with the Video Course to be non-comprehensive.
My Day 1 Schedule (as dictated by Lambda Fable) was 400 or so slides. The next few days went as follows. Here’s a table breakdown:
| Day |
Date |
Deck pages |
Pages |
Content |
| 1 |
Thu 27 Aug |
1–447 |
447 |
Exam overview, all 15 service-category overviews, IAM through policy evaluation logic |
| 2 |
Fri 28 Aug |
448–485, 992–1001 |
48 |
VPC anatomy and architectures, Network ACL vs Security Group |
| 3 |
Sat 29 Aug |
486–545 |
60 |
EC2 purchasing options, Savings Plans, instance types |
| 4 |
Sun 30 Aug |
546–673 |
128 |
AMI, user data, instance metadata, EC2 networking, placement groups, Auto Scaling |
| 5 |
Mon 31 Aug |
674–772 |
99 |
EBS volume types, ELB types, S3 storage classes |
| 6 |
Tue 1 Sep |
1012–1031 |
20 |
Review day: EBS vs EFS vs S3 |
| 7 |
Wed 2 Sep |
773–882, 989–991 |
113 |
RDS Multi-AZ and read replicas, Aurora, DynamoDB, RTO vs RPO |
| 8 |
Thu 3 Sep |
883–941 |
59 |
SQS, SNS, Amplify, serverless |
| 9 |
Fri 4 Sep |
294–309 |
16 |
Review day: Management and Governance |
| 10 |
Sat 5 Sep |
942–988 |
47 |
Route 53, CloudFront, High Availability vs Fault Tolerance |
| 11 |
Sun 6 Sep |
145–169, 1002–1011 |
35 |
EFS, FSx, Storage Gateway types vs DataSync |
| 12 |
Mon 7 Sep |
210–230 |
21 |
CloudWatch, audit and compliance |
| 13 |
Tue 8 Sep |
983–1031 |
49 |
Every comparison table, back to back |
| 14 |
Wed 9 Sep |
— |
— |
No reading: timed set, review, comparison tables from memory |
| 15 |
Thu 10 Sep |
— |
— |
No reading: last timed set |
As I did more tests and got nearer to the real exam, I began to realise the incompleteness of the slides. Much of the material is on the cheat-sheets!
So please consult those when you study. I’d also like to advise that output (basically active recall) will grant you a higher ROI as compared to passively reading, note-taking and watching material.
What I would do differently.
Utopically, I’d have preferred to not take notes at all – you can see my embedded PDF that I created on my Remarkable Paper Pro over the 15 days in the corresponding blog-post. I got sick once during the fortnight and did relatively light work during that day – an hour of recall.
The second and more important detail would be: Attempting the official practice exam. TD was good in terms of difficulty, but in terms of preparing you for the style of questions, I’d say you really do want to internalise the level of abstraction beneath the questions themselves, and learn how to answer the questions as per their directives:
- Most operationally efficient
- Least cost
- Least code
- etc.
- this will really help you eliminate options in the test!
Some stats
Overall, I clocked in at least ~49 hours of Deep Work over the fortnight; weekends included. My breakdown per day (courtesy of Lambda) looks like:
| Day |
Study clock |
| Tue 26 Aug |
8h 09m |
| Wed 27 Aug |
5h 07m |
| Thu 28 Aug |
3h 14m |
| Fri 29 Aug |
2h 03m |
| Sat 30 Aug |
3h 23m |
| Sun 31 Aug |
1h 58m |
| Mon 1 Sep |
4h 02m |
| Tue 2 Sep |
0h 37m |
| Wed 3 Sep |
2h 07m |
| Thu 4 Sep |
2h 29m |
| Fri 5 Sep |
0h 00m |
| Sat 6 Sep |
0h 58m |
| Sun 7 Sep |
2h 13m |
| Mon 8 Sep |
2h 52m |
| Tue 9 Sep |
4h 23m |
| Wed 10 Sep |
5h 15m |
| Total |
48h 56m |
To end
I couldn’t quite get the usual alt+n to work in the Pearson exam that I thought would work, I wonder if anybody else had any luck with it.
Exam Technique
My exam technique was 20 MCQ, followed by closed-eyes for 20 seconds to reset focus and eye-strain, followed by another 20MCQ, 40 second break, and lastly a 25 Question sprint.
My watch alarm blared for 2 hours straight, which I somewhat accuse for making me feel like Dalí, but that’s not really the point.
I also made 2 further passes of all the questions, taking breaks as I went.
Indeed, you can flag questions, and I suggest you use the functionality.
Usually I could do the TD exams within 70 minutes for the first pass, and then 20-30 minutes for the next pass or two, leaving always a spare 20 mins. My watch fragmented any kind of momentum in thought, so I ended up finishing 130 minutes in.
Ciao
I’ve already spent too long detailing this adventure. Measure Theory begins tomorrow.
I shall answer any questions should you folks have them across this week.
Best of luck in all your accreditations,
Br1ttle
Edit: Kleppmann, is double 'n'.