10 AZ-104 Interview Questions That Have Nothing to Do with PowerShell

You passed AZ-104. You can write Get-AzVM in your sleep. Conditional Access policies, Exchange hybrid deployments, route tables, storage redundancy tiers — you've studied the blueprint and the questions that flow from it. You're technically ready.

And then the hiring manager asks: "Tell me about a time you accidentally deleted a resource in production." And you freeze, because nothing in the practice exam prepared you for the only part of the interview that actually determines whether they call back.

The AZ-104 tests Azure knowledge. The AZ-104 interview tests Azure judgement — which is a different thing, and the industry hasn't agreed yet to teach it. Below are ten questions we see come up again and again in real Azure Administrator interviews, organised by what the interviewer is actually measuring. None of them are about PowerShell syntax. All of them can unpass you.

Every one of these questions is answered better with one specific example than with three paragraphs of theory. If a question starts with "Tell me about a time…" and you start your answer with "Well, typically…" — you've already lost the room.

1. "Tell me about a time you accidentally deleted a resource in production."

What they're measuring: accountability, blast-radius awareness, recovery discipline. Can you own a mistake cleanly? Did you know the right buttons to press? What did you change after?

The answer shape they want: a specific situation (one customer, one resource, one morning), the exact action you took in the first 60 seconds (rollback source, backup, soft-delete retention, incident channel), and what you changed in the environment afterward (resource locks, policy, Bicep template, RBAC). The structural giveaway: you describe a concrete control that now prevents the same mistake.

Common mistake: blame-shifting ("someone had given me prod access by mistake"). The interviewer isn't grading your innocence; they're grading your ownership.

2. "How do you explain Azure Governance to a non-technical CEO?"

What they're measuring: communication under translation pressure. Senior admins talk to engineering; lead admins translate to the business. Being able to say "Policy + RBAC + Blueprints" to another admin is easy. Saying it in a way your CFO understands is the actual job.

The answer shape they want: a business metaphor first (think "building code for cloud resources" or "guardrails on a motorway"), then one concrete payoff the CEO will recognise (cost control, audit readiness, reducing the chance of the $200k surprise bill), then — only if they ask — the technical stack beneath it.

3. "Walk me through how you'd right-size a production VM that's over-provisioned."

What they're measuring: disciplined process, not the magic right answer. Do you gather data before changing things? Do you communicate before changing things? Do you have a rollback?

The answer shape they want: Azure Monitor + Advisor for baseline data over at least a week; check burstable vs sustained load; confirm owner and change window; resize in non-peak; monitor for regressions. The shape matters more than the tool.

4. "A stakeholder walks in on Monday morning. The Azure bill doubled over the weekend. You have 20 minutes before a board meeting. What's your first move?"

What they're measuring: grace under pressure. The candidate who blurts out a tool name (Cost Management!) is already behind the candidate who says "I'd ask three questions first."

The answer shape they want: Stabilise before you investigate. Take a deep breath, set expectations with the stakeholder ("I'll have a first read in 10 minutes, a plan in 20, a full root-cause by end of day"), then jump to Cost Management's Analysis view grouped by Service and by Resource Group. The stabilisation step is what senior admins do differently.

5. "Tell me about a time you disagreed with a senior architect's design."

What they're measuring: technical courage paired with political sense. Teams hate the admin who always nods; they also hate the one who always argues. They want the one who picks the right fights.

The answer shape they want: a specific technical disagreement (hub-and-spoke vs flat VNet, whatever), how you documented your concerns in writing rather than in a meeting, what compromise you reached, and — critically — whether the decision ended up being right. "We did it their way and it failed" and "we did it their way and it worked" are both legitimate endings if you tell the story well.

6. "How would you convince a team to migrate from VMs to Azure Container Apps?"

What they're measuring: whether you lead with technology or with the team. The wrong answer starts with container benefits. The right answer starts with: whose problem am I solving?

The answer shape they want: acknowledge the team's current investment, identify the specific pain (deployment speed? cost? scaling?), map that pain to a migration outcome, propose a low-risk wedge (one stateless service, reversible), then scale. Engineers who migrate things because they're "better" usually end up with half-migrated estates; engineers who migrate things because a specific person asked for a specific outcome finish the job.

7. "A user's Conditional Access policy is blocking them five minutes before they present to a client. They ring you. What do you do?"

What they're measuring: triage instinct, change-management discipline, and whether you respect the change window even when it's inconvenient.

The answer shape they want: identify the blocking policy from sign-in logs, confirm the user's identity out-of-band (because you do not take action based on an unverified phone call), apply the smallest possible temporary exception (named user, time-bound, logged), and schedule the real fix for the change window. The candidate who says "I'd just exclude them from CA" loses. The candidate who describes the audit trail wins.

8. "What's the last thing you learned about Azure that changed how you work?"

What they're measuring: curiosity and recency. A senior admin who can't answer this is a senior admin who stopped growing; one of the most reliably predictive questions for seniority fit.

The answer shape they want: something concrete and recent (last three months), not a cert you passed — a feature you discovered, a design pattern you started using, a limitation you bumped into. Bonus points for describing a small habit change: "Now I always…" or "I used to… and I don't anymore because…".

9. "How do you document architectural decisions so the next admin understands why, not just what?"

What they're measuring: systems thinking. Admins who produce good ADRs or decision logs compound their team's effectiveness; admins who don't leak tribal knowledge every time they change jobs.

The answer shape they want: a specific artefact you actually use — ADR template, runbook repo, architecture-as-code with inline comments, Confluence with versioned RFCs. Include one example of a decision you documented and how someone later referenced it.

10. "Where do you want to be in three years?"

What they're measuring: whether hiring you is a long-bet or a stopgap. The answer they want depends on the role — ambition is a feature for cloud-engineer roles, a flag for senior-admin roles where continuity is the whole point. Read the room.

The answer shape they want: a specific direction that intersects with the role you're interviewing for. "Azure Solutions Architect Expert by year two, leading a small cloud platform team by year three, still hands-on with Bicep" is infinitely better than "grow into a senior role". The second answer means you don't know what the first rung is.

What this looks like on your InterviUni profile

Every answer above maps to one or more of the five dimensions we track on your IT Identity. The ten questions between them exercise every axis. This is the target profile for an Azure Administrator at the "senior, hire-ready" level — the bar these questions are aimed at:

The dimensions that actually move with the ten questions above are EQ (questions 1, 5, 10), Communication (2, 6, 9), and Stress Resilience (4, 7). Technical Depth is already high if you've passed the exam. The gap between "AZ-104 certified" and "Azure Administrator hired" lives almost entirely in those three.

What to read next

• Why your IT resume fails ATS — same genre of "thing no one tells you until it's too late".
• How PRISM measures the five dimensions — methodology, for the sceptics.
• Take a free 20-question mock — no card, HIRE/NO-HIRE verdict, this class of question on repeat.