A company's ecommerce application stores order transactions in an Amazon RDS for MySQL database. The database has run out of available storage and the application is currently unable to take orders. W

Question

Options

• AAdd more storage space to the DB instance using the ModifyDBInstance action.
• BCreate a new DB instance with more storage space from the latest backup.
• CChange the DB instance status from STORAGE_FULL to AVAILABLE.
• DConfigure a read replica with more storage space.

• A
  94% (30)
• C
  3% (1)
• D
  3% (1)

Explanation

Explanation

Modifying the DB instance directly using ModifyDBInstance is the fastest resolution because it allows you to increase storage on the existing running instance without recreating it or waiting for a full backup restore - Amazon RDS also supports autoscaling storage, making this a near-seamless operation. Option B is incorrect because restoring from a backup to a new DB instance is time-consuming and introduces downtime, making it far from the "shortest amount of time" solution. Option C is a distractor because STORAGE_FULL is a read-only status flag set by AWS - you cannot simply change it manually; you must resolve the underlying storage issue. Option D is incorrect because read replicas are used for read scaling, not for resolving storage issues on the primary instance, and adding a replica doesn't fix the primary's storage problem.

Memory Tip: Think "Modify first, migrate last" - whenever an RDS issue involves a configuration change (storage, instance type, parameter groups), always check if ModifyDBInstance can solve it in place before considering rebuilding from a backup.

No community discussion yet for this question.