Loading course title...

Loading assessment title...

Connecting to LMS... Progress: in progress

Assessment

1. What is the main goal of DDoS mitigation? A. Generate more test traffic B. Hide all logs C. Protect service availability during traffic pressure D. Remove every public service forever

2. What should a team do before a DDoS incident? A. Inventory critical services, baselines, providers, and escalation paths B. Disable monitoring C. Remove all runbooks D. Wait until the incident starts

3. Which DDoS category focuses on expensive web or API behavior? A. Firmware failure B. Printer discovery C. Patch management D. Application-layer pressure

4. Why are traffic baselines useful? A. They replace incident response B. They help teams recognize unusual traffic and saturation C. They prove every spike is hostile D. They remove the need for provider contacts

5. What can edge services such as CDN, WAF, DNS protection, Anycast, or scrubbing help do? A. Eliminate all architecture planning B. Make origins public by default C. Absorb, filter, or route traffic before it overwhelms origin systems D. Disable user access permanently

6. What is a risk of overly broad blocking during mitigation? A. It always improves customer experience B. It has no business impact C. It removes the need for communication D. It can block legitimate users, partners, monitoring, or recovery paths

7. Which application-layer control can help preserve availability during heavy request pressure? A. Caching, quotas, circuit breakers, or degraded modes B. Turning off all evidence collection C. Publishing private secrets D. Removing all ownership

8. What should happen after a DDoS event is recovered? A. Delete the timeline and forget the incident B. Review evidence, improve runbooks, tune controls, and update architecture C. Disable provider contacts D. Remove all monitoring