You are troubleshooting a scenario where an Azure App Service hosting an AI frontend cannot communicate with an Azure OpenAI endpoint secured by a private endpoint in a different virtual network. Which THREE of the following networking configurations should you verify? (Choose three)
A private endpoint resides in its own VNet, so traffic from the App Service VNet must traverse a peering link to reach it. Without peering, routing between the two virtual networks fails, blocking connectivity to the Azure OpenAI private endpoint.
Why this answer
Option B is correct because the App Service VNet and the private endpoint VNet must be peered (or otherwise connected via a gateway/transit) so that traffic can flow between them; without peering, the App Service cannot reach the private endpoint's private IP. Option C is correct because App Service must have regional VNet integration enabled, which routes outbound application traffic from the app into the delegated integration subnet, allowing it to reach the peered VNet and the private endpoint. Option E is correct because the private endpoint's FQDN (e.g., <resource>.privatelink.openai.azure.com) must resolve to the private IP via a private DNS zone linked to the relevant VNets; without this DNS integration, name resolution returns the public IP and the connection fails.
Option A is not relevant because Azure Front Door geo-filtering affects inbound HTTP traffic distribution, not internal DNS resolution or App Service-to-private-endpoint connectivity. Option D is not relevant because local admin passwords on worker instances have no bearing on VNet routing, peering, or private DNS resolution for private endpoint access.
Exam trap
AI-200 often tests the assumption that VNet integration alone is sufficient — candidates forget that private DNS zone linkage is mandatory or that peering must exist between the two VNets.