nerdexam
Amazon

DOP-C02 · Question #476

A DevOps engineer is supporting early-stage development for a developer platform that runs on Amazon Elastic Kubernetes Service (Amazon EKS). Recently, the platform has experienced an increased rate…

The correct answer is D. Configure Amazon CloudWatch Container Insights for the EKS cluster by enabling the. To diagnose increased container restart failures in Amazon EKS, configure Amazon CloudWatch Container Insights to collect and analyze granular performance and diagnostic data from the cluster.

Submitted by yaw92· Mar 6, 2026Monitoring and Logging

Question

A DevOps engineer is supporting early-stage development for a developer platform that runs on Amazon Elastic Kubernetes Service (Amazon EKS). Recently, the platform has experienced an increased rate of container restart failures. The DevOps engineer wants to implement a solution that can provide diagnostic information to help isolate issues and resolve them. Which solution will meet this requirement?

Options

  • AConfigure Amazon CloudWatch dashboards for the EKS cluster by using the default EKS service
  • BConfigure AWS CloudTrail for the EKS cluster by enabling CloudTrail in the AWS account that the
  • CConfigure AWS CloudTrail Insights for the EKS cluster by enabling CloudTrail Insights on the trail
  • DConfigure Amazon CloudWatch Container Insights for the EKS cluster by enabling the

How the community answered

(56 responses)
  • A
    9% (5)
  • B
    2% (1)
  • C
    5% (3)
  • D
    84% (47)

Why each option

To diagnose increased container restart failures in Amazon EKS, configure Amazon CloudWatch Container Insights to collect and analyze granular performance and diagnostic data from the cluster.

AConfigure Amazon CloudWatch dashboards for the EKS cluster by using the default EKS service

While CloudWatch dashboards are useful, default EKS service metrics often provide high-level cluster health, lacking the detailed, container-level performance and diagnostic data needed to pinpoint the reasons for container restart failures.

BConfigure AWS CloudTrail for the EKS cluster by enabling CloudTrail in the AWS account that the

AWS CloudTrail logs API calls made to AWS services, primarily for auditing and security purposes, and does not provide runtime diagnostic information or performance metrics essential for troubleshooting container-level issues like restarts.

CConfigure AWS CloudTrail Insights for the EKS cluster by enabling CloudTrail Insights on the trail

AWS CloudTrail Insights detects unusual API activity patterns in CloudTrail logs, focusing on control plane anomalies rather than application-level performance or container runtime diagnostics relevant to container restart failures.

DConfigure Amazon CloudWatch Container Insights for the EKS cluster by enabling theCorrect

Amazon CloudWatch Container Insights is specifically designed for monitoring containerized applications and Amazon EKS clusters, automatically collecting metrics and logs related to CPU, memory, disk, network, and container restart counts. This granular diagnostic information is crucial for identifying the root causes of container restart failures and effectively troubleshooting issues within the platform.

Concept tested: EKS container monitoring and diagnostics

Source: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights.html

Topics

#Amazon EKS#CloudWatch Container Insights#Container Monitoring#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full DOP-C02 Practice