DP-300 Implement a secure environment Practice Question
Your company has an Azure SQL Database that contains sensitive financial data. You need to ensure that database administrators cannot view the actual data while still being able to perform administrative tasks such as backups and index maintenance. Which feature should you implement?
⚠ Common exam trap
Watch out — candidates often confuse Dynamic Data Masking with encryption, assuming it provides strong data protection, when in fact it is a lightweight obfuscation that can be easily circumvented by privileged users.
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
✓
Always Encrypted with column master key stored in Azure Key Vault
Always Encrypted with the column master key stored in Azure Key Vault ensures that sensitive data is encrypted at the client side and the encryption keys are never exposed to the database engine. This means database administrators (DBAs) can perform administrative tasks like backups and index maintenance on the encrypted columns without ever being able to view the plaintext data, because the SQL Server instance only sees ciphertext.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Always Encrypted with column master key stored in Azure Key Vault
Why this is correct
Always Encrypted keeps data encrypted in memory and at rest, so administrators querying the database see only ciphertext while backups and index maintenance still function. Storing the column master key in Azure Key Vault separates key custody from the administrators, satisfying the requirement.
- ✗
Row-Level Security
Why it's wrong here
Row-Level Security filters which rows a principal may read, but administrators granted db_owner or sysadmin rights can still query unmasked column values, so actual data remains visible. It is tempting because RLS genuinely restricts row visibility for application users, which is its intended scenario, not hiding columns from administrators.
- ✗
Dynamic Data Masking
Why it's wrong here
Dynamic Data Masking only rewrites query output for non-privileged users; members of the sysadmin or db_owner roles always see unmasked values, so administrators still read the financial data. It is tempting because masking does hide sensitive columns, but its correct scenario is limiting exposure to application users, not administrators.
- ✗
Transparent Data Encryption
Why it's wrong here
Transparent Data Encryption protects data at rest by encrypting the database files, yet any administrator with query access reads decrypted plaintext through normal connections. It is tempting because TDE genuinely secures backups and stolen files, which is its intended scenario, but it does not restrict what an authenticated administrator can view.
Go deeper
Related to this question
Learn chapter
Deploying and Configuring Azure SQL Managed Instance
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
About these practice questions
This DP-300 question is part of Courseiva's 574-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.