Implementing DevOps Solutions and Practices Using Cisco Platforms (DEVOPS) — Question 87

A DevOps engineer is supporting a containerized application with multiple components running across the Kubernetes cluster. Metrics from the container (CPU and memory) and application (requests per second and heap size) are being collected by Prometheus and displayed with Grafana. Users report transaction timeout problems with the application, but the metric graphs all look within normal levels.
Which type of failure would prevent the engineer from seeing the problem using the captured metrics?

Answer options

• A. Grafana has lost connectivity to Prometheus, which causes graphs to display only the cached data.
• B. CPU and memory metrics from Kubernetes nodes are not accurate due to the way that containers share resources.
• C. Some containers are crashing regularly and being restarted automatically by Kubernetes.
• D. The metricbeat agent has crashed and is no longer sending new data to Prometheus, so the metrics are not updating.

Correct answer: D

Explanation

The correct answer is D because if the metricbeat agent has crashed, new data won't be sent to Prometheus, preventing any updates to the metrics displayed in Grafana. While A, B, and C may present issues, they would not specifically stop the metrics from being updated, leading to a false sense of normalcy in the graphs.