DP-300 Implement a secure environment Practice Question
You have a new Azure SQL Database. You need to ensure that all connections use TLS 1.2 or higher. What should you configure?
⚠ Common exam trap
Many exam-takers confuse the 'minimal TLS version' setting with a database-level property or think that firewall rules or connection string options can enforce TLS version restrictions, but Azure SQL Database only exposes this control at the server level.
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
✓
Set the 'minimal TLS version' to 1.2 in the server's properties in the Azure portal.
To enforce TLS 1.2 or higher for all connections to an Azure SQL Database, you must configure the 'minimal TLS version' setting at the server level in the Azure portal. This setting applies to all databases hosted on that logical server, ensuring that any client attempting to connect with a TLS version lower than 1.2 is rejected. The server-level property directly controls the TLS protocol version accepted during the SSL/TLS handshake, overriding any client-side or database-level settings.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set the 'minimal TLS version' to 1.2 in the server's properties in the Azure portal.
Why this is correct
Configuring the server-level minimal TLS version to 1.2 rejects any client handshake negotiating TLS 1.0 or 1.1, enforcing the requirement across every database on that logical server. This is a server property, so it applies to all connections without per-database changes.
- ✗
Set the 'minimal TLS version' to 1.2 in the database's properties.
Why it's wrong here
Azure SQL Database exposes no per-database 'minimal TLS version' property; the minimum TLS version is configured at the logical server level, so setting it in database properties is not possible. It is tempting because server-level minimal TLS version is exactly the setting that enforces TLS 1.2, but the scope here is wrong.
- ✗
Add a firewall rule to deny connections using TLS 1.0 or 1.1.
Why it's wrong here
Azure SQL Database firewall rules filter by source IP address and cannot inspect the TLS version negotiated during the handshake, so such a rule never denies TLS 1.0 or 1.1 clients. Firewall rules are tempting because they restrict network access, and would be correct when limiting connections to specific IP ranges.
- ✗
Enable the 'Force encryption' option in the connection string and require TLS 1.2.
Why it's wrong here
'Force encryption' in a connection string is a client-side directive that encrypts the session; it does not compel the server to reject TLS 1.0 or 1.1 handshakes. It is tempting because forcing encryption sounds like enforcing a version, and would be correct when a client must guarantee its own traffic is encrypted.
Go deeper
Related to this question
Learn chapter
Implementing High Availability for Azure SQL Databases
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.