Courseiva

DP-300 Implement a secure environment Practice Question

Your organization has a policy that all Azure SQL Database connections must use Microsoft Entra authentication. You need to ensure that application developers cannot accidentally use SQL authentication. What should you do?

⚠ Common exam trap

Test-takers frequently think disabling SQL authentication for contained users (Option B) is sufficient, but they miss that the server-level authentication policy must be enforced to block all SQL authentication attempts, including those from server-level logins or newly created contained users.

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

✓

Enable 'Microsoft Entra ID-only authentication' on the logical server.

Enabling 'Microsoft Entra ID-only authentication' on the logical server explicitly blocks all SQL authentication connections, including those from contained database users. This setting enforces that only Microsoft Entra ID (formerly Azure AD) principals can authenticate, directly aligning with the policy to prevent accidental use of 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.

  • ✗

    Configure server-level firewall rules to block all IP addresses except Azure services.

    Why it's wrong here

    Firewall rules filter by source IP, not by authentication method, so a permitted client can still connect using SQL authentication. They are tempting because they restrict network reachability, and would be correct when the requirement is to limit which hosts may reach the server rather than which authentication type is accepted.

  • ✗

    Disable SQL authentication for all contained database users.

    Why it's wrong here

    Disabling SQL authentication for contained users leaves server-level SQL logins and the server admin account usable, so developers can still connect with SQL credentials. It is tempting because contained users are database-scoped, and would be correct when the goal is to restrict access to a single database rather than enforce Entra-only authentication server-wide.

  • ✗

    Create a database-level trigger to reject connections using SQL authentication.

    Why it's wrong here

    A logon trigger can reject sessions, but Azure SQL Database does not support server-level logon triggers for this purpose, and it cannot reliably distinguish authentication type before login completes. Triggers are tempting because they enforce logic inside the database, and would be correct for auditing or blocking specific statements after a session is established.

  • ✓

    Enable 'Microsoft Entra ID-only authentication' on the logical server.

    Why this is correct

    Enabling 'Microsoft Entra ID-only authentication' on the logical server disables all SQL authentication methods, including the server-level admin login. This directly enforces the policy that all connections must use Microsoft Entra ID, as any attempt to connect with a SQL username and password is rejected at the server level. This satisfies the constraint of preventing accidental SQL authentication by developers.

Go deeper

Related to this question

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 →

How Courseiva writes practice questions · Editorial policy

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.