Your organization is using Microsoft Defender for Cloud to protect Azure SQL databases. You need to enable Advanced Threat Protection (ATP) for all existing and future Azure SQL databases in a subscription. The solution must minimize administrative effort. What should you do?
Correct. Enabling the plan at the subscription level applies to all current and future resources.
Why this answer
Enabling the Azure SQL databases plan in Microsoft Defender for Cloud at the subscription level automatically enables Advanced Threat Protection (ATP) for all existing and future Azure SQL databases within that subscription. This approach requires minimal administrative effort because it applies the protection globally without needing to configure each database individually or create custom policies. Microsoft Defender for Cloud manages the ATP settings centrally, ensuring consistent security coverage across the entire subscription.
Exam trap
The trap here is that candidates often confuse enabling a Defender for Cloud plan (which is a simple toggle at the subscription level) with creating an Azure Policy (which is a more complex, policy-as-code approach), leading them to choose Option C even though it requires more administrative effort than the direct plan enablement.
How to eliminate wrong answers
Option A is wrong because Microsoft Sentinel is a Security Information and Event Management (SIEM) tool used for threat detection and response across multiple sources, not a mechanism to enable ATP on Azure SQL databases; it can ingest alerts from Defender for Cloud but does not enable the ATP feature itself. Option C is wrong because while an Azure Policy can enforce the deployment of ATP on Azure SQL databases, it requires creating and assigning a custom policy definition, which introduces additional administrative overhead compared to simply enabling the plan at the subscription level; the question specifically asks to minimize administrative effort. Option D is wrong because enabling ATP on each Azure SQL database individually is the most labor-intensive approach and contradicts the requirement to minimize administrative effort, as it does not automatically cover future databases.