DP-300 Implement a secure environment Practice Question
Your company uses Azure SQL Database. You need to ensure that all connections to the database use TLS 1.2 or higher. Currently, some client applications are connecting using TLS 1.0. What should you do?
⚠ Common exam trap
Many candidates think updating client applications (Option D) is sufficient, but the exam tests the understanding that server-side enforcement is required to guarantee compliance across all clients, especially when you cannot control or update every client application.
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 'Minimum TLS version' property of the logical server to 1.2.
Setting the 'Minimum TLS version' property of the Azure SQL logical server to 1.2 enforces that all incoming connections must use TLS 1.2 or higher. This server-level setting overrides any client-side configuration, blocking connections that attempt to use TLS 1.0 or 1.1. It is the simplest and most effective way to enforce the minimum TLS version across all client applications without requiring changes to each client.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the server firewall to block non-TLS traffic.
Why it's wrong here
A server firewall filters by IP address and port, not by TLS protocol version, so TLS 1.0 clients would still connect. It is tempting because firewalls control network access, and blocking non-TLS traffic would be relevant when restricting connectivity to specific networks rather than enforcing a minimum protocol version.
- ✓
Set the 'Minimum TLS version' property of the logical server to 1.2.
Why this is correct
Configuring the logical server's Minimum TLS version to 1.2 rejects any client handshake negotiating TLS 1.0 or 1.1, directly satisfying the requirement that all connections use TLS 1.2 or higher. This server-level setting enforces the constraint across every database on that server.
- ✗
Set the 'tls_version' database parameter to 1.2 in the master database.
Why it's wrong here
Azure SQL Database exposes no 'tls_version' database parameter; TLS version enforcement is configured through the minimum TLS version setting on the logical server. It is tempting because other database platforms do expose TLS parameters, and setting such a parameter would be correct on a platform that supports per-database TLS configuration.
- ✗
Update the client applications to only use TLS 1.2.
Why it's wrong here
Updating clients fixes only the applications you control, leaving unmanaged or third-party clients still negotiating TLS 1.0. It is tempting because client-side remediation is a genuine hardening step, and it would be the right approach when the server cannot enforce a minimum version and each client must be individually configured.
Go deeper
Related to this question
Learn chapter
Deploying and Configuring SQL Server on Azure Virtual Machines
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 574 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.