Your organization operates a mission-critical Cloud SQL for MySQL database instance supporting an enterprise order-processing application. During an operational readiness review, the team identifies two operational requirements: the database must support Point-in-Time Recovery (PITR) without risking disk space exhaustion from unmanaged logs, and system maintenance reboots must be restricted to weekend off-peak hours rather than occurring at default provider times. Which TWO configuration actions should you perform on the Cloud SQL instance to satisfy these requirements?
- Enable binary logging on the Cloud SQL instance and configure an automated binary log retention period to manage storage consumption.Answer
- Configure a customized maintenance window in the instance settings specifying the preferred day of the week and time range for updates.Answer
- CMigrate the order-processing transactional data to Cloud Bigtable to obtain automatic native point-in-time recovery and relational query support.
- DAttach a Cloud Storage Object Lifecycle Management policy directly to the instance persistent disk to transition binary logs to Nearline storage after 30 days.
Answer
The two correct actions are enabling binary logging with log retention management to support Point-in-Time Recovery safely, and defining a maintenance window to restrict automated updates to designated off-peak hours.
Enabling binary logging on Cloud SQL for MySQL is mandatory for Point-in-Time Recovery (PITR), and establishing a log retention policy prevents storage exhaustion. Setting a maintenance window guarantees that routine maintenance reboots take place during administrative off-peak windows.
Step-by-Step Solution
Key Concept
Cloud SQL Operations: Binary Logging, Log Retention, and Maintenance Scheduling