Google Professional Cloud Developer Question 181
Select 3Google Cloud PlatformYou are developing an application on Google Cloud that processes high volumes of transactional data from multiple sources in real-time. The application must scale automatically based on changes in data volume, minimize latency, and ensure data is processed reliably. Which Google Cloud services should you use to meet these requirements?
- A
Google Cloud Pub/Sub
- B
Google Cloud Spanner
- C
Google Cloud Functions
- D
Google Cloud BigQuery
- E
Google Compute Engine
Show answer and explanation
Correct answers: A, B, C
Explanation
To handle high volumes of transactional data in real-time with automatic scaling and reliability, the best combination of services includes Google Cloud Pub/Sub for messaging, Google Cloud Spanner for transaction processing, and Google Cloud Functions for event-driven compute. This architecture ensures scalability, low latency, and reliability while minimizing operational overhead. BigQuery and Compute Engine, while powerful, do not align with the real-time, event-driven nature of the requirements in this scenario.
- A. Correct.
Google Cloud Pub/Sub is a messaging service designed for real-time data ingestion and event processing, making it ideal for handling high volumes of data and ensuring reliable communication between components.
- B. Correct.
Google Cloud Spanner is a globally distributed, highly scalable relational database service that supports high volumes of transactional data with low latency and strong consistency.
- C. Correct.
Google Cloud Functions is a serverless compute service that can automatically scale based on data volume, enabling the application to respond dynamically to real-time changes in workload.
- D. Incorrect.
Google Cloud BigQuery is an excellent choice for analytics on large datasets, but it is not designed for real-time data processing or handling transactional workloads.
- E. Incorrect.
Google Compute Engine provides virtual machines but requires manual scaling configurations and is less suited for real-time, event-driven architectures compared to serverless and managed services.