A company runs a microservices application on Amazon EKS. Users report delays accessing an account summary feature during peak hours. CloudWatch metrics and logs show normal CPU and memory utilization

Question

Options

• ADeploy the AWS X-Ray daemon as a DaemonSet in the EKS cluster. Use the X-Ray SDK to
• BEnable CloudWatch Container Insights for the EKS cluster. Use the Container Insights data to
• CCreate alarms based on existing CloudWatch metrics. Set up SNS email alerts.
• DIncrease the timeout settings in the application code for network operations.

• A
  84% (32)
• B
  3% (1)
• C
  5% (2)
• D
  8% (3)

Explanation

AWS X-Ray provides distributed tracing, which allows visualization of latencies and errors within microservices, pinpointing bottlenecks or delays. Instrumenting application code with the X-Ray SDK and running the X-Ray daemon as a DaemonSet in EKS ensures tracing data is collected cluster-wide. Container Insights (Option B) provides resource-level metrics but not detailed request tracing. CloudWatch alarms and alerts (Option C) detect symptoms but don't provide root cause tracing. Increasing timeouts (Option D) only masks the issue and does not diagnose it.

No community discussion yet for this question.