Practice Exam

Explanations for each answer:

• 1. Build a new application image by using the dockerfile 2. Tag the image with the fully qualified path to the registry 3. Log in to the registry 4. Push the image is correct. This is the correct sequence for deploying a Docker image to ACR. First, build the image from the Dockerfile, then tag it with the registry's fully qualified path (like myregistry.azurecr.io/imagename:tag), authenticate to the registry using 'az acr login' or docker login, and finally push the tagged image to ACR where it becomes available for deployment.
• 1. Build a new application image by using the dockerfile 2. Download the image to your local computer 3. Tag the image with the fully qualified path to the registry 4. Push the image is incorrect. After building an image locally with Docker, the image is already on your local computer—there's no separate 'download' step needed. You build locally, tag the local image, authenticate to ACR, and then push. Including a download step is redundant and not part of the ACR deployment workflow.
• 1. Tag the image with a new build number 2. Build a new application image by using the dockerfile 3. Log in to the registry 4. Push the image is incorrect. You cannot tag an image before it exists. The image must be built first using the Dockerfile before you can apply any tags to it. Additionally, simply tagging with a build number isn't sufficient—you need to tag with the full registry path for ACR to accept the push.
• 1. Log in to the registry 2. Pull the image 3. Tag the image with the fully qualified path to the registry 4. Push the image is incorrect. Pulling an image downloads an existing image from a registry, but you need to build a new version of your application from the Dockerfile. Pulling would get an old version; you need to build the new version locally first before tagging and pushing it to ACR.