SC-200 Regulatory compliance dashboard Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Secure Score

  Why it's wrong here

  Secure Score in Microsoft Defender for Cloud aggregates the status of all security recommendations into a numeric percentage that represents your overall security posture relative to Microsoft's best practices. However, it is not aligned to any specific regulatory framework such as CIS, and it does not map findings to compliance domains or controls. Therefore, while Secure Score helps prioritize security improvements, it cannot demonstrate compliance against the CIS benchmark, making it incorrect for this requirement.

• ✓

  Regulatory compliance dashboard

  Why this is correct

  The Regulatory compliance dashboard in Defender for Cloud is specifically designed to track and manage compliance against selected standards like CIS and ISO. It works by assigning built-in Azure Policy initiatives that embed the audit requirements of each standard, then continuously evaluating your resources against those policies and displaying pass/fail results for each compliance control. This directly provides the capability to manage security against a particular compliance standard, so it is the correct answer.

• ✗

  Adaptive application controls

  Why it's wrong here

  Adaptive application controls are a workload protection feature that uses machine learning to create and enforce an allowlist of trusted applications on your Azure VMs, blocking unknown or malicious executables. This is a runtime security control focused on preventing malware and unauthorized software, not a compliance assessment tool. It does not evaluate configuration settings, resource compliance, or any standard like CIS, so it is unrelated to the described requirement.

• ✗

  File Integrity Monitoring (FIM)

  Why it's wrong here

  File Integrity Monitoring (FIM) in Defender for Cloud monitors for changes to critical files, directories, and registry keys, and alerts you when suspicious modifications occur. Its purpose is to detect tampering post-breach and support forensic investigations, not to benchmark your environment against regulatory standards. Since it does not map or score resources against CIS controls, it cannot be used to manage compliance with that standard.