Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure container registry named Registry1 that contains an image named image1. You receive an error message when you attempt to deploy a container instance by using image1. You need to be able to deploy a container instance by using image1. Solution: You create a private endpoint connection for Registry1. Does this meet the goal?

Question

Accepted Answer

B. No While a private endpoint provides private and secure connectivity to Azure Container Registry from a virtual network, merely creating it does not guarantee a container instance will successfully deploy using the image. The container instance must be deployed within the virtual network (or a peered one) where the private endpoint is located, and proper DNS resolution must be configured, along with addressing any other potential issues like authentication.

Answer

A. Yes Creating a private endpoint for ACR addresses only network connectivity from a virtual network. It does not resolve other common deployment errors such as authentication failures, incorrect image references, or the container instance's own network configuration to utilize the private endpoint.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

Question

Options

How the community answered

Why each option

Community Discussion