Question 740
A production Azure security implementation shows this failure: A payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic. After remediation, which test result best proves the intended change?
Explanation
Correct Answer
This validates the specific control for azure sql private endpoint dns and public disable: The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The associated corrective action is: Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access. Testing a different component would not establish this result.
Incorrect Answers
The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Use supported modern SMB client configuration and private connectivity or TLS where applicable” would address that alternative cause, not the condition in this question: the SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction.
“Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs” responds to this separate finding: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. This question instead needs “Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access”, so the alternative does not meet the stated condition.
TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” applies to that separate problem. The observed case is a payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic; choosing this alternative would address the wrong failure mode.