Back to AWS Elastic Beanstalk

Troubleshooting and Debugging

5 minutes 5 Questions

Troubleshooting and debugging are critical processes in AWS Elastic Beanstalk, which helps in identifying and resolving issues in your application or infrastructure. Elastic Beanstalk provides various tools and features to aid in troubleshooting, including logs, monitoring dashboards, health report…

Test mode:
Start practice test
AWS Certified Solutions Architect - Troubleshooting and Debugging Example Questions

Test your knowledge of Troubleshooting and Debugging

Question 1

A company runs a public website on an Amazon EC2 instance behind an Application Load Balancer. Users report intermittent high latency during peak hours. The team wants to diagnose the root cause using AWS-native tooling before making any architectural changes. What is the most effective approach?

Correct Answer: Enable detailed monitoring and review EC2/ALB CloudWatch metrics; collect and analyze application and web server logs in CloudWatch Logs; optionally use AWS X-Ray to trace requests end to end.

Intermittent high latency is best diagnosed by correlating infrastructure and application telemetry. Enabling detailed monitoring provides 1-minute EC2 metrics such as CPU, network, and status checks, while ALB metrics like TargetResponseTime, 5XX errors, and RequestCount help identify load or backend issues. Centralizing application and web server logs in CloudWatch Logs (and querying with Logs Insights) lets you pinpoint slow endpoints and errors during the affected time windows. AWS X-Ray can trace requests across services to isolate where latency accumulates (e.g., application code, external calls, or database queries). In contrast, creating an RDS instance, running Glue ETL jobs, or enabling S3 versioning do not diagnose latency on an EC2-hosted website.

Question 2

An Amazon RDS instance is experiencing high query latency as the number of client connections increases. The team needs an AWS-native feature to quickly identify bottlenecks such as wait events, top SQL, and active sessions in order to remediate the issue. Which option should they use first?

Correct Answer: Enable Amazon RDS Performance Insights to analyze and optimize the database's performance

Amazon RDS Performance Insights provides database-level visibility into load (DBLoad), active sessions, wait events, and top SQL, allowing teams to quickly pinpoint whether high latency under increasing connections is due to CPU, I/O, locks, inefficient queries, or connection contention. It is the most effective AWS-native feature to use first for diagnosing query latency. Enhanced Monitoring focuses on OS-level metrics and cannot show SQL or wait-event analysis. Restarting the instance does not resolve the underlying cause and introduces downtime. Creating a read replica and using it as a primary is incorrect for diagnosis and does not inherently address latency analysis.

Question 3

An application hosted on an EC2 instance is encountering HTTP 503 errors. What approach should be taken to identify and resolve the issue?

Correct Answer: Check the application and web server logs for any errors and review load balancer settings

HTTP 503 errors indicate that the service is unavailable. Check the application and web server logs for any errors and review the settings of the load balancer that distributes traffic to the instances.

More Troubleshooting and Debugging questions
15 questions (total)
Start 15 question test