A cloud engineer is not a junior architect. The role is hands-on: provisioning infrastructure, writing automation, fixing broken deployments at 4 pm on a Friday, and keeping cost and monitoring dashboards honest. That distinction matters before you spend a penny on exams, because the certifications that serve this role are the operational, keyboard-first ones — not the design-heavy architect track, and not a stack of entry-level badges. What follows is a sequenced path: what to learn before any exam, which single associate certification to book, and what to layer on once you are doing the job.
Short answer: build Linux and networking basics first, take at most one fundamentals exam (or skip that tier entirely if you are already in IT), then earn one hands-on associate certification — Microsoft's AZ-104 Azure Administrator, Google's Associate Cloud Engineer, or AWS Solutions Architect – Associate — while building real automation projects alongside it. That combination, not a wall of certificates, is what gets people hired as cloud engineers.
If you want a ranked comparison of cloud certifications across providers and roles rather than a path into this specific job, our best cloud computing certifications round-up handles that in one sentence-saving place. And if your long-term ambition is the architect's chair rather than the engineer's, the solutions architect certification path is a different sequence.
Step 0: the unexamined foundations (no certificate required)
Every cloud platform is, underneath, Linux boxes and networks. Before studying for any cloud exam, make sure you can comfortably: navigate and script in a Linux shell; explain IP addressing, subnets, DNS and firewalls; and use Git. None of this requires a certification — free labs and a laptop cover it — but skipping it is the single most common reason people pass a cloud exam and still fail cloud interviews. If you are coming from a Windows-centric sysadmin background, the system administrator certification ladder shows how that experience maps across.
Infrastructure-as-code belongs here too. Terraform appears constantly in cloud engineer adverts; you do not need a Terraform certification to start, but you do need a repository showing you can define a network and a couple of services in code. Treat tooling fluency as a portfolio item rather than an exam item at this stage.
Step 1: decide whether you need a fundamentals exam at all
The fundamentals tier — AWS Certified Cloud Practitioner ($100), Microsoft's AZ-900 Azure Fundamentals (country-based pricing, commonly cited around US$99), and Google's Cloud Digital Leader ($99 plus tax) — exists to teach cloud vocabulary and billing concepts. None is a prerequisite for anything: AWS, Microsoft and Google all let you sit associate and even professional exams directly.
Take a fundamentals exam if you are new to IT, changing careers, or need a low-stakes first win: AZ-900 never expires, Cloud Practitioner runs 65 questions in 90 minutes, and both are far cheaper than the associate tier. Skip the tier if you already work in IT and can pass a fundamentals practice set cold — put the money towards the associate exam instead. One useful quirk: passing any AWS exam, including Cloud Practitioner, earns a 50% discount voucher for your next AWS exam, which softens the cost of the associate step.
Step 2: choose and earn your core associate certification
This is the certification that changes your CV. Pick exactly one, matched to the platform your current or target employers run:
If Azure: AZ-104 Azure Administrator Associate
AZ-104 is the anchor Azure operations credential and the closest thing Microsoft offers to "cloud engineer, certified". The 100-minute proctored exam covers identities and governance, storage, compute, virtual networking, and monitoring — precisely a cloud engineer's day job. There are no formal prerequisites, though Microsoft recommends hands-on experience with the portal, PowerShell, Azure CLI and ARM/Bicep templates. Passing needs 700 on a 1,000-point scaled score (that is not 70% — the scale is not a percentage). Pricing is set per country; US$165 is the commonly cited US figure, but confirm at booking. The certification expires after 12 months, renewed free through an open-book online assessment — an annual nudge, not an annual bill. AZ-104 also happens to be the mandatory stepping stone if you later want the Azure Solutions Architect Expert credential, so nothing is wasted.
If Google Cloud: Associate Cloud Engineer
Google's Associate Cloud Engineer is the most literally named option — the exam was built for this role. Expect 50–60 multiple-choice and multiple-select questions over 2 hours, for $125 plus tax; Google recommends 6+ months of hands-on experience and publishes no passing score (results are pass/fail only). Google Cloud exams have no codes, so ignore any resource selling "GCP-ACE" — that is an invented label. The certification lasts 3 years, and Google now offers a shorter renewal exam (20 questions, 1 hour, $75) so you are not re-sitting the full thing. Note the retake rules are stricter than the other providers': a failed attempt means a 14-day wait, rising to 60 days and then a year, with at most 4 attempts in 2 years.
If AWS: Solutions Architect – Associate (with a note on CloudOps)
AWS's portfolio splits the engineer's job across exams. SAA-C03 (65 questions, 130 minutes, $150, 720 scaled to pass) remains the credential AWS-shop recruiters search for, even for engineering rather than architecture roles, which is why it earns the recommendation here. The operations-purist alternative is the AWS Certified CloudOps Engineer – Associate (SOA-C03) — and yes, that is the renamed SysOps Administrator, updated and relaunched in September 2025, not a retired exam as forums sometimes claim. Same $150 fee, same 65-question/130-minute shape, no lab component. If your target adverts say "AWS cloud engineer", holding SAA-C03 plus demonstrable automation skills covers you; add CloudOps later if your role tilts heavily operational. All AWS certifications run on a 3-year cycle.
Whichever exam you choose, do not book it on hope. Work through the official exam guide, lab every domain, then take a full-length timed practice test and read the results by domain: a weak-networking column tells you exactly where the next fortnight goes. ExamPractice's free sample questions let you gauge the question style before committing to the full simulation — and the goal is understanding the objectives, never memorising answer letters.
Step 3: prove it with projects while the certificate is fresh
A realistic scenario shows why this step is not optional. Two candidates hold AZ-104. One lists the badge. The other links a repository that deploys a three-tier app with Bicep, wires up monitoring alerts, and includes a README explaining a cost-reduction decision. The second candidate gets the interview, because cloud engineering interviews are show-me conversations. Budget as many hours for building as for studying: a deployed project per major exam domain is a good rule of thumb, and it doubles as revision.
Step 4: specialise once you are in the seat
After landing a cloud engineer role, let the job pick your next exam rather than collecting credentials speculatively. Common second moves:
- Automation and delivery: AWS Certified DevOps Engineer – Professional (DOP-C02: 75 questions, 180 minutes, $300 — passing it also renews the associate-tier Developer and CloudOps certs) or Microsoft's AZ-400 DevOps Engineer Expert, which requires holding AZ-104 first now that the AZ-204 route has been retired.
- Networking depth: AZ-700 on Azure, or Google's Professional Cloud Network Engineer.
- Security lean: AWS Certified Security – Specialty (now SCS-C03) or Google's Professional Cloud Security Engineer.
- Second platform breadth: an associate exam on a second cloud, useful in consultancies and large enterprises.
One warning for anyone sequencing a Microsoft path from older blog posts: Microsoft retired a wave of certifications between 2025 and 2026 (AZ-204 and AZ-500 among them), so verify any Azure exam code on Microsoft Learn before buying a voucher.
Readiness checklist before you book the associate exam
- You can build, break and rebuild the exam-guide scenarios in a lab account without following a tutorial line by line.
- You can explain, aloud, why you would choose one storage or compute option over another for a given workload.
- A timed, full-length practice test lands you comfortably above the pass line with time to spare — and your per-domain results show no domain in freefall.
- You have at least one deployable project in version control per platform you claim.
- You have confirmed the current exam version, fee and local pricing on the provider's official page this month, not from a cached blog post.
What the role pays — honestly
No survey gives "cloud engineer with certification X earns Y", and be suspicious of any page that does. The credible anchors: Robert Half's 2026 US Technology Salary Guide lists a midpoint of $145,750 for DevOps engineers — the nearest listed cousin of the cloud engineer role — with US tech salaries overall projected to rise about 1.6% into 2026, and the US Bureau of Labor Statistics put the median for network and computer systems administrators at $96,800 (May 2024). Real offers swing widely with location, sector and experience; certifications move you into the interview, and experience moves the number.
Your first two quarters, mapped
Quarter one: foundations and a decision — Linux, networking and Git fluency, a chosen platform, and either a fundamentals pass or the deliberate choice to skip it. Quarter two: the associate certification earned the honest way, with a project portfolio grown alongside it and a timed practice-test benchmark before booking day. That is the whole entry path. Everything after — professional-tier exams, specialties, a second cloud — should be pulled by a job you are already doing, not pushed by a list you read online. Where the full multi-year ladder across providers goes from there, our cloud computing certification roadmap picks up the sequencing.