I Passed AWS Cloud Practitioner — Later Than Planned, but Still Moving Forward
Yesterday, I passed the AWS Certified Cloud Practitioner (CLF-C02) exam.
Finally! What a relief.
I had originally intended to take it earlier, but balancing personal responsibilities and professional priorities disrupted that schedule. Finding consistent time and energy to prepare was harder than I expected.
I’m sharing this because certification announcements usually show the result. They don’t always show the revised schedules, interrupted study sessions, or uncertainty that came before it.
Here’s what my preparation looked like and what I learned along the way.
The study method needed to change
I used Jason Dion’s Cloud Practitioner preparation course on Udemy.
Initially, I took extensive notes while watching. Eventually, I realized I was copying nearly every slide. I was putting in time, but creating a second version of material I already had wasn’t the best use of that time.
I changed my approach and watched the videos at 2× speed, which suited how I prefer to consume video content.
I wouldn’t present playback speed as a shortcut everyone should use. The important change was recognizing that my original method wasn’t working efficiently for me and being willing to adjust it.
The practice-test explanations were a major part of the learning
I also purchased Dion’s six practice tests.
I took each test once and read the explanations for every answer, including the questions I answered correctly.
That distinction mattered. Getting a question right didn’t always mean I understood the concept thoroughly. Sometimes I could eliminate unlikely choices without being entirely confident about the remaining answer.
Reviewing the explanations helped me see where my understanding was solid and where it needed more work.
Get Ismail Abdur-Rahman’s stories in your inbox
Join Medium for free to get updates from this writer.
Honestly, I learned as much from that process as I did from the course. AWS has a broad range of services, and the challenge wasn’t simply recognizing names. It was understanding which service addressed a particular requirement — and why the alternatives didn’t fit as well.
Service names can offer clues
One observation I found useful was that many service names contain clues about their purpose.
Amazon Elastic Kubernetes Service, for example, gives you a clear starting point: Kubernetes.
That sounds obvious, but when you’re working through unfamiliar terminology, making those connections can help.
There’s a limit to this approach, though. A descriptive name might help identify the general category, but it won’t necessarily explain the service’s limitations, operating model, or suitability for a specific scenario.
I found it useful as a reasoning aid, not a replacement for studying.
Security helped connect the concepts
Security stood out throughout my preparation and exam experience.
Rather than treating security services as another list to memorize, I found it more useful to think about the underlying questions: What needs protection? What kind of threat are we addressing? Which responsibilities belong to AWS, and which remain with the customer?
That framing helped the services make more sense.
What comes next
I plan to begin preparing for AWS Certified Solutions Architect — Associate next week, with a provisional goal of taking the exam in late December.
At the same time, I’ll continue building projects that demonstrate my ability to solve real business problems with AWS.
The next certification is a useful goal, but I also want evidence that I can apply what I’m learning, explain my decisions, and work through problems when something doesn’t behave as expected.
For now, I’m grateful to have completed this milestone.
The schedule changed. The goal didn’t.
Onward.
