Q: 1
Your application is deployed as a highly available cross-region solution behind a global external
HTTP(S) load balancer. You notice significant spikes in traffic from multiple IP addresses but it is
unknown whether the IPs are malicious. You are concerned about your application's availability. You
want to limit traffic from these clients over a specified time interval.
What should you do?
Options
Discussion
C/D? Firewall rule trap, but throttle with Cloud Armor (C) fits rate-limiting over time for each IP.
Guessing A this time. Cloud Armor's rate_based_ban directly blocks clients for a set interval if they go over the limit, which sounds stronger than just throttling. Not totally sure but that's how I read it.
Pretty sure C is the way to go here. Throttle with Cloud Armor seems like it’d limit requests per client, which fits if you want to reduce spikes over a time window. Not 100% though since I'm not sure if it's as aggressive as a ban. Agree or am I missing something?
Be respectful. No spam.