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.
A multinational financial services company is redesigning its core transaction processing backend on Google Cloud. The architecture must accommodate rapid international expansion and satisfy the following technical requirements:
Which Google Cloud database service should the architect select to meet these requirements?
AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible relational database service designed for demanding enterprise transactional and analytical workloads, featuring a disaggregated compute and storage architecture.
The application required full PostgreSQL compatibility with high vertical transactional throughput and scalable intra-region read performance, without requiring multi-region active-active horizontal write scaling.
Cloud Spanner is Google Cloud's fully managed, mission-critical, enterprise-grade relational database service. It uniquely combines the benefits of traditional relational database structure—such as ACID transactions, relational schemas, and SQL support—with the horizontal scalability and high availability typically found only in non-relational distributed databases.

Compared to single-master relational engines like Cloud SQL or AlloyDB, which rely on vertical compute scaling and asynchronous read replicas, Cloud Spanner is the only Google Cloud relational engine architected to scale write workloads horizontally across multiple global regions while maintaining strict transactional consistency.
Cloud SQL is a fully managed relational database service supporting MySQL, PostgreSQL, and SQL Server. It is designed for standard enterprise workloads requiring managed relational functionality, automatic backups, and high availability within regional boundaries.
The workload were confined to a single geographic region, possessed read-heavy access patterns that could be offloaded to read replicas, and had write volumes that fit within a vertically scaled database instance.
Cloud Bigtable is a sparsely populated, distributed NoSQL wide-column store designed for high-throughput, low-latency analytical and operational workloads at petabyte scale.
The application required massive ingestion of unstructured or semi-structured time-series/sensor data with sub-10ms read/write latencies and did not require relational queries or multi-row transactional integrity.
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