Study guide

6.1 Defender for Cloud Purpose and Exam Role

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

6.1 Defender for Cloud Purpose and Exam Role

Key Takeaways Explain This Topic AI

Microsoft Defender for Cloud is a Cloud-Native Application Protection Platform (CNAPP) for Azure, hybrid, and multicloud (AWS and GCP) resources.

Its two anchor capabilities are Cloud Security Posture Management (CSPM) for hardening and Cloud Workload Protection Platform (CWPP) for threat detection.

SC-900 positions Defender for Cloud as the product for assessing resources, surfacing recommendations, calculating secure score, and protecting workloads.

Do not confuse Defender for Cloud with Defender for Cloud Apps (the cloud access security broker for SaaS) or Microsoft Sentinel (the SIEM/SOAR).

Last updated: June 2026

Defender for Cloud as a CNAPP

Microsoft Defender for Cloud is the primary SC-900 service for cloud resource posture and workload protection. Microsoft now describes it as a Cloud-Native Application Protection Platform (CNAPP) — a unified solution that combines multiple cloud security tools to protect applications across their entire lifecycle, from code to runtime. The acronym CNAPP is increasingly tested, so memorize that Defender for Cloud is a CNAPP and that a CNAPP folds posture management, workload protection, and development security into one experience.

Microsoft frames Defender for Cloud around three core components:

Cloud Security Posture Management (CSPM) — checks and improves the security posture of cloud resources (the pre-breach, hardening side).

Cloud Workload Protection Platform (CWPP) — defends workloads such as virtual machines, containers, storage, databases, and serverless functions from threats (the active, threat-detection side).

Development Security Operations (DevSecOps) — manages code-level security across multicloud and multi-pipeline environments (GitHub, Azure DevOps, GitLab).

For SC-900 the two you must know cold are CSPM and CWPP . When a scenario asks how to understand and improve the security state of Azure or multicloud resources, Defender for Cloud is almost always the correct product family.

Recognizing Defender for Cloud Scenarios

The easiest way to spot Defender for Cloud is assessment language. Microsoft documents it as continually assessing resources, subscriptions, and the organization for security issues, then aggregating findings into posture views, recommendations, and a score so teams can decide what to fix first. That makes it different from a single network control (such as a web application firewall) or an identity tool (such as Microsoft Entra Privileged Identity Management).

  • Scenario wording Defender for Cloud concept
  • Assess cloud resources for security issues Cloud Security Posture Management (CSPM)
  • Show recommendations to harden resources Security recommendations
  • Track cloud posture in a single number Cloud secure score
  • Monitor compliance against assigned standards Regulatory compliance dashboard
  • Protect machines, containers, or databases from threats Cloud workload protection / Defender plans
  • Review which assets are protected or unprotected Asset inventory and coverage views

Defender for Cloud also surfaces a unified portal dashboard that includes security posture, threat protection, asset coverage, critical recommendations, high-severity incidents, attack paths, and workload insights. SC-900 does not expect you to operate every blade — only to connect this dashboard wording to Defender for Cloud.

Common Traps and Product Boundaries

A frequent exam trap is confusing Defender product names. Defender for Cloud protects cloud resources, posture, and workloads. Defender for Cloud Apps is a separate cloud access security broker (CASB) focused on SaaS discovery and control. Defender for Endpoint protects endpoint devices. Defender for Identity protects on-premises Active Directory. If the prompt says cloud posture, subscriptions, resource recommendations, secure score, or workload-protection plans, stay with Defender for Cloud.

Use product purpose to eliminate distractors:

Azure Firewall, NSGs, DDoS Protection, and Bastion are infrastructure controls — they do not calculate secure score or assess subscriptions against standards.

Key Vault stores secrets, keys, and certificates — it does not assess posture.

Microsoft Sentinel is the cloud-native SIEM and SOAR for collecting, detecting, investigating, and automating across all security data; Defender for Cloud feeds alerts into Sentinel but is not itself the SIEM.

Microsoft Purview owns compliance, data classification, and governance — not cloud resource posture.

Defender for Cloud spans the timeline: pre-breach it exposes misconfigurations, missing protections, and compliance gaps through CSPM; during or after an attack it raises workload-protection alerts through CWPP. SC-900 may use the phrases pre-breach posture and post-breach threat protection — both live inside Defender for Cloud.

Choose Defender for Cloud for posture, recommendations, secure score, workload protection, and regulatory compliance views.

Choose Sentinel for SIEM/SOAR.

Choose Microsoft Entra services for identity and access.

Choose Microsoft Purview for compliance, information protection, and audit.

Where Defender for Cloud Fits in the Microsoft Security Story

SC-900's third skill area covers the capabilities of Microsoft security solutions , and Defender for Cloud is one of three pillars there alongside Microsoft Sentinel (the cloud-native SIEM and SOAR) and Microsoft Defender XDR (the extended detection and response suite covering endpoints, email, identity, and apps). A clean mental model: Defender for Cloud secures the cloud infrastructure and workloads , Defender XDR secures the end-user and productivity estate , and Sentinel collects, correlates, and automates across everything.

' questions quickly, because each prompt usually emphasizes one scope — cloud resources, user devices/mail, or organization-wide log analytics and automation.

It also helps to know how Defender for Cloud is enabled and billed, because the exam contrasts free and paid tiers. The moment you turn on Defender for Cloud on an Azure subscription, you get free Foundational CSPM and access to Microsoft Defender XDR at no charge. Layering on any Defender plan (for servers, storage, databases, containers, and so on) or the Defender CSPM plan adds paid, advanced capabilities. This free-then-upgrade structure is exactly why a single product can appear in both 'free posture visibility' and 'paid threat protection' questions.

A Quick Worked Selection Example

The requirements resolve cleanly: one place across Azure and AWS means multicloud, so Defender for Cloud; seeing misconfigurations and tracking a posture score means CSPM and secure score (free Foundational CSPM); and alerts when a database is attacked means CWPP, so enable Defender for Databases . Every requirement points to Defender for Cloud with one paid Defender plan layered on — the pattern the exam rewards: identify the product from the assessment/protection language, then name the specific capability.

  • 'Which solution?' clue Best answer
  • Secure cloud resources, posture, and workloads Microsoft Defender for Cloud
  • Collect and correlate logs, automate response Microsoft Sentinel
  • Protect endpoints, email, identity, and SaaS apps Microsoft Defender XDR
  • Discover and control SaaS / shadow IT Microsoft Defender for Cloud Apps
  • Govern, classify, and protect data Microsoft Purview