Courseiva

Google PCA Practice Question: Analyze and optimize technical and business processes

A healthcare company runs a critical patient portal on Compute Engine. The portal uses a Cloud SQL for PostgreSQL database. The company needs to perform a major version upgrade of the database with minimal downtime and wants to minimize the risk of data loss. They also want to be able to roll back quickly if issues arise. Which approach should they take?

⚠ Common exam trap

The trap here is assuming that in-place major version upgrades are always safe and reversible, when they can cause downtime and are not easily rolled back.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use Database Migration Service to migrate to a new Cloud SQL instance with the desired major version, then switch over.

Database Migration Service enables a minimal-downtime migration to a new Cloud SQL instance with the desired major version. It continuously replicates data, so the cutover is quick and the original instance remains available for rollback. This approach minimizes data loss risk and downtime, unlike in-place upgrades or export/import.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Use Cloud SQL's in-place major version upgrade feature during a maintenance window, and rely on automated backups for rollback.

    Why it's wrong here

    In-place major version upgrades can cause downtime and are not easily reversible. While automated backups exist, restoring them may take time and may not be point-in-time consistent for the upgrade. This approach does not minimize downtime or provide a quick rollback, so it is not the best choice.

  • ✗

    Export the database to a Cloud Storage bucket, create a new instance with the new version, and import the data.

    Why it's wrong here

    Exporting and importing causes significant downtime and potential data loss because changes made after the export are not captured. It also does not provide a quick rollback. This method is not suitable for a critical portal that requires minimal downtime.

  • ✗

    Create a read replica, promote it to primary, and then upgrade the original instance.

    Why it's wrong here

    Promoting a read replica does not upgrade the database version; it only changes the replication role. The original instance would still need upgrading, and this process does not provide a rollback path. This approach does not address the major version upgrade requirement.

  • ✓

    Use Database Migration Service to migrate to a new Cloud SQL instance with the desired major version, then switch over.

    Why this is correct

    Database Migration Service (DMS) can perform a minimal-downtime migration to a new Cloud SQL instance with a different major version. It continuously replicates data, allowing a quick cutover and keeping the original instance intact for rollback if needed. This meets the requirements for minimal downtime, low data loss risk, and quick rollback.

About these practice questions

One of 807 original PCA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Google Cloud exam blueprint

This PCA practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCA exam.