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…

Question

Options

• AConfigure a throttle action by using Google Cloud Armor to limit the number of requests per client
• BConfigure a rate_based_ban action by using Google Cloud Armor and set the ban_duration_sec
• CConfigure a firewall rule in your VPC to throttle traffic from the identified IP addresses.
• DConfigure a deny action by using Google Cloud Armor to deny the clients that issued too many

• A
  73% (46)
• B
  8% (5)
• C
  3% (2)
• D
  16% (10)

Explanation

The throttle action in Google Cloud Armor rate-limits requests from a client - allowing traffic to continue but capping it at a configured threshold over a time window. This is the right choice when the malicious nature of the traffic is uncertain, because it reduces the blast radius of a potential attack without completely cutting off potentially legitimate users. Option B (rate_based_ban) temporarily bans clients after they exceed a threshold, which is more aggressive and appropriate when malicious intent is confirmed. Option C (VPC firewall rules) cannot perform rate limiting - they are binary allow/deny. Option D (deny action) permanently blocks clients, which is inappropriate when the traffic's legitimacy is unknown.

No community discussion yet for this question.