DOP-C02 Practice Question 98: Container Insights ECS Task Metrics
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 10 · question 8 of 10
An operations team runs several services on Amazon ECS on Fargate. They currently have no visibility into per-task CPU and memory utilization, and cannot tell which service in a cluster is approaching its reserved memory limit without SSH-like access to a container, which Fargate does not provide anyway. They want aggregated dashboards at the cluster, service, and task level built from CloudWatch metrics, with minimal setup.
Which feature should they enable?
Show answer and explanation
Answer:
Container Insights collects and aggregates CloudWatch metrics and logs from containerized applications, and it supports ECS, including Fargate launch type tasks, at the cluster, service, and task level. Enabling it on an ECS cluster requires no code changes to the application, only turning the setting on for the cluster (or the account default), and it produces prebuilt CloudWatch dashboards showing CPU, memory, network, and storage metrics broken down by service and task.
Option A misapplies X-Ray, which traces requests through a distributed application to analyze latency and errors along a call chain; it is not a source of aggregated CPU and memory utilization metrics.
Option C captures network flow metadata (source, destination, ports, and bytes) for network interfaces, which says nothing about a task's CPU or memory consumption.
Option D tracks configuration changes to ECS resources over time for compliance and drift purposes; it records what a task definition looks like, not how much CPU or memory a running task is consuming.
Reference: Using Container Insights