Google Professional Cloud Developer Question 171
Select 1Google Cloud PlatformYou are designing a cloud-based e-commerce application on Google Cloud that needs to store customer orders and product catalog data. The customer orders must support complex queries, such as searching by customer ID, date range, and order status. The product catalog data should be flexible to allow for frequent schema changes, such as adding new attributes for products. Which combination of storage solutions would best suit this use case?
- A
Use Cloud SQL to store customer orders and Firestore to store the product catalog.
- B
Use Firestore to store customer orders and Cloud SQL to store the product catalog.
- C
Use Bigtable to store customer orders and Firestore to store the product catalog.
- D
Use Cloud SQL to store both customer orders and product catalog.
- E
Use Firestore to store both customer orders and product catalog.
Show answer and explanation
Correct answer: A
Explanation
This scenario involves two distinct types of data: structured data (customer orders) and semi-structured/unstructured data (product catalog). Cloud SQL is a relational database that provides robust support for structured data and complex queries, making it ideal for customer orders. Firestore, a NoSQL database, offers schema flexibility and is well-suited for semi-structured or unstructured data, making it a better choice for the product catalog. Choosing the right storage solution for each type of data ensures optimal performance and scalability.
- A. Correct.
Correct. Cloud SQL is a relational database suitable for structured data like customer orders that require complex queries. Firestore is a NoSQL database that is well-suited for unstructured or semi-structured data like a product catalog with frequent schema changes.
- B. Incorrect.
Incorrect. Firestore is not ideal for storing customer orders because it does not support complex queries as efficiently as Cloud SQL. Cloud SQL is also not a good fit for the product catalog due to its rigid schema requirements.
- C. Incorrect.
Incorrect. Bigtable is optimized for analytical workloads with high throughput and is not ideal for transactional systems like customer orders. Firestore is a good choice for the product catalog, but the combination does not fully address the use case.
- D. Incorrect.
Incorrect. While Cloud SQL is suitable for customer orders, it is not an ideal choice for the product catalog due to its inability to adapt easily to frequent schema changes.
- E. Incorrect.
Incorrect. Using Firestore for both customer orders and product catalog might simplify the architecture, but it is not suitable for customer orders because Firestore lacks support for complex relational queries.