Question

Difficulty: EasySelecting and Designing Storage and Database Resources

Match each Google Cloud storage or database service on the left to its primary workload characteristic and access pattern on the right.

  • Cloud BigtableHigh-throughput, low-latency NoSQL wide-column store designed for large-scale analytical and time-series workloads.
  • Cloud SpannerGlobally distributed relational database supporting horizontal scaling with full transactional ACID compliance across regions.
  • Cloud StorageUnstructured object storage optimized for binary data, media files, backups, and data lake storage.
  • Cloud SQLFully managed regional relational database service supporting traditional engines like PostgreSQL, MySQL, and SQL Server.

Answer

Cloud Bigtable matches the high-throughput NoSQL wide-column store for time-series/analytical workloads. Cloud Spanner matches the globally distributed relational database with horizontal scaling and ACID compliance. Cloud Storage matches the unstructured object storage service for media and backups. Cloud SQL matches the managed regional relational database supporting PostgreSQL, MySQL, and SQL Server.
Each service is accurately paired with its primary architecture pattern: Cloud Bigtable for high-throughput NoSQL wide-column data, Cloud Spanner for globally consistent multi-region relational data, Cloud Storage for unstructured object data, and Cloud SQL for regional managed relational databases.

Step-by-Step Solution

1
Identify the data model requirements (structured relational vs. unstructured vs. NoSQL wide-column).
Cloud Storage handles unstructured objects; Cloud Bigtable handles NoSQL wide-column data; Cloud SQL and Cloud Spanner handle structured relational data.
Categorizing services by data model narrows down valid target access patterns.
2
Evaluate scale and regional constraints for relational services.
Cloud SQL represents regional managed relational engines (MySQL/PostgreSQL/SQL Server), whereas Cloud Spanner represents multi-region horizontal scaling with ACID guarantees.
Distinguishing between regional relational engines and enterprise global relational databases separates Cloud SQL from Cloud Spanner.
3
Verify NoSQL and object storage use cases.
Cloud Bigtable aligns with high-throughput key-value/time-series data, and Cloud Storage aligns with unstructured binary file and backup object storage.
Matching specific performance characteristics completes all service definitions.

Key Concept

Selecting GCP storage and database services based on data model, consistency needs, scale requirements, and access patterns.
Rate this question