AWS Certified CloudOps Engineer Associate SOA-C03 Practice Question

Restoring the most recent automated snapshot into a single-AZ instance that uses a smaller, burstable class (for example, db.t3.large) creates an independent, writable environment at the lowest possible compute cost. Snapshot storage is already paid for, so the company is charged only for the temporary instance while it is running. Choosing single-AZ avoids the extra standby charges of a Multi-AZ deployment, and using a smaller class further reduces hourly costs. Creating and promoting a read replica is a more complex workflow and is less cost-effective for a short-lived, independent test database than a direct snapshot restore. A point-in-time restore to the original, larger class in Multi-AZ would be significantly more expensive. Maintaining a continuously replicated target through AWS Database Migration Service requires running a target instance at all times, which is the most expensive option.