2V0-71.23 Question 304
Select 3Your organization is using VMware Aria Operations for Applications (formerly known as Tanzu Observability) to monitor a Kubernetes-based application. The application team has reported intermittent latency issues in a specific microservice. Which of the following steps should you take within Aria Operations for Applications to identify the root cause of the latency?
- A
Analyze trace data for the affected microservice to identify slow spans or bottlenecks.
- B
Enable synthetic monitoring to simulate traffic to the affected microservice and measure response times.
- C
Review Kubernetes node metrics, such as CPU and memory utilization, for the nodes hosting the affected microservice.
- D
Use the Alerting feature to configure a new alert for latency thresholds on the affected microservice.
- E
Examine the network topology map to identify potential network-related issues impacting the microservice.
Show answer and explanation
Correct answers: A, C, E
Explanation
To diagnose the root cause of intermittent latency in a microservice using Aria Operations for Applications, you should combine trace analysis (to pinpoint application-level problems), Kubernetes node metrics (to identify resource constraints), and network topology insights (to detect network-related issues). These three approaches provide a comprehensive view of potential causes for the reported latency.
- A. Correct.
Analyzing trace data is crucial for identifying slow spans, bottlenecks, or errors within the microservice's code or dependencies.
- B. Incorrect.
While synthetic monitoring is useful for proactive testing, it does not directly help identify the root cause of existing latency issues.
- C. Correct.
Reviewing Kubernetes node metrics can help determine if resource constraints, such as CPU or memory exhaustion, are causing latency in the microservice.
- D. Incorrect.
Configuring a new alert can help monitor future latency issues but does not address the current problem or identify its root cause.
- E. Correct.
Examining the network topology map can reveal network-related problems, such as high latency or dropped packets, that could be affecting the microservice.