A company is using an Amazon CloudWatch alarm to monitor the FreeLocalStorage metric for an Amazon Aurora PostgreSQL production database. The alarm goes into ALARM state and indicates that the…

Question

Options

• ATurn on Aurora PostgreSQL query plan management.
• BModify the configuration of the DB cluster to turn on storage auto scaling.
• CAdd an Aurora read replica to the DB cluster. Modify the report to use the new read replica.
• DModify the DB instance class for each DB instance in the DB cluster to increase the instance size.

• A
  17% (3)
• B
  72% (13)
• C
  6% (1)
• D
  6% (1)

Explanation

Option B is correct because enabling storage auto scaling on the Aurora DB cluster allows Aurora to automatically expand storage capacity when it detects low availability - directly addressing the FreeLocalStorage alarm triggered by the resource-intensive weekly report without requiring manual resizing.

Option A is wrong because Aurora PostgreSQL query plan management optimizes execution plans for performance and stability, but it does not allocate or increase temporary storage capacity.

Option C is wrong because a read replica would have the same instance class and the same storage constraints; the report would simply exhaust the replica's local storage instead, not solving the underlying problem.

Option D is wrong because upgrading the DB instance class is a valid but manual, costly, and reactive approach - it requires downtime or a maintenance window and doesn't automatically adapt to future workload spikes the way auto scaling does.

Memory tip: When a CloudWatch alarm fires because something is running low automatically, the fix is usually to automate the scaling - "alarm fires automatically → fix it automatically with auto scaling."

No community discussion yet for this question.