Question 830
The cloud operations team reviews the following risk: A design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint. Which explanation fits the observed symptoms most closely?
Explanation
Correct Answer
The described technical condition is: Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The appropriate corrective action is: Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service. Confirm with: The service resolves to a VNet private address and only permitted private clients connect.
Incorrect Answers
The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Configure the correct privatelink DNS zone record and link the client VNet to the zone” would address that alternative cause, not the condition in this question: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.
“Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” responds to this separate finding: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. This question instead needs “Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service”, so the alternative does not meet the stated condition.
The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” applies to that separate problem. The observed case is a design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint; choosing this alternative would address the wrong failure mode.