PROFESSIONAL-CLOUD-NETWORK-ENGINEER Question #248: Real Exam Question with Answer & Explanation

Question

You recently reviewed the user behavior for your main application, which uses an external global Application Load Balancer, and found that the backend servers were overloaded due to erratic spikes in the rate of client requests. You need to limit the concurrent sessions and return an HTTP 429 Too Many Requests response back to the client while following Google-recommended practices. What should you do?

Options

• ACreate a Cloud Armor security policy, and associate the policy with the load balancer. Configure
• BConfigure the load balancer to accept only the defined amount of requests per client IP address,
• CCreate a Cloud Armor security policy, and apply the predefined Open Worldwide Security
• DConfigure a VM with Linux, implement the rate limit through iptables, and use a firewall rule to

Explanation

Using Google Cloud Armor, you can create a security policy to implement rate limiting on an external global Application Load Balancer. This is a Google-recommended practice for handling erratic spikes in traffic and limiting concurrent sessions to prevent backend server overload. Cloud Armor rate limiting: - The action: throttle setting enables rate limiting based on client behavior, such as the number of requests from a specific IP address. - The exceed action: deny-429 returns an HTTP 429 (Too Many Requests) response to clients exceeding the configured rate, signaling them to reduce their request rate. - This approach ensures the backend servers are protected from being overloaded while providing proper feedback to clients.

No community discussion yet for this question.