Study guide
5.2 Azure DDoS Protection for Availability
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.2 Azure DDoS Protection for Availability
Key Takeaways Explain This Topic AI
A DDoS attack is an availability attack: it floods a public endpoint so legitimate users cannot reach the application; Azure DDoS Protection adds enhanced L3/L4 mitigation around resources in DDoS-enabled virtual networks.
Azure DDoS Protection has two paid tiers: Network Protection (whole-VNet, includes DDoS Rapid Response, cost protection, and a WAF discount) and IP Protection (per public-IP, no Rapid Response).
DDoS Protection guards layers 3 and 4 only; layer 7 web exploits still require a Web Application Firewall, so the two are paired in a layered design.
Adaptive tuning, attack metrics, alerts, and mitigation flow logs streamed to Microsoft Sentinel support detection and investigation during an attack.
Last updated: June 2026
Protect Public Availability from DDoS Attacks
Distributed denial-of-service (DDoS) attacks are availability attacks — they target the A in the CIA triad. The attacker overwhelms an application or its reachable endpoint with traffic so legitimate users cannot use it. In Azure scenarios the exam clue is usually a public endpoint, a virtual-network resource, or a business requirement to stay reachable during high-volume malicious traffic. Azure DDoS Protection is the Microsoft service that addresses this risk.
Microsoft describes Azure DDoS Protection as enhanced mitigation that is automatically (adaptively) tuned to help protect specific Azure resources in a virtual network, combined with application design best practices. That phrasing matters for SC-900: the service does not replace good architecture — it adds always-on, Azure-native mitigation around resources that public reachability would otherwise expose. Every Azure customer also gets DDoS Infrastructure Protection (also called basic) for free at the platform level; the paid offering adds dedicated monitoring, adaptive tuning, telemetry, and guarantees for your resources.
Two Paid Tiers: Network Protection vs IP Protection
The paid offering comes in two SKUs, and the exam may test the difference at a conceptual level.
Tier Scope Key extras Best when
DDoS Network Protection Plan covers an entire DDoS-enabled virtual network (up to 100 public IPs included) DDoS Rapid Response (DRR) team support, cost-protection guarantee, WAF discount You have many protected public IPs (roughly 15+)
DDoS IP Protection Enabled per individual public IP address Same core mitigation, but no Rapid Response or cost-protection extras You only need to protect a few public IPs
The rule of thumb Microsoft publishes: if you protect fewer than about 15 public IP resources , the per-IP IP Protection tier is more cost-effective; beyond that, the whole-network Network Protection tier wins. You do not need exact prices for SC-900, but knowing Network Protection = whole VNet + Rapid Response versus IP Protection = per public IP is fair game.
- DDoS concept Exam-safe meaning
- Attack goal Exhaust resources so the app is unavailable to legitimate users
- Primary Azure control Azure DDoS Protection
- Network layer focus Layers 3 and 4 only
- Web application gap Layer 7 web protection needs a WAF
- Investigation support Metrics, alerts, attack analytics, and mitigation flow logs to Sentinel/SIEM
Layer Boundaries and Layered Design
The layer distinction is the most testable point. Azure DDoS Protection protects at layers 3 and 4 . If a stem describes SQL injection, cross-site scripting, malicious HTTP headers, or other application-layer web exploits, the better answer is WAF . If the stem describes volumetric traffic against an internet-facing endpoint, DDoS Protection is the natural answer.
DDoS Protection slots into a layered design rather than replacing other controls. A web workload can use DDoS Protection for network-layer floods and WAF for application-layer attacks; NSGs still limit which traffic reaches subnets or interfaces; Azure Firewall still provides central inspection and policy. These controls cover different attack paths and do not cancel one another.
Do not overstate the service for the exam. Azure DDoS Protection is not a guarantee that no outage can ever occur, and it is not the tool for storing secrets, reviewing identity risk, or classifying data. Keep your answer tied to enhanced mitigation, public availability, and network-layer attack traffic .
A useful mental model: imagine a public application behind several layers. DDoS Protection addresses the flood before it consumes the environment; WAF inspects the request content ; Firewall and NSGs enforce allowed paths ; Bastion removes unnecessary public management exposure; Key Vault protects secret material .
Choose DDoS Protection when the question emphasizes denial of service or public availability.
Pair DDoS Protection with WAF when the workload is a web application.
Treat DDoS Protection as part of defense in depth, not a substitute for every other control.
Treat metrics, alerts, attack analytics, and Sentinel flow logs as detection and investigation support.
Attack Types and Why Mitigation Is Adaptive
DDoS attacks come in categories, and understanding them clarifies why a managed service exists. Volumetric attacks flood the target with massive traffic to saturate bandwidth (for example, UDP or amplification floods). Protocol attacks consume connection-state resources on network devices (for example, SYN floods). Resource (application-layer) attacks target the application itself — these are layer 7, and that is precisely where DDoS Protection hands off to WAF . Azure DDoS Protection focuses on the first two categories at layers 3 and 4 .
- Attack category Layer Example Best Azure control
- Volumetric L3/L4 UDP/amplification flood Azure DDoS Protection
- Protocol L3/L4 SYN flood Azure DDoS Protection
- Resource / application L7 HTTP flood, slowloris Web Application Firewall
The word adaptive is worth knowing. DDoS Protection learns the normal traffic patterns (a policy baseline ) for each protected public IP. When traffic crosses the learned threshold, mitigation engages automatically and continues until traffic normalizes — without the customer manually invoking anything.
This is the difference between the free platform-level Infrastructure Protection every Azure customer gets and the paid offering: the paid tiers add dedicated, per-resource adaptive tuning, telemetry, alerting, and (on Network Protection) the DDoS Rapid Response (DRR) team plus a cost-protection guarantee that credits scale-out costs incurred during a documented attack.
A frequent exam trap is treating DDoS Protection as a security-of-data control. It is not. It does not inspect payloads for malware, it does not encrypt anything, and it does not authenticate users. Its single job is availability — keeping a reachable resource reachable. Pair it with WAF for request content, with NSGs and Azure Firewall for allowed paths, and with identity controls for who may connect.