How can these requirements be met?
Enable Multi-AZ on the RDS instance to maintain the data in a second Availability Zone.
Create a read replica of the RDS instance to maintain the data in a second region.
Ensure that automated backups are enabled and set the appropriate retention period.
Enable versioning in RDS to recover altered table data when needed.
Explanations:
Multi-AZ provides high availability by replicating data in a different Availability Zone, but it does not protect against table corruption. The changes made to the primary instance, including any corruption, will be reflected in the secondary instance.
Creating a read replica in a second region only helps with disaster recovery and scaling. It does not provide protection against table corruption or a way to restore data within a 30-day window.
Enabling automated backups ensures that point-in-time recovery is possible. It provides a 30-day retention window, which allows recovery to a specific point before corruption occurred, fulfilling the requirement for a 30-day protection window.
RDS does not support versioning for tables. The only form of data versioning that exists in RDS is through backups or snapshots. Thus, this option would not help recover corrupted table data.
I classify that the answer is:
Ensure that automated backups are enabled and set the appropriate retention period.