Explanation:
To prevent future disruptions due to maintenance events in a Cloud SQL instance, the most effective immediate actions would be to set the maintenance window to non-business hours (Option A) to minimize impact on the production application during peak usage times. Additionally, migrating to Cloud Spanner (Option B) could be considered for long-term resilience as it is designed for high availability and global consistency, reducing the likelihood of maintenance-related downtimes. Contacting Support (Option C) may provide insights but does not prevent future issues. Using Cloud Scheduler (Option D) is not a viable solution as maintenance windows are not directly controllable via scheduling in this manner.
Ultimate access to all questions.
How can you promptly resolve the maintenance issue with your Cloud SQL instance that caused over 5 minutes of downtime during a critical launch, impacting your production meeting booking application, to avoid future unplanned disruptions?
A
Set your production instance's maintenance window to non-business hours.
B
Migrate the Cloud SQL instance to Cloud Spanner to avoid any future disruptions due to maintenance.
C
Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
D
Use Cloud Scheduler to schedule a maintenance window of no longer than 5 minutes.
No comments yet.