Azure Container Registry (ACR) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Container Registry with the Azure CLI.

Azure

az acr create --resource-group myResourceGroup --name myRegistry [1] --sku Basic

Drag options to blanks, or click blank then click option'

A--location westus

B--location centralus

C--location eastus

D--location northcentralus

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the --location parameter causes the command to fail.

Using an invalid or misspelled region name.

The --location parameter specifies the Azure region where the registry will be created. Here, westus is used as the location.

2fill in blank

medium

Complete the code to log in to your Azure Container Registry using the Azure CLI.

Azure

az acr [1] --name myRegistry

Drag options to blanks, or click blank then click option'

Alogin

Bdelete

Ccreate

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using push instead of login.

Trying to create the registry again instead of logging in.

The az acr login command logs you into the Azure Container Registry so you can push or pull container images.

3fill in blank

hard

Fix the error in the command to push a Docker image to your Azure Container Registry.

Azure

docker [1] myRegistry.azurecr.io/myapp:v1

Drag options to blanks, or click blank then click option'

Abuild

Bpull

Crun

Dpush

Attempts:

3 left

💡 Hint

Common Mistakes

Using pull instead of push.

Using run which executes containers, not uploads images.

The docker push command uploads your local image to the registry. Using push here is correct.

4fill in blank

hard

Fill both blanks to create a repository in Azure Container Registry and tag a local image correctly.

Azure

docker [1] myapp:latest myRegistry.azurecr.io/myapp:[2]

Drag options to blanks, or click blank then click option'

Atag

Bpush

Cv1

Dbuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using push instead of tag for labeling images.

Forgetting to specify a tag version.

The docker tag command tags a local image with the registry name and version. Here, v1 is the tag version.

5fill in blank

hard

Fill all three blanks to write a command that lists repositories in your Azure Container Registry.

Azure

az acr repository [1] --name myRegistry --output [2] --query [3]

Drag options to blanks, or click blank then click option'

Alist

Btable

C[].name

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using delete instead of list.

Not specifying output format or query correctly.

The command az acr repository list lists repositories. The output format table shows a readable table, and the query [].name extracts repository names.

Practice

1. What is the main purpose of Azure Container Registry (ACR)?

easy

A. To securely store and manage container images in Azure

B. To create virtual machines in Azure

C. To monitor network traffic in Azure

D. To manage Azure user permissions

Solution

1. Step 1: Understand what ACR is designed for

   Azure Container Registry is a service to store container images securely in Azure.

2. Step 2: Compare options with ACR's purpose

   Only To securely store and manage container images in Azure describes storing and managing container images, which matches ACR's main use.

3. Final Answer:

   To securely store and manage container images in Azure -> Option A

4. Quick Check:

   ACR purpose = store container images [OK]

Hint: ACR is for container images, not VMs or users [OK]

Common Mistakes:

• Confusing ACR with Azure VM services
• Thinking ACR manages user permissions
• Assuming ACR monitors network traffic

2. Which of the following is the correct Azure CLI command to create an Azure Container Registry named myRegistry in resource group myGroup with the Basic SKU?

easy

A. az acr new --group myGroup --registry myRegistry --tier Basic

B. az acr create --resource-group myGroup --registry-name myRegistry --sku Basic

C. az container registry create --group myGroup --name myRegistry --sku Basic

D. az acr create --resource-group myGroup --name myRegistry --sku Basic

Solution

1. Step 1: Recall the correct Azure CLI syntax for ACR creation

   The correct command uses az acr create with parameters --resource-group, --name, and --sku.

2. Step 2: Match options to correct syntax

   az acr create --resource-group myGroup --name myRegistry --sku Basic matches the exact syntax. Options A, C, and D use incorrect commands or parameter names.

3. Final Answer:

   az acr create --resource-group myGroup --name myRegistry --sku Basic -> Option D

4. Quick Check:

   Correct CLI syntax = az acr create --resource-group myGroup --name myRegistry --sku Basic [OK]

Hint: Use 'az acr create' with --resource-group and --name [OK]

Common Mistakes:

• Using wrong command like 'az acr new'
• Incorrect parameter names like --registry-name
• Confusing 'az container registry' with 'az acr'

3. Given this Azure CLI command sequence, what will be the output of the last command?

az acr create --resource-group myGroup --name myRegistry --sku Standard
az acr login --name myRegistry
az acr repository list --name myRegistry --output json

medium

A. A JSON list of repositories stored in myRegistry, initially empty

B. An error saying the registry does not exist

C. A list of running containers in myRegistry

D. A JSON list of all Azure resource groups

Solution

1. Step 1: Understand the commands run

   The first command creates the registry. The second logs into it. The third lists repositories in JSON format.

2. Step 2: Predict output of repository list on new registry

   Since the registry is new, it has no repositories yet, so the output is an empty JSON list.

3. Final Answer:

   A JSON list of repositories stored in myRegistry, initially empty -> Option A

4. Quick Check:

   New registry repo list = empty JSON list [OK]

Hint: New ACR has empty repo list JSON output [OK]

Common Mistakes:

• Expecting error when registry exists
• Confusing repositories with running containers
• Thinking it lists resource groups

4. You run this command but get an error:

az acr create --resource-group myGroup --name myRegistry --sku Basic --location eastus

What is the most likely cause of the error?

medium

A. The command syntax is incorrect

B. The SKU Basic is not supported in eastus

C. The resource group myGroup does not exist

D. The registry name myRegistry is already in use globally

Solution

1. Step 1: Check command syntax and parameters

   The syntax is correct and Basic SKU is supported in eastus.

2. Step 2: Identify common causes of creation errors

   If the resource group does not exist, creation fails with an error.

3. Final Answer:

   The resource group myGroup does not exist -> Option C

4. Quick Check:

   Missing resource group causes create error [OK]

Hint: Ensure resource group exists before creating ACR [OK]

Common Mistakes:

• Assuming SKU is unsupported without checking
• Ignoring resource group existence
• Thinking registry name conflict causes this error

5. You want to speed up your app deployment by sharing container images across multiple Azure regions. Which ACR feature should you enable to replicate your registry automatically to other regions?

hard

A. Configure Azure Traffic Manager for your registry

B. Enable geo-replication on your Azure Container Registry

C. Use Azure Blob Storage replication instead

D. Create multiple separate registries manually in each region

Solution

1. Step 1: Understand the need for multi-region image availability

   To share images across regions and speed deployment, the registry must replicate images automatically.

2. Step 2: Identify ACR feature for automatic replication

   Geo-replication is the ACR feature that replicates container images across regions automatically.

3. Step 3: Evaluate other options

   Creating registries manually is manual and error-prone. Blob Storage replication is unrelated to container images. Traffic Manager manages traffic, not image replication.

4. Final Answer:

   Enable geo-replication on your Azure Container Registry -> Option B

5. Quick Check:

   Multi-region image sharing = geo-replication [OK]

Hint: Use geo-replication to sync images across regions [OK]

Common Mistakes:

• Manually creating registries instead of replicating
• Confusing storage replication with ACR replication
• Using Traffic Manager for image replication