As I progressed through my AWS learning journey, I went from being familiar with EC2 to working with services like Lambda, IAM, VPC, RDS, DynamoDB, Aurora, and several others.
At some point, I felt I had built enough knowledge to take the AWS Certified Solutions Architect – Associate exam.
Until I decided to solve Tutorials Dojo practice questions.
That was my rude awakening.
I quickly realized that knowing AWS services was not the same as knowing how to architect solutions on AWS.
I came across Tutorials Dojo frequently while researching how other people prepared for the exam, especially through the AWS Certifications Reddit community.
NB: This Reddit community was extremely helpful throughout my preparation. If you're preparing for an AWS certification, I'd recommend spending some time going through the posts, discussions, study tips, and experiences shared there.
The exam was testing something different
The scenario-based questions weren't simply asking:
"What does this AWS service do?"
They were asking me to think through situations such as:
- Which architecture best satisfies these requirements?
- What is the most cost-effective solution?
- Which solution provides the highest availability?
- What trade-offs should I consider in this scenario?
- Which service or configuration minimizes operational overhead?
- Which option satisfies the requirements with the least amount of change?
That was when I realized I had to change my study approach.
I was studying AWS services.
The exam was testing whether I could use those services to make the right architectural decisions.
That changed how I approached my preparation.
I stopped studying only for knowledge and started practicing for decision-making
I went through Stephane Maarek's AWS Solutions Architect Associate course on Udemy to build and strengthen my understanding of the exam objectives and AWS services.
But I didn't stop there.
I used Tutorials Dojo extensively to get accustomed to the scenario-based nature of the questions.
I primarily used the review mode, and I developed a simple rule for myself:
Every wrong answer had to become a learning opportunity.
If I got a question wrong, I didn't just look at the correct answer and move on.
I read the explanation carefully to understand why I got it wrong.
I wanted to understand:
- Why was the correct option correct?
- Why were the other options wrong?
- What requirement in the question eliminated the other choices?
- Was I misunderstanding an AWS service?
- Was I missing a key architectural concept?
- Was I choosing a technically valid solution when the question was asking for the most cost-effective, most highly available, or least operationally complex solution?
Whenever the explanation wasn't enough for me, I used ChatGPT to break the concept down further and help me understand the reasoning behind the answer.
This became more important because I was trying to get better at recognizing the architectural pattern behind the question.
I also used AWS Skill Builder to supplement the other resources I already had. I didn't want to take any chances with my preparation, so I used it to reinforce areas where I felt I needed more understanding.
My preparation eventually became less about memorizing AWS services and more about understanding trade-offs, requirements, architecture, cost, availability, performance, and operational complexity.
That shift from theoretical study to high-intensity, scenario-based practice changed my preparation completely.
And eventually, it paid off.
I passed the AWS Certified Solutions Architect – Associate certification.
This is such a significant milestone for me in my Cloud and DevOps career.
Onto the next.
Also if you have any questions, don't forget to reach out to me on LinkedIn
Top comments (0)