Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud Network Engineer · Google Cloud
Select 2 answers.
This question asks for 2 answers, but our data marks only 1. Compare with the community discussion below for the full answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
C. Create a global HTTP(s) load balancer and move your application backend to this load balancer: This step is crucial because Application Load Balancers (HTTP(S)) are designed for web traffic (Layer 7) and integrate fully with Google Cloud Armor. The existing Network Load Balancer (typically Layer 4 passthrough) has limited integration capabilities for application-level attack mitigation policies like IP blacklisting provided by standard Cloud Armor tiers. Migrating to an Application Load Balancer provides the necessary foundation for effective DDoS protection. A. Use Cloud Armor to blacklist the attacker's IP addresses: Once the application is behind a compatible load balancer (like the HTTP(S) Load Balancer from step C)
Why Not the Other Options? ❌ B. Increase the maximum autoscaling backend Scaling up indefinitely does not stop the attack, and it increases costs dramatically. Without blocking the malicious traffic, your instances will continue getting overwhelmed. ❌ D. Shut down the entire application This is not a viable solution—taking down your application means legitimate users also lose access. The attacker could simply restart the attack when you go back online. ❌ E. SSH into backend instances to analyze logs Too slow for immediate mitigation. While log analysis is useful after the attack, it doesn’t help quickly restore service for real users.
A and C are correct