Google Professional Cloud Database Engineer Question 40
Select 3Google Cloud PlatformYour team is managing a Cloud SQL instance running PostgreSQL, and you need to plan a version upgrade to ensure compliance with security policies. The upgrade requires minimal downtime and rollback capabilities in the event of an issue. Which steps should you take to properly plan and execute the upgrade?
- A
Test the upgrade process on a clone of the database instance in a non-production environment.
- B
Schedule the upgrade during peak traffic hours to verify production resilience.
- C
Create a backup of the database instance before initiating the upgrade.
- D
Review the Cloud SQL release notes for the target version to identify breaking changes or deprecations.
- E
Directly upgrade the production instance without testing since Cloud SQL handles compatibility automatically.
Show answer and explanation
Correct answers: A, C, D
Explanation
Properly planning a database upgrade involves thoroughly testing the upgrade process, reviewing documentation for potential impacts, and creating backups to ensure minimal disruption and rollback capabilities. Testing in a non-production environment and reviewing release notes help identify and mitigate risks, while creating backups ensures you can recover if issues arise. Upgrading directly in production or during peak hours increases the risk of downtime and is not a best practice.
- A. Correct.
Testing the upgrade on a clone in a non-production environment ensures that you can identify and address potential issues without impacting production workloads. This is a critical step in the upgrade process.
- B. Incorrect.
Scheduling the upgrade during peak traffic hours is not recommended as it increases the risk of user impact and complicates rollback efforts in case of failure.
- C. Correct.
Creating a backup before the upgrade provides a safety net to restore the database to its previous state in case of issues during or after the upgrade.
- D. Correct.
Reviewing the release notes is essential to understand the new features, breaking changes, or deprecations in the target version, enabling proper planning and adjustments.
- E. Incorrect.
Directly upgrading the production instance without testing is risky, as it assumes compatibility without verification, which can lead to unexpected failures or downtime.