Google Professional Data Engineer Question 131
Single answerGoogle Cloud PlatformYour company is building a real-time recommendation engine for an e-commerce platform. The system needs to serve low-latency read and write requests while scaling horizontally as user traffic grows. The data model is non-relational, with nested and repeated fields to store user interactions on the platform. Which managed Google Cloud service should you choose to store this data?
- A
Bigtable
- B
Cloud Spanner
- C
Cloud SQL
- D
Firestore
Show answer and explanation
Correct answer: A
Explanation
Bigtable is the best choice for the described scenario because it is a fully managed, NoSQL database optimized for low-latency, high-throughput workloads. It scales horizontally, making it ideal for real-time use cases such as recommendation engines. The non-relational data model with nested fields aligns well with Bigtable's capabilities, whereas the other options are either relational databases or not optimized for such high-performance requirements.
- A. Correct.
Bigtable is an ideal choice for low-latency, horizontally scalable, non-relational workloads, such as storing user interactions in a recommendation engine. It can handle nested and repeated fields effectively and is designed for high throughput.
- B. Incorrect.
Cloud Spanner is a relational database that supports SQL queries and transactions. While it scales horizontally, it is better suited for use cases requiring strong consistency and relational schemas, which are not a requirement in this scenario.
- C. Incorrect.
Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server. It is not optimized for horizontally scaling workloads or non-relational data, making it less suitable for the given scenario.
- D. Incorrect.
Firestore is a NoSQL database designed for mobile and web applications. While it supports hierarchical data and low-latency operations, it is not as optimized for high-throughput, horizontally scalable workloads as Bigtable.