Azure V: Compute, App Hosting & the AZ-104 exam
Running workloads on Azure the way an administrator must for AZ-104 - ARM templates and Bicep, virtual machines, availability zones and scale sets with autoscale, ACR, Container Instances and Container Apps, App Service plans, custom domains, TLS and deployment slots, VNet peering, public IPs, ASGs, Bastion, Azure DNS and load balancers, Azure Monitor metrics, diagnostic settings, alerts and Network Watcher - with four real incidents and timed AZ-104 mock exams.
In plain words
Azure I to III taught you to drive the car: sign in, find things, read the logs, keep the network for a cluster working. This chapter is the mechanic's course. You learn how the parts are ordered (templates), the engines themselves (virtual machines and scale sets), the ready-made vehicles you can rent instead (App Service, Container Apps), the roads between garages (peering, load balancers, DNS) and the dashboard lights that must ring a bell when something breaks (alerts).
At the end you sit the driving test: the AZ-104 exam, with timed mock rounds inside the course.
Why it matters on call
AZ-104 is the Azure administrator certification, and it asks about exactly the parts a platform engineer owns day to day: a template that deletes more than it should, a VM size that is not available, a slot swap that took the wrong connection string, a peering that does not reach the third network, an alert that fired and paged nobody.
Each of those is a lab or an incident here, on a simulated subscription that answers like the real Azure CLI. The exam questions then feel like things you have already fixed, not trivia.
Lessons
- 33.1ARM templates: read, change, preview, deploy, export
- 33.4Bicep: the same deployments, in a language people can read
- 33.7Virtual machines: images, sizes, quotas and the first boot
- 33.9VM disks, encryption at host, and moving a VM
- 33.11Availability sets, zones, scale sets and autoscale
- 33.14Containers without a cluster: ACR, Container Instances, Container Apps
- 33.17App Service: plans, scaling, custom domains, TLS, backups and networking
- 33.21Deployment slots: release by swapping, roll back by swapping again
- 33.24VNet peering, public IPs and troubleshooting connectivity
- 33.27Secure access: NSGs with ASGs, effective rules, Bastion, service and private endpoints
- 33.32Azure DNS and the Standard load balancer
- 33.35Azure Monitor: metrics, diagnostic settings, log queries and Insights
- 33.38Alerts that page: alert rules, action groups and alert processing rules
- 33.41Network Watcher and Connection monitor
- 33.44The AZ-104 exam: format, domains, a study plan and the mocks
Open this chapter in the terminal Free, in your browser - a real Ubuntu terminal to try it in, with missions that check your work.
Questions people ask
Do I need Azure I-III first?
Yes, ideally. This chapter assumes you can sign in with the CLI, read a resource ID, use --query and -o table, and know what a VNet, a subnet and an NSG are - Azure I-III teach that. Here those basics are used, not explained again; the new parts are templates, compute, App Service, the network edges and Azure Monitor.
Is this enough to pass AZ-104?
Together with Azure I-III and the governance, storage and backup material, it covers every skill in the study guide. The chapter ends with the exam lesson and three timed mock rounds from the AZ-104 bank; Progress › Certifications has more. Score 80% or more on fresh mocks before you book, and read the exam lesson's strategy section.
What is simulated here?
The subscription is (simulator): resources are created instantly or with short delays, VMs are lab hosts, metrics and logs come from deterministic patterns, and mail to the action group lands in the lab's mailbox. The commands, their options, output formats and error messages follow the real Azure CLI and Microsoft Learn, so what you type works the same against a real subscription.
Why so many incidents about things that "worked"?
Because that is what Azure incidents usually look like: nothing is broken in the platform, a setting does exactly what it says. A slot setting that was not sticky, an autoscale profile with a minimum of zero, a suppression rule left on after maintenance. The skill is finding which setting, quickly, and these labs train that.
How long does the chapter take?
About 14 hours: fifteen lessons, around twenty labs, four incidents, four replayable drills, a debrief and the three mock rounds. The lessons are split into parts of 5-10 minutes, so you can read one part on the phone and do its lab at the computer later.