What it means
Protection must consider volumetric, protocol, and application-layer attacks. Provider services can absorb or filter traffic, but workload design and operational readiness still matter.
Why it matters
An attack can cause both service disruption and unexpected consumption cost, especially when automatic scaling responds without limits.
Practical focus
- Use layered network and application protections
- Set scaling, rate, and budget safeguards
- Test escalation and provider-support procedures
Common mistakes
- Assuming a cloud provider makes DDoS impossible
- Protecting the edge while leaving the origin exposed
- Ignoring application-layer resource exhaustion
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: