Examkin

Question

Difficulty: MediumSelecting and Designing Storage and Database Resources

An international logistics enterprise is architecting a data tier on Google Cloud to manage two distinct operational workloads:

1. A transactional core order management database requiring multi-region relational ACID compliance, horizontal scaling for write operations, and strong consistency across multiple continents.
2. A telemetry ingestion engine recording millions of real-time GPS and temperature sensor data points per second, requiring high-throughput, low-latency time-series key-value storage.

Which TWO storage and database services should the cloud architect select to satisfy these architecture requirements? (Select TWO answers.)

  1. Cloud Spanner for the order management database workloadAnswer
  2. Cloud Bigtable for the telemetry ingestion workloadAnswer
  3. C
    Cloud SQL for PostgreSQL with cross-region read replicas for the order management database workload
  4. D
    Transfer Appliance for continuous real-time telemetry ingestion storage

Answer

Cloud Spanner should be selected for the globally distributed transactional order management workload, and Cloud Bigtable should be selected for the high-throughput time-series sensor telemetry ingestion workload.
Cloud Spanner satisfies the global order management requirement because it offers multi-region relational storage, global ACID compliance, and horizontal scaling. Cloud Bigtable satisfies the telemetry requirement because it handles massive high-throughput time-series key-value workloads with millisecond latencies.

Step-by-Step Solution

1
Analyze the relational transactional requirements.
The transactional workload requires multi-region relational ACID compliance, global strong consistency, and horizontal write scalability.
Cloud Spanner is the only native GCP database service capable of global relational ACID transactions with horizontal write scaling.
2
Analyze the telemetry streaming requirements.
The telemetry ingestion workload requires storing millions of time-series key-value readings per second at low latency.
Cloud Bigtable is designed specifically for high-volume NoSQL time-series telemetry data with continuous high-write throughput.
3
Evaluate and eliminate invalid storage options.
Cloud SQL is limited to single-region write primary instances and cannot scale writes horizontally across regions. Transfer Appliance is an offline physical migration device, not an ingestion database.
Neither Cloud SQL nor Transfer Appliance meets the stated scale and operational criteria.

Key Concept

Matching transactional and analytical telemetry workloads to appropriate GCP managed database services based on scale, consistency, and access patterns.
Rate this question

Topics

Selecting and Designing Storage and Database Resources