DP-300 Implement a secure environment Practice Question
You need to prevent users from accidentally deleting an Azure SQL Database. What should you configure?
⚠ Common exam trap
Many exam-takers confuse database-level permissions (like db_ddladmin) with Azure Resource Manager-level operations, mistakenly thinking that revoking schema modification rights will prevent database deletion, when in fact deletion is an ARM operation controlled by locks or RBAC at the subscription/resource group scope.
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
✓
Apply a 'CanNotDelete' Azure Resource Lock on the resource group.
A 'CanNotDelete' Azure Resource Lock on the resource group prevents any user, including those with high-level permissions like Owner, from deleting the Azure SQL Database. This lock overrides all role-based access control (RBAC) permissions at the resource or resource group level, ensuring accidental deletion is blocked even if a user has delete permissions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Apply a 'CanNotDelete' Azure Resource Lock on the resource group.
Why this is correct
Resource lock prevents deletion of Azure resources.
- ✗
Revoke the db_ddladmin role from users.
Why it's wrong here
DDL admin controls schema changes, not resource deletion.
- ✗
Create an Azure Policy to deny SQL Database creation.
Why it's wrong here
An Azure Policy denying SQL Database creation prevents provisioning of new databases but does not block deletion of an existing database, which is the specific requirement in the stem. It is tempting because Azure Policies enforce governance rules at the subscription or resource-group scope, making them a natural choice for controlling resource lifecycle. This option would be correct if the stem asked to prevent unauthorised provisioning rather than accidental deletion.
- ✗
Set a deny rule in the SQL Database firewall.
Why it's wrong here
Firewall controls network access, not resource deletion.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
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
One of 906 original DP-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.