Question 290
An Azure SQL operations team investigates: A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address.) is: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails. It directly tests whether the remediation (Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address. The specific supported administrative response is: Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required. The technical risk is: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. Confirm the correction with: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.
Incorrect Answers
SQL authentication management on SQL server vms (2.1) would demonstrate or implement: Approved users authenticate with expected policies while disabled credentials fail and access is logged. This choice can be useful for that problem, but it does not establish the Azure SQL private endpoints and public exposure (2.2) control being assessed here.
Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This case instead tests Azure SQL private endpoints and public exposure (2.2); the choice measures or changes another part of the system.
Diagnosing login and token failures (2.1) addresses another technical failure: Treating every database error as a firewall block can conceal authentication and access-control faults. The required paired action and test concerns Azure SQL private endpoints and public exposure (2.2); a passing result for this alternative could leave that requirement unresolved.