Study guide
4.1 Storage Account Design, Redundancy, and Encryption
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
4.1 Storage Account Design, Redundancy, and Encryption
Key Takeaways Explain This Topic AI
Choose storage account kind, performance, replication, and access tier from workload requirements before creating dependent services.
Replication choices protect against different failure scopes, so LRS, ZRS, GRS, GZRS, RA-GRS, and RA-GZRS are not interchangeable.
Azure Storage encrypts data at rest by default, and administrators must know when Microsoft-managed keys, customer-managed keys, infrastructure encryption, and encryption scopes apply.
Some settings, such as hierarchical namespace and redundancy conversions, affect compatibility, migration planning, and recovery behavior.
Exam scenarios often combine cost, region availability, failover, read access, compliance, and performance constraints.
Last updated: May 2026
Design decisions that matter in production
A storage account is a management boundary for blobs, files, queues, and tables, but it is also a security, networking, redundancy, billing, and encryption boundary. When an exam question asks where to put data, do not jump straight to a blob container or file share. First decide whether a separate storage account is needed for isolation, replication, network rules, private endpoints, customer-managed keys, lifecycle policy, diagnostics, or ownership.
The most common general-purpose account for new workloads is StorageV2. It supports Blob Storage, Azure Files, queues, tables, standard performance, access tiers, lifecycle management, and most current data protection features. Premium accounts are selected for specific performance profiles, such as premium block blobs, premium file shares, or premium page blobs. A premium file share account is not just a faster version of a standard account; it has different performance provisioning behavior and is often used when low latency SMB or NFS file workloads need predictable throughput.
- Requirement Likely storage design choice Why it matters
- General blob and file workload General-purpose v2, standard Broad feature support and normal cost profile
- Low-latency file workload Premium file shares Provisioned performance and SSD-backed shares
Analytics namespace with directories and ACLs StorageV2 with hierarchical namespace Enables Azure Data Lake Storage Gen2 behavior
Cheapest locally durable blob storage Standard account with LRS Three local copies in one region, no cross-region protection
Read from secondary region during outage RA-GRS or RA-GZRS Secondary endpoint can be used for read operations
Zone failure tolerance in primary region ZRS or GZRS Data is synchronously replicated across availability zones
Redundancy is a scenario skill. Locally redundant storage, or LRS, keeps three copies in one data center or storage scale unit within a region. It is usually the lowest-cost option, but it does not protect against a zonal or regional outage. Zone-redundant storage, or ZRS, synchronously copies data across availability zones in a supported region. It is a strong fit when the application must survive a zone failure without cross-region replication.
Geo-redundant storage, or GRS, adds asynchronous replication to a paired secondary region. Because replication is asynchronous, a regional disaster can include some data loss within the recovery point objective. Geo-zone-redundant storage, or GZRS, combines ZRS in the primary region with asynchronous replication to the secondary region. Read-access variants, RA-GRS and RA-GZRS, expose a secondary read endpoint. That does not mean writes automatically move to the secondary region; account failover is a separate operation, and failover can be disruptive.
- Option Primary copies Secondary region Read secondary Typical exam clue
- LRS Three local copies No No Lowest cost, local durability only
- ZRS Three zones No No Survive datacenter or zone failure
- GRS Local copies plus async secondary Yes No Regional disaster protection, no normal secondary reads
- RA-GRS Local copies plus async secondary Yes Yes App must read from paired region during outage
- GZRS Zone copies plus async secondary Yes No Zone and regional protection
- RA-GZRS Zone copies plus async secondary Yes Yes Highest standard redundancy with secondary reads
Encryption at rest is automatic for Azure Storage. By default, Microsoft-managed keys protect the data, and this is enough for many workloads. Customer-managed keys use Azure Key Vault or managed HSM when the organization requires key ownership, rotation control, or separation of duties. Infrastructure encryption adds a second encryption layer for supported account types. Encryption scopes allow different containers or blobs to use distinct encryption settings, which is useful when tenants, departments, or compliance groups share an account but need key separation.
Portal path example: Storage accounts > Create > Basics for subscription, resource group, name, region, performance, and redundancy. Then review Advanced for hierarchical namespace, SFTP, NFS, TLS minimum version, shared key access, and blob public access. After creation, use Settings > Configuration for account-level security defaults, Data management > Redundancy for replication details, and Security + networking > Encryption for key settings.
- CLI example: az storage account create \
- -name staz104prod01 \
- -resource-group rg-storage-prod \
- -location eastus \
- -sku Standard_GZRS \
- -kind StorageV2 \
- -min-tls-version TLS1_2 \
- -allow-blob-public-access false
- az storage account show \
- -name staz104prod01 \
- -resource-group rg-storage-prod \
- -query '{sku:sku.name,kind:kind,tls:minimumTlsVersion,publicBlob:allowBlobPublicAccess}'
Troubleshooting often starts with the error scope. If a client cannot create a container, check identity and account-level permissions before network rules. If a client can reach the account but receives an encryption or key error, inspect Key Vault access, key state, purge protection, managed identity assignment, and whether the storage account can reach the key. If a workload fails after enabling hierarchical namespace, confirm that the application and SDK support Data Lake Storage Gen2 semantics. Some older tools assume flat blob namespace behavior.
A practical design sequence is: identify service type, performance tier, region, redundancy, networking, identity, encryption, data protection, and monitoring. This order prevents common mistakes. For example, choosing LRS for a compliance workload that requires regional recovery is not fixed by blob soft delete. Enabling customer-managed keys without a Key Vault recovery plan can create an availability dependency. Putting unrelated production and test workloads in one account can make firewall rules and key rotation harder than necessary.
Case scenario: a finance team stores quarterly exports in blobs. The data must stay available during a single zone failure, must not be publicly accessible, must be encrypted with organization-managed keys, and must be recoverable if a user deletes a file. The base design is a StorageV2 account with ZRS or GZRS depending on regional disaster requirements, public blob access disabled, customer-managed keys in Key Vault, blob soft delete, versioning, and role-based access for administrators. If the question adds read access from a paired region during a regional outage, move from GRS or GZRS to RA-GRS or RA-GZRS.