Study guide

11.1 Read the Scenario Before Picking a Product

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

11.1 Read the Scenario Before Picking a Product

Key Takeaways Explain This Topic AI

SC-900 product-selection questions almost always lead with a business problem, so classify the workload before you read the answer choices.

Microsoft Entra owns identity and access, Microsoft Defender owns protection and detection, Microsoft Sentinel owns SIEM and SOAR, and Microsoft Purview owns compliance and data governance.

Decide whether the scenario is about identity, security operations, cloud workload posture, or compliance before matching a specific service.

Real Microsoft services that solve a different layer of the problem are the most common distractors; the right answer owns the primary job described.

Last updated: June 2026

Product Selection Starts With the Workload

SC-900 is the Microsoft Security, Compliance, and Identity Fundamentals exam: roughly 40 to 60 multiple-choice questions in about 45 to 60 minutes, with a passing score of 700 out of 1000 and no prerequisites. Because it is a fundamentals exam, product-selection questions reward recognition rather than deep configuration skill. The scenario might describe a risky sign-in, a cloud workload recommendation, a phishing campaign, a data loss prevention requirement, or a security operations workflow. Before you scan for a familiar product name, decide what kind of problem the organization is actually trying to solve.

A reliable first pass sorts the scenario into four lanes that mirror the four SC-900 product families. Microsoft Entra is the identity and access lane. Microsoft Defender is the protection and detection lane covering endpoints, email, cloud apps, identity signals, threat intelligence, vulnerability exposure, and cloud workloads. Microsoft Sentinel is the SIEM and SOAR lane for collecting security data, correlating incidents, hunting, and automating response. Microsoft Purview is the compliance and data governance lane for classification, labels, retention, eDiscovery, audit, privacy, risk, and compliance assessment.

Scenario clue Product family to consider first Why it fits

Sign-in risk, multifactor authentication, access review, privileged role Microsoft Entra The problem is identity, access, or governance.

Endpoint, email, SaaS app, on-premises identity attack, cloud workload protection Microsoft Defender The problem is threat protection, detection, or remediation.

Cross-source incident, analytics rule, workbook, hunting query, playbook Microsoft Sentinel The problem is SIEM, SOAR, or security operations workflow.

Sensitivity label, DLP, retention, eDiscovery, audit, compliance score Microsoft Purview The problem is compliance, data protection, or investigation of data activity.

The Four-Step Exam Move

Use a consistent sequence so you never freeze on a long scenario:

Identify the noun being protected — identity, device, app, data, cloud resource, or security event.

Identify the action — authenticate, authorize, detect, investigate, automate, classify, retain, or audit.

Match the action to the product family before choosing a specific service.

Recheck close names , especially Microsoft Defender for Cloud versus Microsoft Defender for Cloud Apps.

Worked examples make the move concrete. A prompt about preventing a privileged administrator from keeping standing access points to Microsoft Entra Privileged Identity Management (PIM) , not Sentinel. A prompt about correlating alerts from many different sources into a single investigable incident points to Microsoft Sentinel , not a single Defender workload product. A prompt about applying a label that marks files as confidential and can trigger encryption points to Microsoft Purview sensitivity labels, even though the protected files live in Microsoft 365.

Distractors Are Usually Real Services

The exam rarely invents fake products. Instead it offers real Microsoft services that solve a different layer of the problem. Azure Firewall controls network traffic but does not perform eDiscovery. Microsoft Defender for Endpoint protects devices but is not where you create retention labels. Microsoft Purview Compliance Manager assesses compliance posture and improvement actions but is not a SIEM. Azure Key Vault stores secrets and keys but does not detect risky sign-ins. The right answer is the product that owns the primary job in the scenario, not a plausible neighbor.

Keep the official SC-900 skill areas in mind when reviewing misses. The four measured domains are: concepts of security, compliance, and identity (about 10 to 15 percent); capabilities of Microsoft Entra and identity and access (about 25 to 30 percent); capabilities of Microsoft security solutions covering Azure infrastructure security, Defender for Cloud, Microsoft Sentinel, and Defender XDR (about 25 to 30 percent); and capabilities of Microsoft compliance solutions covering Purview, the Service Trust Portal, and Priva (about 25 to 30 percent).

Microsoft security and compliance solutions together dominate the blueprint, so being fast at moving from scenario language to the right product family is one of the highest-value skills you can drill before test day. When you slow down and name the lane first, the four-option list usually collapses to a single defensible answer.

Trigger Words That Pin the Lane

Microsoft tends to reuse a vocabulary of trigger words, and learning them is faster than learning every feature. The words below act as near-deterministic lane markers in SC-900 scenarios:

Entra trigger words : sign-in, authentication, multifactor, Conditional Access, role assignment, RBAC, access review, eligible role, privileged, identity risk, tenant, single sign-on, federation, password protection.

Defender trigger words : endpoint, device, malware, phishing, email attachment, SaaS app, shadow IT, virtual machine posture, secure score, vulnerability, threat intelligence, on-premises Active Directory attack.

Sentinel trigger words : data connector, log ingestion, analytics rule, incident, correlate, hunt, KQL, workbook, automation rule, playbook, SIEM, SOAR, security operations center.

Purview trigger words : classify, sensitivity label, DLP, retention, records, eDiscovery, audit log search, insider risk, compliance score, data lifecycle, privacy, subject rights request.

When two lanes seem to apply, the primary verb breaks the tie. A scenario can mention an email phishing campaign (Defender territory) but actually ask how to correlate that alert with sign-in and endpoint alerts into one incident — the primary verb is correlate, so the answer is Sentinel. Another scenario can mention sensitive customer records (Purview territory) but ask how to prevent users from emailing those records externally — the verb is prevent leakage, so the answer is Purview DLP specifically, not labels and not Defender.

Reading for the verb that the question actually asks you to satisfy, rather than the most eye-catching noun, is the discipline that separates a confident pass from a coin-flip.

Finally, watch for questions that ask for the broadest or most appropriate single product. If a scenario lists symptoms that span endpoint, email, and identity and then asks for one unified detection-and-response experience, the intended answer is usually Microsoft Defender XDR (the correlation layer) rather than any single workload Defender. If it asks to bring non-Microsoft logs into the same investigation too, the intended answer shifts to Microsoft Sentinel .

Holding this hierarchy — workload product, then XDR, then Sentinel — in mind prevents both under-selecting (picking one workload product when correlation is required) and over-selecting (jumping to Sentinel when a single workload product is the better fit).