Study guide

10.2 Identity, Storage, and Compute Integrated Cases

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

10.2 Identity, Storage, and Compute Integrated Cases

Key Takeaways Explain This Topic AI

Compute access to storage usually requires both a valid network path and the correct identity or key-based authorization model.

Managed identities plus data-plane roles are preferred when a workload needs least-privilege access to Azure resources.

Storage firewall and private endpoint settings can make correct credentials appear broken.

VM, App Service, and container troubleshooting should start with logs, identity assignment, role scope, and endpoint reachability.

Case questions often hinge on whether an administrator should change RBAC, app configuration, storage networking, or deployment artifacts.

Last updated: May 2026

Case 1: VM backup job writes reports to Blob Storage

A finance team runs a scheduled script on an Azure VM. The script writes daily reports to a blob container. Yesterday the storage account firewall was changed to selected networks only. Today the script fails. The VM has a system-assigned managed identity, and that identity has Storage Blob Data Contributor on the container.

Do not remove the role assignment. The identity and data-plane role are probably correct. The new variable is the storage network perimeter. Check whether the VM subnet is allowed through a virtual network rule, service endpoint, private endpoint, or trusted access pattern that fits the organization requirement. If the storage account should have no public access, use a private endpoint and private DNS. If public endpoint access is acceptable only from a known subnet, use storage firewall virtual network rules with the required service endpoint configuration.

Troubleshooting sequence:

From the VM, resolve the storage account name and note whether it returns public or private addresses.

Confirm storage account networking: public access, selected networks, private endpoint connections, and firewall exceptions.

Confirm the VM subnet route table and NSG allow the required outbound path.

Confirm the managed identity exists on the VM.

Confirm the role assignment is a data role at container, account, resource group, or subscription scope as required.

Review Storage logs or diagnostic settings if enabled.

  • CLI checks: az vm identity show -g rg-app -n vm-report-01
  • az role assignment list --assignee <principal-id> --scope <container-or-storage-scope> -o table
  • az storage account show -g rg-data -n examstorage104 --query networkRuleSet

az network private-endpoint-connection list -g rg-data -n examstorage104 --type Microsoft.Storage/storageAccounts -o table

The correct fix depends on the stated constraint. If the requirement says keep storage public network access disabled, create or fix the private endpoint and private DNS zone link. If the requirement says allow only the VM subnet, add the subnet to the storage firewall and ensure the service endpoint for Microsoft.Storage exists. If the requirement says least privilege, do not switch to account keys just because they are convenient.

Case 2: App Service reads blobs with managed identity

An App Service app was moved from connection-string storage keys to managed identity. The app starts successfully but receives 403 when reading blobs. The app's system-assigned identity is enabled. A developer assigned Reader on the storage account.

Reader is not enough for blob data. It allows viewing management properties, not reading blob content. Assign Storage Blob Data Reader or Storage Blob Data Contributor depending on whether the app only reads or also writes. Scope it as narrowly as the requirement allows. For a single container, container scope is better than subscription scope.

Portal path: Storage account > Access control (IAM) for management and data roles at account scope, or container-level access control where supported in the data service experience. App identity path: App Service > Identity . App logs path: App Service > Log stream and Diagnose and solve problems .

A complete remediation note would say: The app authenticates as its managed identity, but the identity has a management-plane Reader role instead of a blob data-plane role. Assign Storage Blob Data Reader at the target container scope and keep storage keys out of app settings.

Case 3: Container App pulls image and mounts Azure Files

A containerized report processor runs in Azure Container Apps. It pulls an image from Azure Container Registry and mounts an Azure Files share for temporary exchange files. The latest revision will not start. Logs show one error about unauthorized image pull and another about file share mount failure.

This is a chain failure. Treat each dependency separately. For ACR, confirm the Container App identity and AcrPull role assignment at the registry scope. Confirm the image reference includes the login server, repository, and tag. For Azure Files, confirm the storage account, share name, mount configuration, secret reference, and network reachability. If identity-based Azure Files access is required, confirm the supported identity model and SMB requirements. If the mount uses storage keys, confirm the secret value is current.

Do not fix an ACR pull failure by changing Azure Files permissions. Do not fix an Azure Files mount failure by assigning AcrPull. In an integrated case, several symptoms can be true at once. AZ-104 rewards isolating the failing operation.

Case 4: Bicep deployment creates VM and storage dependencies

A Bicep file deploys a VM, managed identity, storage account, private endpoint, and role assignment. Deployment fails with authorization errors when creating the role assignment. The operator has Contributor on the resource group.

Contributor can deploy many resources but cannot grant access. Role assignment operations require Microsoft.Authorization role assignment permissions, such as Owner or User Access Administrator at the relevant scope. The correct answer is not to make the VM identity Owner. The deployment identity needs permission to create the assignment, and the workload identity should receive only the data role it needs.

Interpret this as a deployment-control problem, not a runtime-workload problem. Activity log and deployment operations show the failing resource provider operation. Use az deployment group show and az deployment operation group list to inspect failures. az deployment group create -g rg-app -f main.bicep

  • az deployment operation group list -g rg-app -n <deployment-name> -o table
  • Remediation patterns to memorize

Symptom Likely root cause Correct remediation

VM script gets 403 to blobs Missing blob data role Assign Storage Blob Data Reader or Contributor at correct scope

VM script times out to storage Network path, firewall, DNS, or route Fix subnet allowance, private endpoint, DNS, NSG, or UDR

App Service has Reader but cannot read blobs Management role instead of data role Assign blob data role to managed identity

Container cannot pull ACR image Missing AcrPull, wrong tag, registry firewall Fix identity role, image reference, or network path

Bicep role assignment fails Deployment identity lacks grant permissions Use Owner/User Access Administrator for deployment identity

The exam wording often gives the intended constraint: least privilege, no secrets, no public access, no downtime, or repeatable deployment. Respect that constraint. A storage key may make a demo pass, but it is not the best answer when a managed identity and data role satisfy the requirement.