Q: 5
You want to migrate an on-premises mission-critical PostgreSQL database to Cloud SQL. The database
must be able to withstand a zonal failure with less than five minutes of downtime and still not lose
any transactions. You want to follow Google-recommended practices for the migration. What should
you do?
Options
Discussion
D pretty sure. HA makes the instance regional so zonal failures are handled, matches the RTO requirement.
D. but notice that if this was about cross-region resiliency (not just zonal), you'd have to go deeper than HA alone. For zonal failure and <5m downtime though, HA covers it per Google docs.
D , enabling HA makes the database regional in Cloud SQL so you get failover if a whole zone goes down. That matches the <5 min RTO requirement and transaction safety. Other options miss the point for zonal failures, I think.
Not sure why you'd pick B here, even though CDC sounds cool. For less than 5 min downtime and no lost transactions on zonal failure, D is Google's recommended HA approach. Think B is a trap for DIY folks.
Lots of practice tests highlight D as the way to handle zonal failure in Cloud SQL. Official docs confirm it too. D
Hard to say, D since enabling HA in Cloud SQL makes the database regional, which covers zonal failure and meets the <5 min downtime. The other options don't guarantee seamless failover or transaction safety under a full zone outage. Pretty sure that's what Google expects for this scenario, but open to other takes if anyone disagrees.
C vs D, but C looks tempting for cross-region but misses the zonal failover with sub-5min RTO part.
Probably D here, that's the only choice with regional HA built in for Cloud SQL.
D here. Enabling HA makes the Cloud SQL instance regional, so a zonal failure triggers quick failover and no transaction loss. Pretty sure that's what Google recommends for under 5 minutes downtime.
B
I'm leaning toward B because a CDC pipeline lets you continuously replicate transactions, which should help minimize downtime and avoid losing changes. Nightly snapshots (A) seem riskier, but with CDC you capture all activity in near real time. Not 100% sure if this is the official way Google recommends though. Disagree?
I'm leaning toward B because a CDC pipeline lets you continuously replicate transactions, which should help minimize downtime and avoid losing changes. Nightly snapshots (A) seem riskier, but with CDC you capture all activity in near real time. Not 100% sure if this is the official way Google recommends though. Disagree?
Be respectful. No spam.
