Question 280
An Azure SQL operations team investigates: A client requires a trusted transport session while private network routing remains separately configured. 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 client requires a trusted transport session while private network routing remains separately configured. The specific supported administrative response is: Require supported TLS encryption, valid certificates and client hostname validation for database network connections. The technical risk is: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. Confirm the correction with: An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.
The acceptance evidence for this incident (A client requires a trusted transport session while private network routing remains separately configured.) is: An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test. It directly tests whether the remediation (Require supported TLS encryption, valid certificates and client hostname validation for database network connections.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. The case states: A client requires a trusted transport session while private network routing remains separately configured. The most direct paired action and test is: Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
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 case instead tests SQL encrypted connections and TLS verification (2.2); the choice measures or changes another part of the system.
Azure SQL firewall rule scoping (2.2) addresses another technical failure: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. The paired-answer requirement concerns SQL encrypted connections and TLS verification (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.