Google Professional Cloud Developer Question 152
Select 2Google Cloud PlatformYou are building a financial application that requires strong consistency for transaction data, low-latency access for customer profiles, and scalable, cost-effective storage for historical logs. Which combination of Google Cloud storage solutions should you use to meet these requirements?
- A
Use Cloud Spanner for transaction data, Memorystore for customer profiles, and Cloud Storage for historical logs.
- B
Use Cloud Firestore for transaction data, Cloud SQL for customer profiles, and BigQuery for historical logs.
- C
Use Cloud SQL for transaction data, Cloud Memorystore for customer profiles, and Cloud Storage for historical logs.
- D
Use Bigtable for transaction data, Memorystore for customer profiles, and Cloud SQL for historical logs.
- E
Use Cloud Spanner for transaction data, Bigtable for customer profiles, and Cloud Storage for historical logs.
Show answer and explanation
Correct answers: A, C
Explanation
Choosing storage options depends on the nature of the data and the application's requirements. Transaction data benefits from strong consistency and scalability, which is supported by Cloud Spanner or Cloud SQL. Customer profiles require low-latency access, well-handled by a memory-based service like Memorystore. Finally, historical logs require a cost-effective and scalable solution, such as Cloud Storage. Both Option 1 and Option 3 balance these requirements appropriately.
- A. Correct.
Correct: Cloud Spanner provides strong consistency, scalability, and global distribution, making it ideal for transaction data. Memorystore provides low-latency access for frequently accessed customer profile data, and Cloud Storage is cost-effective for storing large volumes of historical logs.
- B. Incorrect.
Incorrect: Cloud Firestore supports strong consistency for transaction data, but it is better suited for hierarchical or document-based data, which is not specified here. Cloud SQL is not optimized for low-latency access to customer profiles, and BigQuery is designed for analytical queries, not storing historical logs.
- C. Correct.
Correct: Cloud SQL is a reliable choice for transaction data requiring strong consistency. Memorystore is suitable for low-latency access to customer profiles, and Cloud Storage is cost-effective for storing historical logs.
- D. Incorrect.
Incorrect: Bigtable is ideal for high-throughput, low-latency workloads but is not designed for strong consistency in transaction data. Memorystore is suitable for customer profiles, but Cloud SQL is a poor fit for cost-effective storage of historical logs.
- E. Incorrect.
Incorrect: Cloud Spanner is appropriate for transaction data, but Bigtable is not the best choice for customer profiles requiring low-latency access. Cloud Storage is suitable for historical logs, but this combination lacks balance for the given requirements.