Azure gives you several ways to manage the same cloud, and the AZ-900 loves to ask which one you would reach for. The trick is to see them in three tiers — shown in the diagram above: a graphical interface you click through, scripted command-line tools you automate with, and declarative templates you deploy repeatably. Whichever you choose, your request ends up going through the same place: Azure Resource Manager. Learn the three tiers and their tools, and this whole cluster of questions becomes free points.
The GUI: Azure portal (and the mobile app)
The Azure portal is the browser-based graphical interface — point, click, fill in a form. It is the friendliest place to explore the service catalog, learn your way around, and knock out a one-off change or build a single resource. It shines when you are experimenting or doing something once; it is a poor fit when you need to repeat the same steps reliably.
The Azure mobile app is the portal’s companion for your phone: check resource status, view alerts, and run a few quick actions while you are away from your desk. For the exam, know it by name and purpose — mobile monitoring on the go.
Scripted: CLI, PowerShell, and Cloud Shell
When a task is repetitive, you script it. Azure gives you two command-line tools that do the same jobs with different syntax:
- Azure CLI — cross-platform commands that all start with
az (for example az vm create). Comfortable for anyone from a Bash or Linux background, and identical on Windows, macOS, and Linux.
- Azure PowerShell — cmdlets in a Verb-Noun form (for example
New-AzVM, Get-AzResourceGroup). A natural fit for teams already automating with PowerShell.
Both are scriptable and largely interchangeable — pick by the syntax your team already knows.
Azure Cloud Shell is the third piece: a shell that runs straight from the browser inside the portal, with nothing to install and you already signed in. It offers both a Bash experience (Azure CLI) and a PowerShell experience, so you can run commands from any machine — even a borrowed laptop during an incident.
Declarative: ARM and Bicep templates
For environments you must stand up the same way, again and again, you stop typing steps and instead declare the result in a file. This is infrastructure as code. On Azure that means ARM templates or Bicep — Bicep being the cleaner, friendlier language that compiles down to the same deployment. You keep the file in source control, and every deployment produces an identical environment. The difference from scripting is subtle but exam-worthy: a script says how to build it step by step; a declarative template says what the end state should be and lets Azure work out the rest.
Which for which job
That is the whole mental model, and the diagram sums it up: explore in the GUI, automate with scripts, standardize with templates. A quick look or a single change is the portal; a repetitive task is CLI or PowerShell; an environment you need to reproduce reliably is ARM/Bicep.
The real exam mixes multiple-choice, true/false, and drag-and-drop formats; the seven questions above are standard multiple-choice, and every explanation carries a “why not the others” so the wrong options teach you as much as the right one.
Updated for AZ-900 (July 2026). The sample questions above are our own work
in the style of the exam — not real exam items. The exam itself is set and marked
by the certification body.