2V0-71.23 Question 322
Single answerYour organization is using VMware Tanzu Kubernetes Grid (TKG) on a vSphere environment with NSX Advanced Load Balancer (ALB) to manage ingress traffic for your Kubernetes clusters. During a recent deployment, you noticed latency and uneven traffic distribution for workloads behind the load balancer. Which configuration should you investigate first to resolve this issue?
- A
Ensure the NSX ALB Service Engine placement is optimized across multiple ESXi hosts.
- B
Verify that the NSX ALB is using the Round Robin load balancing algorithm.
- C
Check if the NSX ALB's health monitors are properly configured for the backend services.
- D
Increase the memory and CPU allocation for all Service Engines.
Show answer and explanation
Correct answer: C
Explanation
When using NSX Advanced Load Balancer with Tanzu Kubernetes Grid, health monitors are crucial for ensuring that only healthy backend services receive traffic. If the health monitors are not properly configured, the load balancer may direct traffic to unhealthy or degraded services, causing latency and uneven distribution. Verifying health monitor configuration is the most relevant step in this scenario.
- A. Incorrect.
While Service Engine placement can impact availability, it is unlikely to directly cause latency or uneven traffic distribution unless there is a host failure or resource contention.
- B. Incorrect.
Round Robin is one of the load balancing algorithms, but it does not guarantee even traffic distribution or low latency in all scenarios. The issue may lie with backend health or connectivity.
- C. Correct.
Improperly configured health monitors can result in uneven traffic distribution or latency because unhealthy backend services may still receive traffic, or healthy services may be incorrectly marked as unavailable.
- D. Incorrect.
Increasing memory and CPU allocation for Service Engines could be beneficial for high throughput workloads, but it is not the first step to troubleshoot uneven traffic distribution or latency.