Study guide
4.7 Storage Case Lab
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.7 Storage Case Lab
Key Takeaways Explain This Topic AI
Case questions require ordering storage decisions across account design, network access, identity, data protection, and operations.
Least privilege in storage usually means combining RBAC, SAS scoping, firewall rules, private endpoints, and short-lived secrets.
Recovery requirements must be translated into specific features such as versioning, soft delete, snapshots, backup, redundancy, or account failover.
Troubleshooting storage failures starts by classifying the symptom as DNS, network, authentication, authorization, feature compatibility, or data state.
CLI and portal fluency matters because AZ-104 questions often describe implementation tasks rather than definitions.
Last updated: May 2026
Case lab: Contoso storage modernization
Contoso is moving several storage workloads to Azure. The application team needs blob storage for customer documents. The finance team needs a secure file share for monthly reports. A vendor needs temporary upload access for migration files. Security requires private access where practical, no anonymous blob access, customer-managed keys for production data, and recovery from accidental deletion or overwrite. Operations wants repeatable CLI commands and a troubleshooting checklist.
Start with workload separation. Put production customer documents in a dedicated StorageV2 account because the data has specific encryption, network, lifecycle, and recovery requirements. Put finance Azure Files in a storage account designed for file shares, with premium if performance requires it or standard if normal departmental documents are enough. Keep migration landing data separate if vendor access is temporary and riskier. Separate accounts make firewall rules, key rotation, private endpoints, cost reporting, and deletion policies easier to reason about.
Workload Account or service choice Access model Protection model
Customer documents StorageV2 blob account RBAC and private endpoint GZRS if regional recovery needed, versioning, soft delete, CMK
- Finance reports Azure Files share Identity-based SMB Snapshots or Azure Backup, NTFS ACLs, private endpoint
- Vendor uploads Landing container Short-lived SAS Soft delete, limited lifecycle retention
- Archive exports Blob container RBAC for admins Lifecycle to cool, cold, or archive
Create the production blob account with secure defaults. Disable public blob access, require TLS 1.2 or later, choose redundancy based on the recovery requirement, and configure customer-managed keys through Key Vault if required. If a regional outage must allow reads from the paired region, use RA-GZRS or RA-GRS depending on zone requirements. If the requirement only says survive a zone failure in the primary region, ZRS may be enough and cheaper than geo-redundancy.
Example CLI skeleton: az group create --name rg-contoso-storage --location eastus
- az storage account create \
- -name stcontosodocs01 \
- -resource-group rg-contoso-storage \
- -location eastus \
- -kind StorageV2 \
- -sku Standard_GZRS \
- -min-tls-version TLS1_2 \
- -allow-blob-public-access false \
- -default-action Deny
- az storage container create \
- -account-name stcontosodocs01 \
- -name customer-docs \
- -auth-mode login
Then add data protection. Enable blob soft delete for accidental deletion. Enable container soft delete if container deletion is a realistic risk. Enable versioning for overwrite recovery. Add lifecycle rules to move older documents to cooler tiers when access drops, but do not delete data before the retention requirement. If compliance says data cannot be modified or deleted for a fixed period, add immutable storage policy; soft delete alone does not satisfy that requirement.
Network design comes next. For application subnets in Azure, choose private endpoints if the security requirement says private IP access or public network access must be disabled. Create private endpoints for the blob subresource, and for dfs as well if Data Lake Storage Gen2 style access is used by tools. Link the proper private DNS zones to VNets. For Azure Files, create a private endpoint for the file subresource, not blob. If using service endpoints instead, remember the endpoint remains public and the storage firewall authorizes the subnet.
Access-control choice table:
Requirement Do this Avoid this
App runs in Azure and should have ongoing blob access Managed identity plus Storage Blob Data Contributor at container scope Account key in app settings
Vendor needs upload for two days Short-lived SAS with create/write, HTTPS, optional IP range Subscription Contributor or account key
Finance users need mapped drive Identity-based Azure Files, share RBAC, NTFS ACLs Shared account key distributed to users
Break-glass storage administration Privileged role through just-in-time process Permanent broad Owner for many users
Revoke many vendor SAS tokens early Service SAS tied to stored access policy where supported Long unmanaged SAS tokens
Portal implementation path: create storage account from Storage accounts > Create. Configure Networking to selected networks or disabled public network access with private endpoint connections. Configure Encryption for customer-managed keys. Configure Data protection for soft delete and versioning. Configure Lifecycle management rules under Data management. Assign data-plane RBAC through Access Control (IAM) at account, container, or share scope. For Azure Files identity, configure the directory service integration and then manage NTFS ACLs from a mounted client.
Troubleshooting case 1: the application receives 403 from a VM after the firewall is enabled. Check whether the VM subnet is allowed through service endpoint rules or whether DNS resolves to a private endpoint. Confirm the managed identity still has the right data-plane role. A 403 can mean network denial or authorization denial, so inspect the error details and logs instead of assuming RBAC.
Troubleshooting case 2: the vendor upload SAS fails immediately. Check token start time and clock skew, expiry, permissions, signed resource, HTTPS requirement, IP restriction, and whether the storage firewall allows the vendor source. If the account disallows shared key and the SAS is key-signed, regenerate the plan with an allowed authorization method or use a user delegation SAS for Blob Storage where appropriate.
Troubleshooting case 3: finance users can mount the share but cannot edit a folder. That points past DNS and port 445 because the mount worked. Check Storage File Data SMB Share Contributor or Elevated Contributor assignment, then check NTFS ACLs on the folder. If key-based mount works but identity mount fails, investigate identity integration rather than share quota.
Troubleshooting case 4: lifecycle policy did not archive old blobs. Confirm the rule is enabled, prefix matches, blob type is block blob, age condition is met, and the action applies to base blobs rather than only versions. If versioning is enabled, old versions may remain and continue billing even when the current blob moves tier.
A strong exam answer usually names both the feature and the reason. Do not simply say use private endpoint; say use a private endpoint for the correct storage subresource and configure private DNS. Do not simply say use SAS; say short-lived SAS with only required permissions, HTTPS-only, and stored access policy if revocation is needed. Do not simply say enable backup; match the recovery problem to soft delete, versioning, share snapshots, Azure Backup, or redundancy. That level of precision is what separates AZ-104 implementation knowledge from entry-level cloud vocabulary.