Google Professional Cloud Developer Question 182
Single answerGoogle Cloud PlatformYou are developing a real-time analytics application on Google Cloud that processes a high volume of streaming data from IoT sensors. The data volume is expected to grow exponentially over the next few years. Which approach should you prioritize to ensure scalability and cost-effectiveness in handling the increasing data volume?
- A
Store all incoming data in Cloud SQL for structured querying.
- B
Use Cloud Pub/Sub to ingest the streaming data and integrate it with Dataflow for processing.
- C
Process data locally on each IoT device to reduce the volume of data sent to the cloud.
- D
Use a single-instance Compute Engine VM with a large disk for data ingestion and processing.
Show answer and explanation
Correct answer: B
Explanation
The combination of Cloud Pub/Sub and Dataflow is a best practice for ingesting and processing high-volume streaming data on Google Cloud. Pub/Sub provides a scalable messaging solution to handle growing data volumes, while Dataflow enables real-time data processing with autoscaling capabilities. This approach ensures both scalability and cost-effectiveness as the data volume grows.
- A. Incorrect.
Cloud SQL is not designed to handle high volumes of streaming data efficiently. It is better suited for structured, relational data and transactional workloads, not for high-throughput ingestion of streaming data.
- B. Correct.
Cloud Pub/Sub is designed for scalable message ingestion, and Dataflow provides a managed service for real-time data processing. This combination is well-suited for handling high-volume streaming data in a scalable and cost-effective manner.
- C. Incorrect.
Processing data locally on IoT devices may reduce data volume sent to the cloud, but it is not practical for all use cases, especially when the data needs centralized processing and storage for analytics.
- D. Incorrect.
A single-instance Compute Engine VM is not scalable for handling exponentially growing data volumes, and it introduces a single point of failure, making it unsuitable for this scenario.