Question

Difficulty: HardSelecting and Designing Storage and Database Resources

A global media streaming provider is architecture-designing its next-generation GCP storage layer. The architecture must support two core workloads with distinct performance and transactional operational requirements:

1. A global user subscription entitlement database requiring relational SQL capabilities, multi-region synchronous write consistency, high availability across continents, and seamless horizontal scale without application downtime.
2. A high-throughput telemetry engine recording real-time user playback interaction events (time-series data) generating millions of write requests per second with sub-10ms write latency.

Which TWO storage and database service selections should the cloud architect recommend to satisfy these requirements? (Select TWO.)

  1. Deploy Cloud Spanner to manage the global user subscription entitlement database.Answer
  2. Deploy Cloud Bigtable to handle the high-throughput real-time user playback interaction telemetry.Answer
  3. C
    Deploy Cloud SQL for PostgreSQL configured with cross-region read replicas for the global user subscription entitlement database.
  4. D
    Configure Customer-Supplied Encryption Keys (CSEK) for Cloud Storage audit bucket exports to simplify key management overhead.

Answer

The optimal architectural selection requires Cloud Spanner for the globally distributed transactional relational subscription entitlement database and Cloud Bigtable for the high-throughput real-time playback telemetry workload.
Cloud Spanner fulfills the requirement for a multi-region relational database with strong global consistency and horizontal write scaling. Cloud Bigtable delivers the low sub-10ms write latency and high throughput required for real-time time-series telemetry processing.

Step-by-Step Solution

1
Analyze the requirements for the subscription entitlement database.
Identified needs for multi-region relational SQL, synchronous global write consistency, and horizontal scale.
Cloud Spanner is Google Cloud's globally distributed relational database offering relational features with multi-region strong consistency.
2
Analyze the requirements for the playback telemetry engine.
Identified needs for high write throughput, time-series access pattern, and sub-10ms write latency at scale.
Cloud Bigtable is a NoSQL wide-column database engineered specifically for high-volume time-series and low-latency streaming write workloads.
3
Evaluate and eliminate non-conforming service options.
Cloud SQL with cross-region replicas lacks multi-region write consistency and horizontal scale. CSEK unnecessarily adds raw key management overhead compared to CMEK.
Cloud SQL regional boundaries limit multi-region write scalability, while CSEK places raw key security management on the customer.

Key Concept

Selecting GCP Storage Services Based on Scalability, Consistency, and Workload Access Patterns
Estimated Time:2m 0s
Rate this question