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 planning its multi-year data architecture on Google Cloud to handle projected data growth across three critical business workloads:
Which combination of Google Cloud storage and database services best satisfies the scalability and architectural requirements of these workloads?
This architecture pairs Google Cloud's premier managed storage engines to their exact workload strengths: Cloud Spanner for globally scalable relational transactions, Cloud Bigtable for high-throughput NoSQL time-series data, and BigQuery for serverless, petabyte-scale analytical querying.
This combination aligns each workload with a purpose-built system designed to support exponential data growth while maintaining predictable latencies, high availability, and optimal cost-performance trade-offs.
Cloud Bigtable provides a distributed key-value NoSQL map. Cloud Storage external tables allow BigQuery to query data stored in raw object formats (like CSV, JSON, or Parquet) without loading it into managed native storage.
Workload 1 required a high-volume NoSQL document store, and Workload 3 required an ad hoc, low-frequency query capability over historical data lake archives without importing them into an active data warehouse.
BigQuery is an enterprise OLAP data warehouse engineered for complex SQL analytics over massive datasets. Cloud Bigtable is a low-latency NoSQL engine designed for operational key-value lookups and sequential scans.
Workload 2 was a batch reporting warehouse ingesting point-of-sale logs for daily executive reports, and Workload 3 was an operational backend serving real-time user-facing key-value profiles.
Cloud SQL is a managed relational database service supporting MySQL, PostgreSQL, and SQL Server. Cloud Spanner provides horizontally scalable, globally distributed relational transactions.
Workload 1 was a localized departmental database with predictable transactional volume under 64 TB, and Workload 2 required full multi-table relational joins across incoming sensor records.
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