Azure SQL Database Security Best Practices
Which THREE are best practices for securing Azure SQL Database? (Choose three.)
Quick Answer
Enable Transparent Data Encryption (TDE) for all databases is a core best practice for securing Azure SQL Database because it automatically encrypts data at rest, ensuring that database files, backups, and transaction logs are protected against unauthorized physical access or theft of storage media. TDE uses a database encryption key (DEK) protected by a service-managed or customer-managed key, and it operates seamlessly without requiring any application changes. On the Microsoft Azure Database Administrator Associate DP-300 exam, this topic frequently appears in questions about defense-in-depth and compliance requirements; a common trap is confusing TDE with column-level encryption or row-level security. Always remember that TDE covers the entire database at rest, while other encryption methods target specific data. A helpful mnemonic is “TDE: The Database Encryptor” — think of it as the mandatory first layer of data protection for any production workload.
⚠ Common exam trap
Test-takers frequently confuse 'public network access' with 'flexible connectivity' and overlook that private endpoints or Azure service endpoints are the secure alternatives, while also mistakenly thinking that granting db_owner simplifies management without considering the security implications of over-privileged accounts.
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 Microsoft Entra ID authentication instead of SQL authentication.
Microsoft Entra ID (formerly Azure AD) authentication provides centralized identity management, supports conditional access policies, and eliminates the need to manage SQL logins and passwords. It also enables features like multifactor authentication (MFA) and integration with Azure RBAC, which significantly reduces the risk of credential theft compared to SQL authentication.
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 Microsoft Entra ID authentication instead of SQL authentication.
Why this is correct
Entra ID provides stronger authentication and supports conditional access.
- ✓
Use Azure SQL Database firewall rules to restrict access to known IP addresses.
Why this is correct
Firewall rules limit network access to authorized IPs.
- ✓
Enable Transparent Data Encryption (TDE) for all databases.
Why this is correct
TDE encrypts data at rest, a fundamental security requirement.
- ✗
Enable public network access to allow flexible connectivity.
Why it's wrong here
Public access should be minimized; use private endpoints for security.
- ✗
Grant db_owner role to developers for ease of management.
Why it's wrong here
Developers should have least privilege; db_owner is too permissive.
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 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 →
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. Which TWO of the following are best practices for securing Azure SQL Database?
medium- A.Enable Auditing to block malicious queries.
- B.Enable TDE to prevent SQL injection attacks.
- C.Use SQL authentication with complex passwords.
- ✓ D.Enable firewall rules to restrict access to specific IP addresses.
- ✓ E.Use Azure Active Directory authentication instead of SQL authentication.
Why D: Azure SQL Database firewall rules allow you to restrict access to specific IP address ranges, which is a fundamental network security best practice. By limiting inbound traffic to only trusted IPs, you reduce the attack surface and prevent unauthorized connections from unknown sources. This is a first line of defense in a defense-in-depth strategy for securing Azure SQL Database.
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.