A team switched its Azure SQL traffic off the old service endpoint path onto a private endpoint. Apps that connect by IP work, but apps using the server name fail. What should be fixed?
Show answer and explanation
Answer: B
A private endpoint only helps name-based clients when the server's public FQDN resolves through the privatelink zone to the endpoint's private IP. When DNS still returns the public record, name-based clients take the public path, which the new design no longer permits, so connections fail. IP-based connections work because they skip DNS. Pool size, NSG removal, and reenabling service endpoints do not change how the name resolves.
Why the other options are wrong
- A. Connection pool settings affect how many connections an application keeps open. They do not change the address a server name resolves to, so the failures would persist.
- C. Removing an NSG opens traffic in the subnet but does not change which address the server name resolves to. The name lookup still returns the public record, so the failure remains.
- D. Reenabling the service endpoint alongside the private endpoint does not fix name lookup. The server name still resolves to the public record, so the migration problem is left in place.