Answer: Configure Amazon CloudWatch Container Insights in the existing EKS cluster. View the metrics and logs in the CloudWatch console.

## Explanation **Correct Answer: D** - Configure Amazon CloudWatch Container Insights in the existing EKS cluster. View the metrics and logs in the CloudWatch console. **Why this is correct:** 1. **CloudWatch Container Insights** is specifically designed for containerized applications running on Amazon EKS, Amazon ECS, and Kubernetes platforms on EC2. 2. It automatically collects, aggregates, and summarizes metrics and logs from containerized applications and microservices. 3. It provides a centralized view in the CloudWatch console with pre-built dashboards for performance monitoring. 4. It supports both metrics (CPU, memory, disk, network) and logs collection from EKS clusters. 5. It's a managed service that requires minimal configuration compared to running agents manually. **Why other options are incorrect:** **A:** While the CloudWatch agent can collect metrics and logs, it requires manual configuration and doesn't provide the same level of container-specific aggregation and summarization as Container Insights. **B:** AWS App Mesh is a service mesh for microservices that provides traffic management and observability, but it's primarily for traffic control and doesn't provide comprehensive metrics and logs collection/aggregation like CloudWatch Container Insights. **C:** AWS CloudTrail is for auditing API calls and governance, not for collecting application metrics and logs from EKS clusters. It doesn't meet the requirements for collecting metrics and logs from microservices applications. **Key AWS Services:** - **Amazon CloudWatch Container Insights**: Specifically designed for container monitoring - **Amazon EKS**: Managed Kubernetes service - **Microservices architecture**: Container Insights provides the necessary observability for distributed systems

Author: LeetQuiz Editorial Team