Question 720
A new Azure SQL Database private endpoint has been requested but its connection remains Pending approval. Meanwhile, VM clients in vnet-payroll continue to resolve sql-payroll.database.windows.net to a public address because their VNet has no link to the private endpoint DNS zone. Which TWO independent configurations must be completed? Select TWO answers.
Explanation
Correct Answers
A pending private endpoint connection is not an approved private path to the SQL resource. An authorized owner must confirm that the request targets the right SQL server and approve it so the connection reaches the approved state. This resolves the connectivity authorization half of the problem. Approval alone cannot make VM DNS use the endpoint’s private IP; the client VNet must also see the associated private DNS records.
Azure SQL Database private endpoints use the private zone privatelink.database.windows.net. Linking the client VNet and ensuring its A record targets the endpoint IP allows the normal sql-payroll.database.windows.net lookup to resolve privately through the expected CNAME chain. This fixes the separate DNS defect identified in the stem. DNS alone cannot approve a Pending private endpoint, so the matching endpoint approval remains necessary before reliable application connections.
Incorrect Answers
For Azure SQL Database, connection strings should continue to use the normal logical-server FQDN, not the raw private endpoint address. SQL Gateway routing and certificate validation depend on the proper name. Direct-IP connection attempts can fail even when the private endpoint is healthy. Correct the name resolution and endpoint approval while leaving clients on the supported server DNS name.
Service endpoints use a different routing and firewall mechanism and do not approve an outstanding Private Link connection. The requirement explicitly calls for the new SQL private endpoint, and its Pending state remains unresolved by switching to a public service-endpoint path. This choice also leaves the reported private-zone DNS failure in place.
Allowing public Azure services can create an additional public ingress route rather than repair the private connection. It neither approves the Pending endpoint request nor provides the private DNS mapping required for VNet clients. The business requirement is specifically to use the private endpoint; exposing public connectivity as a workaround contradicts the intended network boundary.