Your team manages a Cloud SQL for MySQL instance used by a critical application. You need to ensure the instance is recoverable to any point within the last 4 days, with a Recovery Point Objective (RPO) of under 5 minutes. What configuration steps are required?
Trap 1: Enable automated backups and set the backup retention to 4 days
Automated backups alone only provide recovery to the time of backup, not point-in-time. Binary logging is required for PITR.
Trap 2: Enable binary logging and set the binary log retention to 4 days
Automated backups are required as a baseline; binary logs alone cannot restore without a base backup.
Trap 3: Create an on-demand backup daily and set binary log retention to 4…
On-demand backups are not incremental and do not integrate with binary logging for continuous recovery.
- A
Enable automated backups and set the backup retention to 4 days. Binary logging is not required because automated backups already capture all changes.
Why wrong: Automated backups alone only provide recovery to the time of backup, not point-in-time. Binary logging is required for PITR.
- B
Enable binary logging and set the binary log retention to 4 days. Automated backups are optional and not needed for PITR.
Why wrong: Automated backups are required as a baseline; binary logs alone cannot restore without a base backup.
- C
Create an on-demand backup daily and set binary log retention to 4 days. This provides the same RPO as automated backups with binary logging.
Why wrong: On-demand backups are not incremental and do not integrate with binary logging for continuous recovery.
- D
Enable automated backups and binary logging. Set the transaction log retention period to 4 days.
Automated backups plus binary logging (with appropriate retention) enables PITR with a 4-day window.