DVA-C02 Troubleshooting and Optimization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Migrate the database to Amazon DynamoDB for better performance.

  Why it's wrong here

  Migrating a relational database to Amazon DynamoDB is a significant architectural change, requiring extensive refactoring of application code and data models. This option is premature because the root cause of the performance issue has not been identified; the problem might not even stem from the database type itself. Undertaking such a large-scale migration without proper diagnosis is costly, time-consuming, and may not resolve the actual performance bottleneck.

• ✓

  Enable enhanced health reporting and monitor CloudWatch metrics for database connection time.

  Why this is correct

  Elastic Beanstalk's enhanced health reporting provides detailed system and application metrics, including crucial database connection statistics, directly to Amazon CloudWatch. Monitoring "database connection time" specifically allows for direct diagnosis of latency issues between the application instances and the database. This approach provides actionable data to pinpoint whether the database itself, network latency, or application-level connection pooling is the bottleneck, enabling targeted resolution.

• ✗

  Add database indexing to improve query performance.

  Why it's wrong here

  While database indexing can significantly improve the performance of specific queries, it is a targeted optimization that should only be applied after identifying the exact slow queries. Indiscriminately adding indexes can consume additional storage, slow down write operations, and may not address the actual performance bottleneck if the issue is, for example, high database connection latency or inefficient application code. Diagnosis of specific query patterns is a prerequisite for effective indexing.

• ✗

  Increase the instance size to improve performance.

  Why it's wrong here

  Increasing the instance size (scaling up) for the Elastic Beanstalk environment primarily provides more CPU, memory, and network bandwidth to the application servers. This approach treats the symptom by throwing more resources at the problem without identifying the root cause. If the bottleneck is database latency, inefficient queries, or external service calls, larger application instances will not resolve the underlying issue and will only lead to increased operational costs without a proportional performance gain.

Go deeper

Related to this question