Kubernetes and Cloud Native Associate (KCNA)Cloud Native ObservabilityHard
An infrastructure team needs to ensure that their critical Kubernetes services remain operational even if a single data center fails. They have deployed their applications across multiple geographically dispersed clusters. Which monitoring strategy is essential to provide a unified view of the application's health across all clusters and automatically trigger failover mechanisms when a regional outage occurs?
- ASingle-cluster Prometheus deployments
- BRegional logging aggregation
- CGlobal active/active monitoring with federated metrics
- DManual health checks via `kubectl`
Show answer & explanationAnswer & explanation
Correct answer: C. Global active/active monitoring with federated metrics
Global active/active monitoring with federated metrics (e.g., using Thanos or Cortex) is crucial for geographically dispersed clusters. It provides a unified, real-time view of application health across all regions, enabling automatic detection of regional outages and triggering of failover mechanisms to maintain high availability.
Why the other options are wrong
- A. Single-cluster deployments would not provide a unified view or detect cross-region issues.
- B. Regional logging aggregation helps with troubleshooting but doesn't provide a real-time, unified health view for automatic failover.
- D. Manual health checks are not scalable or automated for critical, real-time failover scenarios.
Federated Metrics (Global Monitoring)
A monitoring strategy where metrics from multiple independent monitoring systems (e.g., Prometheus instances) are aggregated into a central system to provide a unified, global view of infrastructure and application health.
- Essential for multi-cluster or multi-region deployments.
- Enables global dashboards and alerts.
- Often implemented using solutions like Thanos or Cortex for Prometheus.
Memory trick: Federated Metrics give you a Full, Global view.