Question 340
While validating an Azure workload, the security team finds: An app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption. Which safeguard would best prevent this issue from recurring?
Explanation
Correct Answer
This guardrail addresses azure sql network tls encryption: Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The prevention measure is: Test secure SQL client driver configurations during application and certificate renewals. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. “Review Entra SQL administrator assignments and database access periodically” would address that alternative cause, not the condition in this question: encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
“Audit file-share permissions at both Azure share level and file system ACL layers” 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 “Test secure SQL client driver configurations during application and certificate renewals”, so the alternative does not meet the stated condition.
TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” applies to that separate problem. The observed case is an app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption; choosing this alternative would address the wrong failure mode.