11.3 Certification: which one, and how to prepare
Describes the projects, certifications and interview practice as of August 2026
What this is and why it exists
A certification is a signal, not a skill, and this lesson is about deciding whether the signal is worth buying in your situation — then preparing for it without spending money on courses you do not need. Three entry-level certifications cover the same ground you have learned in this subject, and the specifics of each — what the exam covers, how it is structured, what it costs, what is on the current version — belong to the vendor's own page under Go deeper, because those details change and a lesson that recited them would be wrong by the time you sat down.
The vocabulary
- Entry-level (or foundational) certification — one aimed at understanding cloud concepts and a provider's services, rather than at hands-on engineering.
- Associate level — the next step up, assuming real working experience.
- Exam guide — the vendor's own document listing what is examinable, which is the only authoritative scope.
- Official learning path — the vendor's free training aligned to that guide.
- Practice questions — questions in the exam's format, used to find gaps rather than to memorise answers.
- Recertification — the fact that certifications expire, and the ongoing cost that implies.
The mental model
The three entry-level certifications are AWS Certified Cloud Practitioner, whose current code is CLF-C02; Microsoft Certified: Azure Fundamentals, AZ-900; and Google's Cloud Digital Leader. They cover much the same territory — what cloud is, the service categories, security and shared responsibility, pricing and support — which is most of what this subject has taught you. Choose by the ecosystem you are heading into, not by which exam is easiest. If the employers you are applying to run on one provider, that provider's certificate is the one that means something to them; if you have no signal at all, pick the provider with the strongest hiring presence in your city and go with it.
Then the honest question of whether to sit one, because the answer is genuinely not always yes. A certificate is worth buying when it gets your application read: when job listings you are actually applying to name it, when a recruiter's filter uses it, when an employer's partner status requires certified staff, or when you need something dated to show a gap was spent learning. It is worth much less when you already have work to show — and after the two projects in this module, you do. An interviewer given a repository with infrastructure code, an architecture diagram and a story about a cost reduction has more evidence than any exam provides. The right order for most students is projects first, certificate second, and never a certificate instead.
Preparing costs nothing but time, and the method is the same for all three. Start from the vendor's exam guide, because it is the only authoritative statement of scope and everything else is somebody's interpretation of it. Work the vendor's own free learning path, which is aligned to that guide by the people who wrote it. Use practice questions as a diagnostic rather than a study method: sit a set, and for every question you got wrong — and every one you guessed right — go and read the actual documentation for that service until you could explain it to somebody else. That last habit is the difference between passing and knowing, and it is what makes the certificate honest.
Two cautions worth carrying. Paid courses and question banks are heavily marketed to people in exactly your position, and they are almost never necessary at this level, where the vendors publish thorough free material aligned to their own exams. And a certificate expires, so it is a recurring commitment rather than a one-off — which is another reason to be sure the signal is worth buying before you buy the first one.
What you should now be able to explain or do
Name the three entry-level certifications and say what they broadly cover. Choose one for your own situation and defend the choice on ecosystem rather than difficulty. Say four situations in which a certificate genuinely helps, and one in which your projects are worth more. Describe a preparation plan using only free vendor material. Explain how to use practice questions as a diagnostic rather than a memory exercise.
Check yourself
How should you choose between the three?
By the ecosystem you are heading into — the provider your target employers use, or the one with the strongest hiring presence where you are. Not by which exam has the reputation of being easiest.
Where does the authoritative scope of an exam live?
In the vendor's own exam guide. Everything else is an interpretation of it, and the details change between versions, which is exactly why they are not written into this lesson.
When is a certificate genuinely worth it?
When it gets your application read — named in listings you are applying to, used by a recruiter's filter, required by an employer's partner status, or needed as dated evidence that a gap was spent learning.
You have finished both projects in this module. What does that change?
It raises the bar a certificate has to clear. A repository with infrastructure code, a diagram and a real story about a cost reduction is stronger evidence than an exam result, so the certificate becomes an addition rather than the point.
How should practice questions be used?
As a diagnostic. For each one you got wrong — and each one you guessed right — read the real documentation for that service until you could explain it. Memorising answers passes an exam and teaches nothing.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to Certification: which one, and how to prepare: work through the checklist