Question 270
An Azure SQL operations team investigates: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. 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 team enables encrypted columns but fails to validate whether its planned query functions are supported.) is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. It directly tests whether the remediation (Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
Incorrect Answers
Contained database users from entra identities (2.1) would demonstrate or implement: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This choice can be useful for that problem, but it does not establish the Always encrypted secure enclave workloads (2.2) control being assessed here.
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 Always encrypted secure enclave workloads (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.