4. Deploying & Managing Azure Compute Resources
Welcome to Phase 4, where we dive into the core of Azure administration: deploying and managing compute resources. Building upon your understanding of Azure's foundational concepts, identity, governance, and storage from previous phases, this section focuses on the practical application of provisioning and maintaining virtual machines, containers, and serverless compute.
This section is crucial for the AZ-104 exam, which demands not just recall, but the ability to configure, manage, and troubleshoot various Azure compute solutions. We'll explore architectural patterns and best practices that ensure your applications are deployed securely, scalably, and efficiently, and that they remain highly available. The focus here is on comprehension and practical application, enabling you to implement robust compute solutions.
Why care: compute is where availability and cost decisions become visible. A VM deployed on its own, outside any availability set or zone, has no protection when its hardware or datacenter fails; an oversized VM quietly doubles the bill; and a VM built by hand rarely matches the one built before it. Think of the compute services as a scale of how much you manage yourself:
| Service | What you manage | Choose it when |
|---|---|---|
| Virtual machines | The operating system, patches, and everything above them | You need full control of the OS |
| App Service | Your code and app settings | You host web apps and APIs |
| Container Instances | A single container group, with no orchestration | A simple container must run quickly, on demand |
| Container Apps | Containers plus their scale rules | Containerized apps must scale with demand, including to zero |
⚠️ Exam Trap: Availability sets and availability zones are not two names for one feature. An availability set spreads VMs across fault and update domains inside a single datacenter; availability zones place VMs in physically separate datacenters within a region. Only zones survive the loss of a whole datacenter, and a VM can't use both.