Match each workload storage requirement to the most appropriate Google Cloud database or storage service based on data access patterns, scalability, and consistency models.
- Low-latency, high-throughput NoSQL key-value store for serving real-time user recommendation features with single-digit millisecond latency.Cloud Bigtable
- Fully managed relational database supporting global ACID transactions, horizontal scaling across regions, and high availability for financial trade settlement.Cloud Spanner
- Regional relational database requiring full SQL support, ACID compliance, automatic failover, and read replicas for a regional CRM application.Cloud SQL
- Unstructured object storage used to store media assets and system log archives with automated lifecycle management for cost tiering.Cloud Storage
Answer
Low-latency key-value feature serving maps to Cloud Bigtable; Global relational trade settlement with strong consistency maps to Cloud Spanner; Regional relational CRM application maps to Cloud SQL; Unstructured media assets and log archives with lifecycle policies map to Cloud Storage.
Each requirement directly matches the core capability of the corresponding GCP service: Cloud Bigtable for high-throughput NoSQL key-value lookups; Cloud Spanner for global multi-region relational ACID workloads; Cloud SQL for standard regional relational databases; and Cloud Storage for unstructured object storage with lifecycle management.
Step-by-Step Solution
Key Concept
GCP Storage and Database Resource Selection Criteria
Estimated Time:1m 30s