Service Desk to Cloud.

What the AWS or Azure exam actually proves, what it doesn't, and the four foundations the interviewer assumes you already have.

Verdict

Cloud is the route that looks shortest from the outside and almost never is. The cert gets you into the interview. It does not get you the job. The hiring manager assumes the AZ-104 or the SAA. They are testing whether you can operate a Linux box, read a packet trace and not panic when something stops working. Most desk-to-cloud candidates have the first and not the others.

Who this is for

·Desk staff already comfortable on the Linux command line in anger, not in a tutorial.
·People who have already deployed something small, even if it broke twice.
·Anyone willing to spend 6 to 12 months on foundations before the cloud cert.

Who this isn't for

·Anyone hoping the AZ-900 plus a Udemy course is enough to get hired. It isn't.
·Anyone who wants the cloud title fast. The compressed version costs you in year two.
·Anyone who can't articulate what a subnet is without looking it up.

The thing the cert can't tell you

What an AZ-104 actually proves.

It demonstrates assessed knowledge and skills within the vendor’s published exam scope. Microsoft exams can use different question formats; check the current AZ-104 guide and exam experience before preparing. That is a real and useful signal. It is not the same signal as "this person can run a system in production". Those are two different jobs. The cert tests one of them.

Inside ten minutes of a technical interview, the gap shows. The candidate who only has the cert talks in service names. The candidate with foundations talks in behaviours. Hiring managers can tell which is which inside two questions.

Named observation

Cloud Without Foundations.

An AWS or Azure pass with no Linux, no scripting, no real networking and no production exposure. Reads as paper-thin inside ten minutes of a technical interview. The cert is real. The gap underneath it is what loses the offer.

The four things underneath

What the interview is actually checking for.

Linux on the command line, in anger. SSH into a box, read the logs, restart the service, work out why disk filled. If you can't do that, the cloud cert is decoration.
Networking enough to debug it. Subnets, routing, DNS resolution, what a security group does, what a NAT gateway is for. Not memorised. Diagnosed.
A scripting language you can converse in.Bash and Python. Enough to read somebody else's code, change it, and not break the surrounding script.
A small thing you've actually shipped. A Terraform repo that stands up a VPC and a couple of services. Public. Linked from the CV. Two weekends of work that survives the first scenario question.

Cloud assumes you can already operate a system. The cloud part sits on top of those skills, not in place of them.

Where it goes wrong

The mistake that turns the cert into a tax.

The most expensive version of this route is the one where the cert comes first and the foundations come after the rejection. Six months of study, a £200 exam, a CV update, twenty applications, three interviews, three no-thank-yous. Then the realisation that the gap was never the cert.

People who pay that tax usually pay it again. The second cloud cert doesn't fix the first interview either. That's the part the cert influencers don't sell.

Named observation

Certification Substitution.

The instinct to fix an interview problem by adding a second certification rather than the missing skill underneath. Common after the first round of rejections. Almost never works. Hiring managers reading the second cert assume the candidate didn't understand why the first one wasn't the answer.

The honest part

The cloud route works. It works best with a year of infrastructure or sysadmin work underneath it, and it works second-best with the foundations done deliberately in your own time. Neither version is the version the cert marketing sells.

Whether the sideways move is open to you is the actual question, and it's not one a guide can answer in the abstract. The Route Planner is where that conversation happens.

Next step

Pick the role you think you're aiming at and see what the route actually looks like from where you are. Honest, hop by hop, with the parts that tend to break.

See your route into Cloud