Study guide
5.3 VM Disks, Sizes, Encryption, and Host Settings
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
5.3 VM Disks, Sizes, Encryption, and Host Settings
Key Takeaways Explain This Topic AI
VM size determines CPU, memory, network throughput, maximum data disks, temporary storage behavior, and supported features.
Managed disks are independent Azure resources with performance, redundancy, bursting, encryption, snapshot, and resize characteristics.
Encryption at host protects data before it leaves the VM host, while disk encryption sets and platform-managed keys or customer-managed keys address different encryption requirements.
Host settings such as dedicated hosts, proximity placement groups, trusted launch, and accelerated networking should be selected only when workload or compliance requirements justify them.
Last updated: May 2026
VM Sizes and Families
A VM size is more than a CPU and memory number. It controls the number of vCPUs, memory, temporary storage, maximum number of data disks, maximum IOPS, maximum throughput, network bandwidth, accelerated networking support, premium storage support, GPU availability, and price. Some sizes are general purpose, while others target compute, memory, storage, GPU, or high performance computing workloads.
- Family pattern Typical use Exam signal
- B series Burstable small workloads Low steady CPU with occasional bursts
- D series General purpose Balanced app servers and small databases
- E series Memory optimized In-memory workloads and database cache
- F series Compute optimized CPU-heavy processing
- L series Storage optimized High disk throughput and low latency storage
- N series GPU Graphics, AI, visualization
- M series Very large memory Large databases and SAP-like workloads
Resizing is possible, but not every size is available in every region, zone, cluster, or host group. If the target size is not available in the current hardware cluster, Azure may require deallocation before resizing. Availability set deployments can also constrain resizing because all VMs in the set must be able to run on compatible hardware.
- Useful commands: az vm list-vm-resize-options -g rg-prod-compute -n vm-db-01 --output table
- az vm list-skus --location eastus --resource-type virtualMachines --output table
- az vm resize -g rg-prod-compute -n vm-db-01 --size Standard_E4ds_v5
If resizing fails, check quota for the target family, regional availability, zone availability, policy restrictions, and whether the VM must be deallocated. Quota is per subscription, per region, and often per VM family.
Managed Disks
Azure managed disks remove the need to manage storage accounts for VM disks. You choose a disk type and size, and Azure manages placement and durability. Common disk types include Standard HDD, Standard SSD, Premium SSD, Premium SSD v2, and Ultra Disk. Availability depends on region and VM size.
- Disk type Strength Tradeoff
- Standard HDD Lowest cost for infrequent access Higher latency and lower IOPS
- Standard SSD Cost-effective production for light workloads Lower performance than Premium SSD
- Premium SSD Broad production default Performance tied to provisioned disk size or tier
- Premium SSD v2 Flexible performance tuning Feature and regional constraints apply
- Ultra Disk Highest IOPS and throughput Requires supported VM sizes and configuration
The OS disk stores the operating system. Data disks store application data. The temporary disk, when present, is local to the host and should not store durable data. It may be erased during maintenance, redeploy, or host movement. Exam questions often test this: never place critical persistent data on the temporary disk.
You can resize managed disks, but shrinking is not generally supported. Increasing an OS or data disk usually requires expanding the partition inside the guest OS after Azure reports the larger disk. Some disk performance changes are online, while others require downtime depending on disk type and VM state. az disk update -g rg-prod-compute -n vm-db-01-data-01 --size-gb 512
az vm disk attach -g rg-prod-compute --vm-name vm-db-01 --name vm-db-01-data-02 --new --size-gb 1024 --sku Premium_LRS
- az vm disk detach -g rg-prod-compute --vm-name vm-db-01 --name vm-db-01-data-02
- Snapshots, Images, and Disk Recovery
A snapshot is a point-in-time copy of a managed disk. Snapshots are useful before risky patching, application upgrades, or disk manipulation. They are not a replacement for a full backup policy because they do not provide the same scheduling, retention, application consistency options, vault management, or cross-protection workflow.
Images and Azure Compute Gallery help standardize VM builds. A custom image can include baseline OS configuration, agents, and hardening. Azure Compute Gallery supports sharing image versions across subscriptions and regions. For AZ-104, know that images help repeat deployment, while backup helps restore protected instances.
Encryption Options
Azure Storage Service Encryption protects managed disks at rest by default. Platform-managed keys are simplest. Customer-managed keys use a disk encryption set backed by Azure Key Vault or managed HSM where supported. Azure Disk Encryption uses BitLocker for Windows or DM-Crypt for Linux inside the guest; it is older and more intrusive. Encryption at host encrypts VM data on the host before it flows to storage, covering temporary disks and caches for supported VM sizes and regions.
- Requirement Likely feature
- Default disk-at-rest encryption with minimal admin work Platform-managed keys
- Organization controls key lifecycle Customer-managed keys with disk encryption set
- Encrypt caches and temporary disks at the host layer Encryption at host
- Guest-level volume encryption requirement Azure Disk Encryption, if supported and appropriate
Bicep example for a VM setting encryption at host: resource vm 'Microsoft.Compute/virtualMachines@2024-07-01' = {
- name: vmName
- location: location
- properties: {
- securityProfile: {
- encryptionAtHost: true
- }
- hardwareProfile: {
- vmSize: 'Standard_D2s_v5'
- }
- storageProfile: {
- osDisk: {
- createOption: 'FromImage'
- managedDisk: {
- storageAccountType: 'Premium_LRS'
- }
- }
- imageReference: imageReference
- }
- osProfile: osProfile
- networkProfile: networkProfile
- }
- }
If a deployment fails after enabling encryption at host, check whether the subscription has the feature available, the VM size supports it, the region supports it, and policy does not conflict. If customer-managed keys fail, check Key Vault permissions, purge protection and soft delete requirements, managed identity access, disk encryption set identity, and network restrictions on the vault.
Host and Security Settings
Trusted launch provides security features such as secure boot and virtual TPM for supported generation 2 images and sizes. Confidential VMs protect data in use for supported scenarios. Dedicated hosts provide physical server isolation for compliance or licensing. Proximity placement groups place Azure compute resources physically close to reduce latency, but they can constrain availability and SKU choices. Accelerated networking improves network performance by bypassing the host datapath for supported sizes and operating systems.
Design table:
- Setting Use when Watch for
- Trusted launch Need secure boot and vTPM baseline Image and size compatibility
- Dedicated host Physical isolation or licensing Capacity, cost, and placement planning
- Proximity placement group Low latency between VMs Reduced placement flexibility
- Accelerated networking High network throughput and low latency OS, size, and NIC support
- Capacity reservation Need capacity assurance Region, zone, and SKU matching
- Troubleshooting Scenario
A database VM has high disk latency after migration. Start with metrics: disk IOPS consumed percentage, disk bandwidth consumed percentage, VM cached and uncached limits, queue depth, and guest OS counters. If the disk is Premium SSD but the VM size has a lower throughput cap than the disks, resizing the VM may help more than changing disk SKU. If the data disk uses host caching incorrectly, adjust caching based on workload guidance. Read-heavy workloads may benefit from read-only caching, but write-heavy database logs often should not use read-write caching without vendor support.
AZ-104 questions often combine cost and performance. The cheapest disk is not always acceptable, and the most expensive disk is not always useful if the VM size throttles it. Match VM family, VM size limits, disk type, disk size, caching, and redundancy to the workload.