ACR image building and pushing in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when you push a Docker image to Azure Container Registry (ACR)?

You have built a Docker image locally and pushed it to your Azure Container Registry. What is the expected behavior after the push completes successfully?

A The image is converted to a virtual machine image in Azure.

B The image is automatically deployed to all Azure Kubernetes Service clusters.

C The image is deleted from the local machine after pushing.

D The image is stored in ACR and can be pulled by authorized clients.

💡 Hint

Think about what a container registry's role is in storing images.

Azure Container Registry stores container images securely. After pushing, the image is available for authorized clients to pull and deploy. It does not automatically deploy or delete local images.

❓ Configuration

intermediate

Which Azure CLI command builds and pushes an image to ACR in one step?

You want to build a Docker image from your local Dockerfile and push it directly to your Azure Container Registry using Azure CLI. Which command achieves this?

A az acr build --registry MyRegistry --image myapp:v1 .

B az acr push --registry MyRegistry --image myapp:v1 .

C az acr create --name MyRegistry --image myapp:v1 .

D az acr deploy --registry MyRegistry --image myapp:v1 .

💡 Hint

Look for the command that builds and pushes in one step.

The az acr build command builds the image from the Dockerfile and pushes it to the specified registry. Other commands do not perform both actions together.

❓ security

advanced

What is the best practice to securely push images to ACR from a CI/CD pipeline?

You want to push Docker images to Azure Container Registry from your CI/CD pipeline securely without exposing credentials. Which approach is best?

A Use a service principal with minimum required permissions and store its credentials securely in the pipeline.

B Use your personal Azure account credentials directly in the pipeline scripts.

C Allow anonymous push access to the registry during the pipeline run.

D Embed the registry admin username and password in the Dockerfile.

💡 Hint

Consider least privilege and secure credential storage.

Using a service principal with least privilege and securely storing its credentials in the pipeline is best practice. Personal credentials or admin credentials in code are insecure. Anonymous push is not supported.

❓ Architecture

advanced

How to optimize image build and push speed for large images in ACR?

You have large container images that take a long time to build and push to Azure Container Registry. Which architectural choice improves build and push speed?

A Push images without tagging to reduce metadata overhead.

B Use Azure Container Registry Tasks with incremental builds and caching enabled.

C Use multiple registries in different regions and push all images to each registry simultaneously.

D Build images locally on a slow machine and push over a slow network.

💡 Hint

Think about build caching and automation features in ACR.

ACR Tasks support incremental builds and caching layers, which speeds up build and push times. Building locally on slow machines or pushing without tags does not help. Pushing to multiple registries simultaneously increases complexity and network load.

✅ Best Practice

expert

What is the recommended way to manage image tags in ACR for continuous deployment?

You want to implement a tagging strategy in Azure Container Registry that supports continuous deployment and easy rollback. Which approach is best?

A Overwrite the 'latest' tag with every build and delete all previous tags.

B Use only commit SHA hashes as tags without any human-readable tags.

C Use semantic version tags (e.g., v1.0.0) for releases and a 'latest' tag for the current stable image.

D Tag images with the build timestamp only and never use semantic versions.

💡 Hint

Consider clarity, rollback, and deployment automation.

Using semantic version tags allows clear identification of releases and rollback points. The 'latest' tag points to the current stable image. Overwriting or deleting tags removes rollback options. Using only SHA hashes or timestamps reduces clarity.