DP-300 Implement a secure environment Practice Question
Your organization uses Azure SQL Database with Microsoft Entra ID authentication. You need to ensure that a specific user can only read data from the Sales schema. The user should not be able to modify any data. What should you do?
⚠ Common exam trap
A common mix-up: candidates assume fixed database roles like db_datareader or db_denydatawriter are sufficient, but they either grant too much access or fail to grant the required read access, whereas schema-level permissions with explicit DENY provide precise control.
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
✓
Create a contained user mapped to the Microsoft Entra identity, then grant SELECT on the Sales schema to the user, and deny SELECT on all other schemas.
It creates a contained database user mapped to the Microsoft Entra identity, then explicitly grants SELECT on the Sales schema. This ensures the user can read data only from that schema. Denying SELECT on all other schemas removes any implicit permissions (such as those from the public role) and enforces the least-privilege principle. This approach is schema-level permission control, which is more granular than fixed database roles.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a contained user mapped to the Microsoft Entra identity, then grant SELECT on the Sales schema to the user, and deny SELECT on all other schemas.
Why this is correct
This explicitly grants SELECT on Sales schema and denies on others, achieving the requirement.
- ✗
Create a contained user mapped to the Microsoft Entra identity and add the user to the db_datareader role.
Why it's wrong here
db_datareader grants read access to all tables in the database, not just Sales schema.
- ✗
Create a contained user mapped to the Microsoft Entra identity and add the user to the db_denydatawriter role.
Why it's wrong here
db_denydatawriter prevents writes but still allows reads on all schemas.
- ✗
Create a contained user mapped to the Microsoft Entra identity and add the user to the db_datareader role, then deny SELECT on all schemas except Sales.
Why it's wrong here
db_datareader already grants SELECT on all schemas; denying SELECT on other schemas would conflict but still allow reads via role membership.
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
Key term
Azure SQL Authentication
Azure SQL Authentication is the process of verifying a user's identity to access an Azure SQL database using either a username and password (SQL Authentication) or a Microsoft Entra ID (formerly Azure AD) identity.
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 906-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.