Continuous Improvement for Existing Solutions I
Explore techniques to improve existing AWS solutions by detecting hidden failures in containerized applications, implementing low-risk deployment strategies, and enforcing centralized management. Understand how to automate remediation with approval controls and validate disaster recovery procedures through testing and monitoring. This lesson equips you to design more reliable, auditable, and maintainable cloud environments using AWS best practices.
We'll cover the following...
Question 42
A containerized checkout application runs on Amazon ECS behind an Application Load Balancer. Users intermittently report failed checkouts, but CPU, memory, and ALB target health metrics remain normal. The business wants to reduce MTTR and detect customer-impacting failures before support tickets arrive. Which THREE actions should a solutions architect recommend? Choose three.
A. Instrument the ECS services with AWS X-Ray or AWS Distro for OpenTelemetry, propagate trace context such as X-Amzn-Trace-Id, and capture downstream service latency.
B. Emit structured application logs with request IDs, customer-journey step names, and order correlation IDs. Use CloudWatch Logs Insights and CloudWatch metric filters to create alarms on business errors.
C. Create CloudWatch Synthetics canaries that run the critical checkout flow, and configure SLO-based CloudWatch alarms for failed or slow journeys.
D. Increase CloudWatch Logs retention to seven years and build dashboards that show CPU, memory, and ALB target health metrics.
E. Enable CloudTrail and VPC Flow Logs for the VPC, and then scale ECS tasks based only on ...