Study guide
5.1 Choose the Right Infrastructure Security Control
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
5.1 Choose the Right Infrastructure Security Control
Key Takeaways Explain This Topic AI
Match the control to the layer: DDoS Protection defends network-layer availability (L3/L4), WAF inspects application-layer web requests (L7), Azure Firewall and NSGs both filter network traffic but at different scopes.
Azure Firewall is a centralized, managed, stateful firewall for whole environments; NSGs are lightweight 5-tuple allow/deny rules attached to subnets or NICs.
The single biggest SC-900 trap is Firewall vs NSG vs WAF: 'centralized stateful policy' = Firewall, 'subnet/NIC allow-deny' = NSG, 'SQL injection / XSS / HTTP' = WAF.
Azure Bastion secures the RDP/SSH admin path without public VM IPs; Azure Key Vault centralizes secrets, keys, and certificates with Microsoft Entra ID authentication.
Last updated: June 2026
Match the Control to the Security Job
Most SC-900 questions about Azure infrastructure security are product-selection questions. The stem describes a risk, a traffic path, or an administrative habit, then asks which Microsoft security service addresses it. Your first move is always the same: identify what is at risk and at which network layer . Is the concern public availability under a flood, malicious HTTP request content, allowed network paths, virtual-machine management access, or sensitive secret material?
Naming the layer collapses most of the wrong answers immediately, because several of these services sound like network security but operate at very different points in the stack.
A reliable way to reason is to ask where enforcement must happen . Azure DDoS Protection absorbs and mitigates volumetric denial-of-service traffic against publicly reachable resources at network layers 3 and 4 . Azure Firewall centrally enforces and logs connectivity policy across an environment. Web Application Firewall (WAF) inspects layer 7 HTTP and HTTPS requests for common web exploits. Network security groups (NSGs) apply simple allow/deny rules close to subnets and network interfaces. Azure Bastion secures the administrative path to VMs. Azure Key Vault protects secret material.
A Selection Table You Can Memorize
Scenario clue in the stem Best Azure control Why it fits
Internet-facing endpoint must stay available during volumetric (L3/L4) floods Azure DDoS Protection Enhanced, always-on mitigation for public IPs in DDoS-enabled virtual networks
Centralized, stateful inspection and logging across many networks Azure Firewall Managed cloud-native firewall for an entire environment (hub-and-spoke)
SQL injection, cross-site scripting, OWASP web exploits Web Application Firewall Rule-based protection of HTTP/HTTPS web apps on App Gateway or Front Door
Permit/deny traffic to a single subnet or VM NIC Network security group Lightweight 5-tuple allow/deny rules at subnet or interface scope
Admins need RDP or SSH without public VM IP addresses Azure Bastion Browser-based RDP/SSH over TLS (port 443) using the VM's private IP
App needs stored secrets, encryption keys, or TLS certificates Azure Key Vault Centralized secrets, key, and certificate management with Entra ID auth
These controls are complementary, not interchangeable . A production web application commonly layers all six: DDoS Protection for network availability, WAF for application-layer inspection, Azure Firewall for hub egress policy, NSGs for subnet filtering, Bastion for private VM administration, and Key Vault for the app's certificates and database connection strings. SC-900 will not ask you to design a landing zone, but it expects you to know these pieces stack into defense in depth .
The Firewall vs NSG vs WAF Trap
This is the chapter's highest-yield distinction. All three filter traffic, so the exam loves to offer two of them as plausible options. Anchor on these phrases:
"Centralized," "stateful," "across virtual networks," "managed firewall," "hub" → Azure Firewall .
"Allow/deny rules," "a subnet," "a network interface," "five-tuple," "inbound/outbound to this VM" → NSG .
"SQL injection," "XSS," "OWASP," "HTTP/HTTPS," "Application Gateway," "Front Door" → WAF .
Read the Layer, Not the Brand Name
Watch wording that points at a layer. Floods, volumetric, denial of service, layer 3/4 point to DDoS Protection . Managed rules, OWASP, web exploit, request inspection point to WAF . Route control, outbound filtering, centralized policy, traffic inspection across VNets point to Azure Firewall . Inbound/outbound allow or deny near subnets points to NSGs .
There is also an administration and data-protection angle. Azure Bastion is not an identity-governance product, but it removes direct public RDP/SSH exposure from virtual machines — a concrete reduction of attack surface. Key Vault is not a firewall, but it supports least privilege by moving passwords, tokens, keys, and certificates out of code and into a controlled service guarded by Microsoft Entra ID authentication plus Azure RBAC authorization.
For the exam, resist picking the most advanced-sounding product. Pick the control whose purpose matches the request:
Identify the protected asset first.
Decide whether the question is about availability, inspection, segmentation, administration, or secrets.
Choose the Azure service designed for that one job.
Remember real architectures combine several of these controls.
If the stem says protect a VM from open management ports , WAF is wrong — the problem is not web request inspection (Bastion plus NSGs fit). If the stem says protect an app from SQL injection , DDoS Protection is wrong — the problem is at the web application layer (WAF fits).
Where Each Control Sits in Defense in Depth
It helps to picture defense in depth as concentric rings around a workload, because SC-900 explicitly tests this layered model. Microsoft's defense-in-depth layers run roughly: physical security, identity and access, perimeter, network, compute, application, and data. The six services in this chapter map cleanly onto those rings, which is why no single one is ever "the" answer to a well-designed environment.
- Defense-in-depth layer Primary chapter control What it stops
- Perimeter Azure DDoS Protection Volumetric floods that exhaust public endpoints
- Network Azure Firewall, NSGs Unwanted lateral movement and unapproved paths
- Application Web Application Firewall SQL injection, XSS, and other L7 web exploits
- Compute (admin path) Azure Bastion Brute-force attacks against exposed RDP/SSH
- Data / secrets Azure Key Vault Leaked keys, passwords, and certificates
A second mental shortcut is to separate prevention from detection . Most controls here are preventive: NSGs and Azure Firewall block disallowed traffic, WAF blocks malicious requests, Bastion removes a public attack surface, and Key Vault restricts who can read a secret. DDoS Protection is preventive too, but it also generates rich telemetry — attack metrics, alerts, and mitigation flow logs — that feed Microsoft Sentinel or another SIEM for detection and post-incident investigation. When an exam stem mentions monitoring, alerting, or streaming logs during an attack, that telemetry angle is the clue.
Finally, beware distractor answers from other chapters . A network-security question may list Microsoft Entra ID, Microsoft Purview, Microsoft Defender for Cloud, or Microsoft Sentinel as options. Those are real Microsoft products, but they answer identity, compliance, posture, or SIEM questions — not "which infrastructure control filters this traffic." If the stem is about a packet path, a flood, an HTTP exploit, an admin connection, or a stored secret, the answer is one of the six services in this chapter, not an identity or compliance product.