PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #127
Your ecommerce website captures user clickstream data to analyze customer traffic patterns in real time and support personalization features on your website. You plan to analyze this data using big…
The correct answer is A. Write your data into Bigtable and use Dataproc and the Apache Hbase libraries for analysis. Bigtable is purpose-built for exactly this workload: low-latency (single-digit milliseconds), massive write/read throughput (millions of requests per second), and petabyte-scale storage. Its row-key-based design is ideal for clickstream data keyed by user or session ID…
Question
Your ecommerce website captures user clickstream data to analyze customer traffic patterns in real time and support personalization features on your website. You plan to analyze this data using big data tools. You need a low-latency solution that can store 8 TB of data and can scale to millions of read and write requests per second. What should you do?
Options
- AWrite your data into Bigtable and use Dataproc and the Apache Hbase libraries for analysis.
- BDeploy a Cloud SQL environment with read replicas for improved performance. Use Datastream
- CUse Memorystore to handle your low-latency requirements and for real-time analytics.
- DStream your data into BigQuery and use Dataproc and the BigQuery Storage API to analyze large
How the community answered
(52 responses)- A77% (40)
- B13% (7)
- C2% (1)
- D8% (4)
Explanation
Bigtable is purpose-built for exactly this workload: low-latency (single-digit milliseconds), massive write/read throughput (millions of requests per second), and petabyte-scale storage. Its row-key-based design is ideal for clickstream data keyed by user or session ID. Dataproc with Apache HBase libraries provides the big data analysis capability on top of Bigtable. Option B (Cloud SQL with read replicas) cannot scale to millions of requests per second. Option C (Memorystore/Redis) is an in-memory cache, not a durable storage solution for 8 TB of data. Option D (BigQuery) is optimized for analytical queries, not for low-latency real-time ingestion at millions of writes per second.
Topics
Community Discussion
No community discussion yet for this question.