Google Professional Cloud Developer Question 197
Select 2Google Cloud PlatformYou are designing a system for an e-commerce company that handles both transactional order processing and analytical sales reporting. Which of the following configurations would best meet the requirements for Online Transaction Processing (OLTP) and data warehousing workloads?
- A
Use Cloud Spanner for transactional order processing and BigQuery for analytical reporting.
- B
Use Firestore for both transactional order processing and analytical reporting.
- C
Use Cloud SQL for transactional order processing and BigQuery for analytical reporting.
- D
Use BigQuery for both transactional order processing and analytical reporting.
- E
Use Cloud Bigtable for transactional order processing and BigQuery for analytical reporting.
Show answer and explanation
Correct answers: A, C
Explanation
OLTP workloads require databases that support high-frequency, low-latency transactional operations, such as Cloud Spanner or Cloud SQL. Data warehousing workloads involve running large-scale analytical queries, making BigQuery the right choice. Using solutions like Firestore or Cloud Bigtable for OLTP in this scenario would not meet the requirements effectively, and BigQuery is not suitable for OLTP workloads.
- A. Correct.
Correct: Cloud Spanner is a horizontally scalable, strongly consistent database suitable for OLTP workloads. BigQuery is a data warehouse optimized for analytical workloads.
- B. Incorrect.
Incorrect: Firestore is optimized for NoSQL document-based use cases and is not ideal for large-scale OLTP or complex analytical queries.
- C. Correct.
Correct: Cloud SQL is a relational database service that works well for OLTP workloads. BigQuery is optimized for analytical tasks, making it a good choice for data warehousing.
- D. Incorrect.
Incorrect: BigQuery is not designed for OLTP workloads as it is optimized for analytical processing and not for the high-frequency, low-latency transactions typical in OLTP.
- E. Incorrect.
Incorrect: Cloud Bigtable is a NoSQL database optimized for low-latency, high-throughput workloads but not ideal for traditional OLTP use cases. BigQuery is suitable for analytical workloads but pairing it with Cloud Bigtable would not address OLTP requirements properly.