Q30 — AWS SAA-C03 Ch.11

Question 30 of 100 | ← Chapter 11

Q730. A company runs a critical, customer-facing application on Amazon Elastic Kubernetes Service (Amazon EKS). The application has a microservices architecture. The company needs to implement a solution that collects, aggregates, and summarizes metrics and logs from the application in a centralized location.Which solution meets these requirements?

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

Explanation

To meet the requirement of collecting, aggregating, and summarizing metrics and logs from a customer-facing application running on Amazon Elastic Kubernetes Service (Amazon EKS) with a microservices architecture, the most suitable solution is:D. Configure Amazon CloudWatch Container Insights in the existing EKS cluster. View the metrics and logs in the CloudWatch console.Option D, configuring Amazon CloudWatch Container Insights in the existing EKS cluster and viewing the metrics and logs in the CloudWatch console, is the recommended solution to meet the requirements:- Amazon CloudWatch Container Insights: Container Insights is a monitoring and troubleshooting solution provided by CloudWatch specifically designed for containerized environments, including Amazon EKS. It collects and aggregates performance metrics and logs from containers, orchestrators, and underlying infrastructure.By configuring Container Insights in the EKS cluster, you can collect and centralize metrics and logs from the microservices application. Container Insights automatically retrieves metrics and logs from the Kubernetes control plane and the container runtime, providing a comprehensive view of the application's performance.You can then view and analyze the collected metrics and logs in the CloudWatch console, which offers various visualization and analysis capabilities. This allows you to gain insights into the application's behavior, troubleshoot issues, and monitor its performance in a centralized location.Option A, running the Amazon CloudWatch agent in the existing EKS cluster and viewing the metrics and logs in the CloudWatch console, is not the most appropriate solution for collecting metrics and logs from containers in an EKS environment. The CloudWatch agent is primarily used for collecting metrics and logs from EC2 instances, not containers.Option B, running AWS App Mesh in the existing EKS cluster and viewing the metrics and logs in the App Mesh console, is not the most suitable solution for collecting and aggregating metrics and logs. AWS App Mesh is a service mesh that provides observability, traffic management, and security features for microservices, but it does not offer the same level of metrics and logs aggregation capabilities as Container Insights.Option C, configuring AWS CloudTrail to capture data events and querying CloudTrail using Amazon OpenSearch Service, is not the recommended solution for collecting and aggregating metrics and logs from a containerized application. CloudTrail is primarily used for auditing and monitoring API activity, and it does not provide the necessary functionality for collecting and analyzing container metrics and logs.Therefore, the solution that best meets the requirements is D: Configure Amazon CloudWatch Container Insights in the existing EKS cluster and view the metrics and logs in the CloudWatch console. This solution provides comprehensive monitoring and analysis capabilities specifically designed for containerized environments, allowing you to collect, aggregate, and summarize metrics and logs from the customer-facing microservices application.