Google Professional Cloud Network Engineer Question 403
Single answerGoogle Cloud PlatformYou are configuring a Global HTTP(S) Load Balancer for an application hosted on Google Cloud. The application has two backend instances in different regions that handle traffic. You want to configure the load balancer to distribute traffic based on backend CPU utilization to ensure optimal performance. Which configuration step is required to achieve this?
- A
Set the balancing mode of the backend service to 'UTILIZATION' and configure a target CPU utilization.
- B
Set the balancing mode of the backend service to 'RATE' and specify a maximum requests-per-second (RPS) value.
- C
Set the backend service balancing mode to 'CONNECTION' and configure a maximum number of connections per instance.
- D
Configure a session affinity policy to ensure requests from a single user are directed to the same instance.
Show answer and explanation
Correct answer: A
Explanation
To distribute traffic based on backend CPU utilization, the balancing mode of the backend service needs to be set to 'UTILIZATION'. This mode enables the load balancer to direct traffic to instances with lower CPU usage, ensuring optimal resource utilization and performance. Other options, such as 'RATE' or 'CONNECTION', distribute traffic based on different metrics and are not suitable for this scenario.
- A. Correct.
Correct. The 'UTILIZATION' balancing mode allows traffic distribution based on CPU utilization, which meets the requirement of distributing traffic based on backend CPU usage.
- B. Incorrect.
Incorrect. The 'RATE' balancing mode distributes traffic based on requests-per-second (RPS), which does not fulfill the requirement to balance based on CPU utilization.
- C. Incorrect.
Incorrect. The 'CONNECTION' balancing mode distributes traffic based on the maximum number of connections per backend instance, not CPU utilization.
- D. Incorrect.
Incorrect. Session affinity ensures that requests from the same user are sent to the same backend instance but does not address traffic distribution based on CPU utilization.