Quick Answer
The answer is Always Encrypted, because it enables column-level encryption of sensitive data like Social Security numbers while keeping encryption keys entirely under client control, ensuring compliance with HIPAA requirements for both data at rest and key management. Unlike Transparent Data Encryption, which encrypts the entire database but offers no granular key control, Always Encrypted allows applications to encrypt specific columns before data reaches Azure SQL Database, and with secure enclaves, computations on encrypted data become possible without exposing plaintext. On the DP-900 exam, this question tests your ability to distinguish between data protection features: Always Encrypted is the only option that combines column-level encryption with client-side key ownership, whereas Dynamic Data Masking only hides data visually and Row-Level Security restricts row access without encryption. A common trap is confusing Always Encrypted with TDE, so remember the mnemonic “ACE” — Always Encrypted for Columns, client-side keys, and Enclaves — to keep the focus on granular, key-controlled protection.
This DP-900 practice question tests your understanding of identify considerations for relational data on azure. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A healthcare organization uses Azure SQL Database to store patient records. To comply with HIPAA regulations, they need to encrypt sensitive columns (e.g., Social Security numbers) at rest and control access to the encryption keys. Which feature should they use?
Dynamic Data Masking
Why wrong: Masking obfuscates but does not encrypt data.
Row-Level Security
Why wrong: RLS restricts row access but does not encrypt columns.
Always Encrypted
Always Encrypted encrypts specific columns and allows client-side key management.
Transparent Data Encryption (TDE)
Why wrong: TDE encrypts data at rest but not column-specific key control.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Always Encrypted
Option A is correct because Always Encrypted with secure enclaves protects sensitive columns at rest and allows client-side key management. Option B is wrong because Transparent Data Encryption encrypts the entire database but does not allow column-level key control. Option C is wrong because Dynamic Data Masking obfuscates data but does not encrypt it. Option D is wrong because Row-Level Security restricts row access but does not encrypt columns.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Dynamic Data Masking
Why it's wrong here
Masking obfuscates but does not encrypt data.
Row-Level Security
Why it's wrong here
RLS restricts row access but does not encrypt columns.
Always Encrypted
Why this is correct
Always Encrypted encrypts specific columns and allows client-side key management.
Related concept
CIDR notation defines the prefix length.
Transparent Data Encryption (TDE)
Why it's wrong here
TDE encrypts data at rest but not column-specific key control.
Common exam traps
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Detailed technical explanation
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Real-world example
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related DP-900 subnetting questions on CIDR, address ranges, and subnet selection.
Identify considerations for relational data on Azure — study guide chapter
Learn the concepts, then practise the questions
Identify considerations for relational data on Azure practice questions
Targeted practice on this topic area only
All DP-900 questions
982 questions across all exam domains
Microsoft Azure Data Fundamentals DP-900 study guide
Full concept coverage aligned to exam objectives
DP-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise DP-900 questions linked to Describe core data concepts.
Practise DP-900 questions linked to Describe an analytics workload on Azure.
Practise DP-900 questions linked to Identify considerations for relational data on Azure.
Practise DP-900 questions linked to Describe considerations for working with non-relational data on Azure.
Practise DP-900 questions linked to DP-900 fundamentals.
Practise DP-900 questions linked to DP-900 scenario.
Practise DP-900 questions linked to DP-900 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Identify considerations for relational data on Azure — This question tests Identify considerations for relational data on Azure — CIDR notation defines the prefix length..
The correct answer is: Always Encrypted — Option A is correct because Always Encrypted with secure enclaves protects sensitive columns at rest and allows client-side key management. Option B is wrong because Transparent Data Encryption encrypts the entire database but does not allow column-level key control. Option C is wrong because Dynamic Data Masking obfuscates data but does not encrypt it. Option D is wrong because Row-Level Security restricts row access but does not encrypt columns.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related DP-900 subnetting questions on CIDR, address ranges, and subnet selection.
CIDR notation defines the prefix length.
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 →
Last reviewed: Jun 20, 2026
This DP-900 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-900 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.