Azure Container Registry (ACR) stores container images with tags. What happens when you push a new image with the same tag as an existing image?
Think about how tags work in container registries as pointers to images.
In ACR, tags are pointers to images. Pushing an image with an existing tag replaces the pointer to the new image, effectively overwriting the old image under that tag.
You want to automate building container images and push them to Azure Container Registry securely without managing build servers. Which Azure service should you use?
Look for a service that integrates directly with ACR for building images.
ACR Tasks is a service that automates building, testing, and patching container images inside Azure Container Registry without needing separate build infrastructure.
After enabling Azure Defender for Container Registries on your Azure Container Registry, what security feature is added?
Think about what Azure Defender adds to container registries.
Azure Defender for Container Registries provides vulnerability scanning for images stored in ACR, helping detect security issues before deployment.
You want to limit access to your Azure Container Registry so only resources inside certain Azure Virtual Networks can pull or push images. What is the best practice to achieve this?
Consider how to securely connect PaaS services privately inside your network.
Azure Private Link allows you to create private endpoints for ACR inside your Virtual Networks, restricting access to only those networks securely without exposing the registry publicly.
You delete your Azure Container Registry resource from the Azure Portal. What is the immediate effect on the container images stored inside?
Think about resource deletion behavior in Azure for PaaS services like ACR.
Deleting an Azure Container Registry resource permanently deletes all stored images and metadata immediately. There is no soft-delete or archive feature for ACR.