Question 300
An Azure SQL operations team investigates: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
The acceptance evidence for this incident (A database-level firewall exception must be documented without bypassing the organization's public endpoint policy.) is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. It directly tests whether the remediation (Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Managed identity database access (2.1) would demonstrate or implement: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. This choice can be useful for that problem, but it does not establish the Azure SQL firewall rule scoping (2.2) control being assessed here.
SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The required paired action and test concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.
Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. The paired-answer requirement concerns Azure SQL firewall rule scoping (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.