Examkin

Question

Difficulty: MediumSelecting and Designing Storage and Database Resources

Match each enterprise workload requirement to the most appropriate Google Cloud database or storage service based on its data model, consistency guarantees, and operational access pattern.

  • Globally distributed transactional OLTP database requiring full ANSI SQL support, horizontal scaling, and external consistency across multiple geographic regions.Cloud Spanner
  • High-throughput time-series IoT sensor data ingestion requiring sub-10 millisecond write latencies and integration with analytical processing pipelines.Cloud Bigtable
  • Unstructured document and binary media file storage requiring automated lifecycle policies to move infrequently accessed objects to lower-cost archival classes.Cloud Storage
  • Regional relational database requiring native PostgreSQL compatibility, automated backups, and built-in regional high availability failover.Cloud SQL for PostgreSQL

Answer

The globally distributed transactional database maps to Cloud Spanner; the high-throughput time-series IoT ingestion maps to Cloud Bigtable; the unstructured media storage with lifecycle policies maps to Cloud Storage; and the regional relational PostgreSQL database maps to Cloud SQL for PostgreSQL.
Each GCP database and storage product is engineered for specific data models and access patterns: Cloud Spanner handles global multi-region relational transactions; Cloud Bigtable excels at high-speed NoSQL time-series writes; Cloud Storage manages unstructured binary objects with lifecycle tiering; and Cloud SQL handles single-region managed relational engines like PostgreSQL.

Step-by-Step Solution

1
Analyze the relational and global scaling constraints of the transactional database requirement.
Identified Cloud Spanner as the unique GCP service offering global scale, ANSI SQL support, and strong external consistency.
Standard regional relational options like Cloud SQL do not scale horizontally across multiple regions with global strong consistency.
2
Evaluate the ingestion rate and write latency requirements for time-series IoT data.
Selected Cloud Bigtable for its high-throughput, low-latency NoSQL key-value/wide-column engine optimized for streaming time-series data.
Relational databases cannot cost-effectively sustain massive continuous IoT write loads with sub-10ms latency.
3
Review object storage requirements for unstructured files and cost-tiering capabilities.
Selected Cloud Storage due to its object storage model and Object Lifecycle Management feature.
Database services are intended for structured or semi-structured data, whereas unstructured media files require object storage.
4
Assess the regional managed database requirement for open-source PostgreSQL compatibility.
Matched with Cloud SQL for PostgreSQL.
Cloud SQL provides managed PostgreSQL with built-in regional high availability.

Key Concept

GCP Storage and Database Resource Selection based on Data Model, Scalability, and Access Patterns
Estimated Time:2m 0s
Rate this question

Topics

Selecting and Designing Storage and Database Resources