Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a highly resilient database architecture on Google Cloud for a mission-critical transactional service. The workload has the following architectural and reliability requirements:
Following the Google Cloud Well-Architected Framework for reliability, which database architecture should you implement?
This setup provisions standalone database instances without active streaming replication, depending entirely on scheduled storage snapshots and Write Ahead Log (WAL) archiving for point-in-time restoration across regions.
The database supported non-critical, batch-oriented workloads with flexible recovery objectives where minimizing infrastructure costs was prioritized over uptime and data loss.
This configuration relies on periodic Write Ahead Log (WAL) archiving via pgBackRest for local database redundancy while attempting cross-region synchronous streaming replication over long physical distances.
The workload permitted transactional data loss locally but required absolute cross-region consistency without regard for write latency or throughput.
This approach uses multi-region synchronous replication to enforce strict consistency across geographically separated cloud regions, paired with manual operational runbooks triggered by Cloud Monitoring alerts.
The organization had strict regulatory mandates forbidding any data loss even during regional destruction, possessed ultra-low-latency dedicated interconnects, and had operational policies prohibiting automated failover.
This architecture combines intra-region high availability (HA) using synchronous streaming replication with inter-region disaster recovery (DR) using asynchronous streaming replication. High availability is automated and coordinated using Patroni alongside a distributed consensus system such as etcd, Consul, or ZooKeeper.
Synchronous replication across distant geographic regions introduces substantial network round-trip latency that severely slows down transactional writes. By confining synchronous replication to local low-latency nodes and using asynchronous replication for cross-region disaster recovery, this solution balances stringent RPO/RTO requirements with optimal application performance.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated