Question 831 of 919
Configuring Always Encrypted with Secure Enclaves for Azure SQL Database
You are the database administrator for a healthcare organization that uses Azure SQL Database. You need to implement column-level encryption for sensitive patient data (e.g., Social Security numbers) using Always Encrypted. The application connecting to the database is a .NET application running on Azure Virtual Machines. The application should be able to perform parameterized queries on encrypted columns without revealing the plaintext to the database. Which configuration is essential for this setup?
Quick Answer
The answer is to use Always Encrypted with secure enclaves and configure the enclave attestation URL. This configuration is essential because secure enclaves enable the database engine to perform rich parameterized queries—including pattern matching and range comparisons—on encrypted data inside a hardware-based trusted execution environment, without ever exposing the plaintext to the database. Standard Always Encrypted only supports equality comparisons, so without an enclave, an application cannot run LIKE or range queries on encrypted columns. On the Microsoft Azure Database Administrator Associate DP-300 exam, this scenario tests your understanding of when to elevate to enclave-based encryption; a common trap is assuming that basic Always Encrypted with column encryption keys is sufficient for parameterized queries. Remember the mnemonic: “Enclave enables equality and more”—if your query needs anything beyond exact matches, you must add an enclave and its attestation URL.
⚠ Common exam trap
A common mix-up: candidates confuse Always Encrypted without enclaves (which only supports equality) with Always Encrypted with enclaves (which supports richer queries), and they may incorrectly choose key management (Option B) as the essential configuration instead of the enclave attestation URL.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Always Encrypted with secure enclaves and configure the enclave attestation URL.
The scenario requires the application to perform parameterized queries on encrypted columns without revealing plaintext to the database. Always Encrypted with secure enclaves allows rich computations (e.g., equality, pattern matching) on encrypted data inside a hardware-based enclave, and the enclave attestation URL is essential to verify the enclave's integrity. Without the enclave, Always Encrypted only supports equality comparisons and cannot handle parameterized queries that require operations like LIKE or range checks on encrypted columns.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Always Encrypted with secure enclaves and configure the enclave attestation URL.
Why this is correct
Secure enclaves enable rich computations on encrypted data, meeting the requirement.
- ✗
Store the column master key in Azure Key Vault and configure the application to retrieve it.
Why it's wrong here
This is required for any Always Encrypted setup but does not enable computations on encrypted data.
- ✗
Implement dynamic data masking on the columns containing Social Security numbers.
Why it's wrong here
Masking hides data from users but the database engine sees plaintext.
- ✗
Enable Transparent Data Encryption (TDE) on the database.
Why it's wrong here
TDE encrypts data at rest, not in use.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DP-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are the database administrator for a healthcare organization that uses Azure SQL Database. You need to implement column-level encryption for a column containing patient Social Security numbers (SSNs). The SSNs must be encrypted at rest and in transit, and only authorized client applications should be able to decrypt them. Which technology should you use?
medium- A.Row-level security (RLS) to restrict access based on user role.
- B.Dynamic data masking (DDM) to mask SSNs for unauthorized users.
- C.Transparent Data Encryption (TDE) with customer-managed keys.
- ✓ D.Always Encrypted with column master key stored in Azure Key Vault.
Why D: Always Encrypted is the correct choice because it ensures that sensitive data, such as SSNs, is encrypted both at rest and in transit, and the encryption keys are stored client-side (e.g., in Azure Key Vault). This design ensures that only authorized client applications with access to the column master key can decrypt the data, preventing even database administrators or cloud operators from viewing the plaintext values.
Last reviewed: Jul 4, 2026
This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.