Google Professional Cloud Developer Question 15
Single answerGoogle Cloud PlatformYou are tasked with building a new event-driven web application that processes incoming user data in real-time. The application requires minimal management overhead, scales automatically with demand, and costs should be proportional to usage. Which Google Cloud service model is the most appropriate for this use case?
- A
IaaS (Infrastructure as a Service)
- B
CaaS (Container as a Service)
- C
PaaS (Platform as a Service)
- D
FaaS (Function as a Service)
Show answer and explanation
Correct answer: D
Explanation
The scenario describes an event-driven application with real-time processing, minimal management, and automatic scaling requirements. FaaS (Function as a Service), such as Google Cloud Functions, is designed for such use cases, offering an event-driven execution model, automatic scaling, and a pay-per-use billing model. Other service models like IaaS, CaaS, and PaaS involve more management overhead or are less optimized for event-driven use cases, making FaaS the most appropriate choice.
- A. Incorrect.
IaaS provides virtualized computing resources like virtual machines, storage, and networking. While highly flexible, it requires significant management and is not ideal for event-driven applications with unpredictable scaling needs.
- B. Incorrect.
CaaS enables container-based application deployment and management. While it provides abstraction and some scalability, it still requires managing container orchestration and infrastructure, which increases overhead compared to FaaS.
- C. Incorrect.
PaaS allows developers to focus on application development by abstracting infrastructure management, but it is less suited for granular, event-driven workloads and may result in higher costs for low-frequency or bursty workloads.
- D. Correct.
FaaS is ideal for event-driven architectures as it abstracts infrastructure management, scales automatically, and charges based on usage. It aligns perfectly with the requirements of minimal overhead, automatic scaling, and cost proportional to usage.