A company just migrated to Amazon Aurora PostgreSQL from an on-premises Oracle database. After the migration, the company discovered there is a period of time every day around 3:00 PM where the…

Question

Options

• ACreate an Amazon CloudWatch dashboard to show the number of connections, CPU usage, and
• BLaunch an Amazon EC2 instance, and install and configure an open-source PostgreSQL
• CModify the logging database parameter to log all the queries related to locking in the database
• DEnable Amazon RDS Performance Insights on the PostgreSQL database. Use the metrics to

• A
  16% (9)
• B
  9% (5)
• C
  5% (3)
• D
  71% (41)

Explanation

Explanation

Amazon RDS Performance Insights is purpose-built for exactly this scenario - it provides a visual dashboard that shows database load over time, allowing you to drill down to identify the specific queries, wait events, or users causing performance degradation at a particular time (3:00 PM in this case), making it the most efficient solution with minimal setup overhead.

Option A is wrong because CloudWatch provides infrastructure-level metrics (CPU, connections) but lacks the query-level granularity needed to pinpoint the specific problematic SQL statement causing the slowdown.

Option B is wrong because installing and configuring a third-party tool on an EC2 instance is unnecessarily complex and time-consuming - it violates the "most efficiently" requirement in the question.

Option C is wrong because enabling lock-related logging only captures locking events, which is a narrow assumption about the root cause; the actual issue could be an inefficient query, not necessarily a locking problem.

Memory Tip: Think of Performance Insights as a "DVR for your database" - it records database load history so you can rewind to exactly 3:00 PM and see which queries were the culprits. Whenever an exam question asks about identifying slow queries efficiently on RDS/Aurora, Performance Insights is almost always the answer.

No community discussion yet for this question.