Google Professional Cloud Developer Question 169
Select 1Google Cloud PlatformYou are designing a cloud-native application for an e-commerce platform that needs to store customer order information and real-time product recommendations. The order information must support complex queries with relationships between entities, while the product recommendations need to handle high write throughput and flexible schema changes. Which combination of data storage solutions should you use?
- A
Use a relational database like Cloud SQL for customer order information and Firestore for product recommendations.
- B
Use Firestore for both customer order information and product recommendations.
- C
Use Bigtable for customer order information and Firestore for product recommendations.
- D
Use a relational database like Cloud SQL for both customer order information and product recommendations.
- E
Use Bigtable for customer order information and BigQuery for product recommendations.
Show answer and explanation
Correct answer: A
Explanation
The key to solving this scenario is understanding the strengths of structured versus unstructured data storage solutions. Customer order information requires structured data storage with relational database capabilities, such as Cloud SQL, to handle complex queries and relationships. Real-time product recommendations need a NoSQL database like Firestore to support high throughput and flexible schema changes. This ensures optimal performance and scalability for both use cases.
- A. Correct.
Correct: A relational database like Cloud SQL is well-suited for storing customer order information due to its support for complex queries and relationships. Firestore, being a NoSQL database, excels at handling high write throughput and flexible schema needs, making it ideal for real-time product recommendations.
- B. Incorrect.
Incorrect: While Firestore is excellent for flexible schemas and scalability, it is not well-suited for the complex queries and relationships required by customer order information.
- C. Incorrect.
Incorrect: Bigtable is optimal for high-throughput and low-latency workloads, but it is not a good fit for storing order information with relational data structures. Firestore is a good choice for product recommendations, but this combination does not address the relational needs of order information.
- D. Incorrect.
Incorrect: Relational databases like Cloud SQL are not ideal for handling real-time, high-throughput data with flexible schema requirements, which is a core need for product recommendations.
- E. Incorrect.
Incorrect: Bigtable is not suitable for relational data like customer orders, and BigQuery is designed for analytical queries rather than real-time product recommendations.