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.
Option A is correct because Microsoft Entra ID authentication centralizes identity management, supports MFA and conditional access, and eliminates the risk of weak or shared SQL logins and passwords. Option B is correct because Azure SQL Database firewall rules (server-level and database-level) limit inbound connections to specific, known IP address ranges, reducing the exposed attack surface from the public internet. Option C is correct because Transparent Data Encryption (TDE) encrypts data at rest, including backups and log files, protecting against unauthorized access to physical media or backup theft. Option D is not a best practice because enabling public network access broadens exposure; private endpoints or restricted firewall rules are preferred. Option E is not a best practice because granting db_owner to developers violates least privilege and gives excessive control over the database.
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
Microsoft Entra ID authentication eliminates stored SQL logins and passwords, satisfying the stem's requirement to secure Azure SQL Database. It enforces centralised identity governance, conditional access and multifactor authentication, while supporting managed identities for application connections. This removes credential sprawl and weak password reuse, which SQL authentication cannot prevent.
- ✓
Use Azure SQL Database firewall rules to restrict access to known IP addresses.
Why this is correct
Firewall rules restrict inbound connections to known IP ranges, blocking unapproved internet access to the logical server. This satisfies the stem's best-practice requirement by minimising the network attack surface, complementing private endpoints and Entra ID authentication.
- ✓
Enable Transparent Data Encryption (TDE) for all databases.
Why this is correct
Transparent Data Encryption provides real-time encryption and decryption of data, log files, and backups at rest, satisfying the requirement to protect stored data. It operates at the page level within the database engine, using a database encryption key protected by a certificate, ensuring compliance without application changes.
- ✗
Enable public network access to allow flexible connectivity.
Why it's wrong here
Public network access exposes the logical server to the internet, widening the attack surface; private endpoints and firewall rules restrict it. Public access is chosen only when connectivity from outside Azure is genuinely required and cannot be achieved privately.
- ✗
Grant db_owner role to developers for ease of management.
Why it's wrong here
Granting db_owner hands developers full control over schema, data and permissions, violating least privilege and enabling destructive changes or privilege escalation. It is tempting because db_owner genuinely suits dedicated development instances where a single team owns the entire database lifecycle. In shared or production Azure SQL Database environments, narrower roles such as db_datareader, db_datawriter or custom roles satisfy the same management needs.
Go deeper
Related to this question
Learn chapter
Managing Identity and Access for Azure SQL
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.
Key term
Azure SQL Firewall Rules
Azure SQL Firewall Rules are security settings that control which IP addresses or Azure services are allowed to connect to a SQL database hosted in Microsoft Azure.
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 →
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: Option D is correct because Azure SQL Database firewall rules (server-level and database-level) restrict inbound connections to approved IP address ranges, reducing the exposed attack surface by denying traffic from unknown sources. Option E is correct because Azure Active Directory (now Microsoft Entra ID) authentication centralizes identity management, supports MFA and conditional access, and eliminates the risk of weak or shared SQL logins and passwords. Option A is incorrect because Auditing records and logs activity for compliance and forensics; it does not block or prevent malicious queries. Option B is incorrect because Transparent Data Encryption encrypts data at rest (and backups) and does nothing to stop SQL injection, which is an application-layer input validation issue. Option C is incorrect because SQL authentication with complex passwords is a weaker, legacy approach compared to Entra ID authentication, and complex passwords alone do not constitute a best practice 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.