Question 240
An Azure SQL operations team investigates: A database owner confuses TDE with encryption of the client network connection. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A database owner confuses TDE with encryption of the client network connection.) is: Encryption state and database availability checks confirm files are encrypted while ordinary authorized queries continue. It directly tests whether the remediation (Enable and validate supported transparent data encryption for Azure SQL or SQL Server databases with appropriate key management.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A database owner confuses TDE with encryption of the client network connection. The specific supported administrative response is: Enable and validate supported transparent data encryption for Azure SQL or SQL Server databases with appropriate key management. The technical risk is: TDE protects physical database files and backups at rest but does not by itself hide plaintext from authorized SQL queries. Confirm the correction with: Encryption state and database availability checks confirm files are encrypted while ordinary authorized queries continue.
Incorrect Answers
Customer-managed tde keys in azure key vault (2.2) addresses another technical failure: Key deletion or disabled access can render encrypted databases unavailable despite healthy compute and storage. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: Encryption state and database availability checks confirm files are encrypted while ordinary authorized queries continue.
SQL database auditing and audit storage (2.3) would demonstrate or implement: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. This case instead tests Transparent data encryption at rest (2.2); the choice measures or changes another part of the system.
Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The paired-answer requirement concerns Transparent data encryption at rest (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.