Study guide

6.1 Azure Container Registry and Image Workflow

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

6.1 Azure Container Registry and Image Workflow

Key Takeaways Explain This Topic AI

Azure Container Registry stores private container images and related artifacts close to Azure compute targets.

Administrators choose registry tiers based on storage, throughput, private endpoint, geo-replication, and network isolation requirements.

Image pull failures usually trace to identity, firewall, repository name, tag, or network path issues.

ACR Tasks can build, import, and automate image workflows without requiring a separate build agent.

AZ-104 scenarios often test the difference between pushing images to ACR and deploying compute that pulls from ACR.

Last updated: May 2026

What ACR does in an administrator workflow

Azure Container Registry, or ACR, is a managed private registry for container images and OCI artifacts. In AZ-104 terms, it is not the compute platform. It is the place where images are stored, secured, scanned by connected tooling, imported, replicated, and pulled by services that actually run containers. When a question says a development team has produced an image and the administrator must deploy it to Azure Container Instances, Azure Container Apps, App Service for Containers, or AKS, ACR is commonly the registry choice.

A basic image workflow has four parts. First, build the image from a Dockerfile or import an existing image. Second, push or import the image into a registry repository with a tag. Third, grant a runtime identity permission to pull the image. Fourth, configure the compute resource with the registry server name, image name, tag, and credentials or managed identity.

The login server format matters: <registry-name>.azurecr.io . Image references are usually written as <registry-name>.azurecr.io/<repository>:<tag> . A common exam trap is giving only repository:tag to a service that expects the full registry path, or creating the container instance before the identity has pull rights.

Tier and capability choices

Requirement Likely ACR choice Why it matters

Low-cost private image storage for simple labs Basic Lowest-cost tier, enough for simple development and small workloads.

More storage and throughput for production Standard Better default for general production registries when advanced network features are not required.

Private endpoint, firewall rules, content trust features, or geo-replication Premium Premium is the tier to recognize when isolation, private connectivity, and regional replication are requirements.

Run a build from source without a dedicated CI runner ACR Tasks A managed build can produce and push the image inside Azure.

Copy images from Docker Hub or another registry without local pull and push az acr import Imports server-side and avoids moving the image through the administrator workstation.

Portal path: Azure portal > Container registries > Create for a registry, then use Repositories to inspect pushed images and tags. Use Access keys only when the scenario permits admin credentials. For production, prefer Microsoft Entra identities and role assignments.

  • CLI examples: az acr create \
  • -resource-group rg-compute \
  • -name examacr104 \
  • -sku Premium \
  • -location eastus

az acr login --name examacr104

  • docker tag web:v1 examacr104.azurecr.io/apps/web:v1
  • docker push examacr104.azurecr.io/apps/web:v1
  • az acr import \
  • -name examacr104 \
  • -source mcr.microsoft.com/azuredocs/aci-helloworld:latest \
  • -image samples/aci-helloworld:latest
  • Authentication and authorization

ACR uses Azure RBAC for registry operations. For a runtime service that only needs to pull images, assign AcrPull at the registry scope. For build or push workflows, AcrPush is more appropriate. The built-in admin account is easy for demos but is usually the wrong answer for least privilege because it creates registry-wide username and password credentials.

Managed identity is the clean exam answer when the compute service supports it. For example, an App Service app running a custom container can use a managed identity to pull from ACR. Container Apps also supports managed identity for registry authentication. If the compute platform or scenario does not support identity-based pull, credentials may be required, but choose the least privileged option available.

Troubleshooting pull failures follows a predictable tree:

Confirm the image reference includes the login server, repository, and tag.

Confirm the image tag exists in Repositories or with az acr repository show-tags .

Confirm the runtime identity has AcrPull on the registry.

Confirm the registry firewall allows the caller or that private connectivity is configured.

Confirm DNS and routing work if a private endpoint is used.

Check whether the service is pulling from the expected region or replica.

  • Useful commands: az acr repository list --name examacr104 --output table
  • az acr repository show-tags --name examacr104 --repository apps/web --output table
  • az role assignment create \
  • -assignee <principal-id> \
  • -role AcrPull \
  • -scope $(az acr show -g rg-compute -n examacr104 --query id -o tsv)
  • Network isolation and private access

Premium ACR supports private endpoints and firewall restrictions. This is where AZ-104 blends compute, networking, and identity. If a registry denies public network access and a container platform cannot reach the private endpoint, authentication is not the only problem. The pull request must also resolve the registry name to the private endpoint address and route over the private network.

For private endpoint scenarios, validate the private DNS zone link. The registry login server still looks like <name>.azurecr.io , but the name should resolve privately from the workload network. If the question mentions a VNet-integrated compute service, a private endpoint, and a failed pull after public access is disabled, suspect DNS or subnet integration before changing image tags.

ACR Tasks and image maintenance

ACR Tasks can build images with az acr build , run quick tasks, or automate builds from source changes. For AZ-104, know the use case more than every task trigger option. If the requirement is to build a container image in Azure and place it in ACR without installing Docker locally, az acr build is a strong fit. az acr build \

  • -registry examacr104 \
  • -image apps/web:v2 \

.

Administrators also need to manage repository hygiene. Untagged images and old tags consume storage. ACR retention policies and purge-style automation are common operational controls, especially when frequent builds produce many tags. The exam may describe rising registry costs or failed pushes due to quota pressure; deleting unused manifests or increasing the tier can both be relevant depending on the requirement.

Exam traps

Do not confuse ACR with Container Instances or Container Apps. ACR stores images; it does not run web apps by itself. Do not use storage account SAS tokens for registry access. ACR authorization is controlled through registry credentials, Microsoft Entra identity, and Azure RBAC roles such as AcrPull and AcrPush .

Do not choose the admin account when a managed identity and AcrPull role assignment meet the requirement. Do not forget that private endpoint and firewall decisions can break image pulls even when the password or role assignment is correct. Do not assume geo-replication exists in every tier; Premium is the tier to associate with geo-replicated registries.

A final scenario pattern: a container app fails to start after a new image is pushed. If the app still points to v1 , pushing v2 does nothing. You must update the compute resource to reference the new tag or use a deployment process that updates the revision, slot, or container setting.