Which statement best describes Serverless architecture's event-driven nature?

Which statement best describes Serverless architecture's event-driven nature?

• A. It scales automatically based on demand
• B. It runs in response to events
• C. It requires manual scaling
• D. It uses persistent connections

Answer: (B)

In serverless, code is invoked only when something happens—an event. Think of functions that sit idle until triggered by an event like an HTTP request, a new message in a queue, a file upload, or a database change. When the event occurs, the platform runs the function, handles provisioning, and scales automatically with the rate of incoming events. This on-demand invocation is the essence of its event-driven behavior. Manual scaling and persistent connections aren’t characteristic of this model: serverless aims to avoid long-lived state and hands off scaling to the platform, starting fresh for each event. So the statement that best captures the event-driven nature is that it runs in response to events.

In serverless, code is invoked only when something happens—an event. Think of functions that sit idle until triggered by an event like an HTTP request, a new message in a queue, a file upload, or a database change. When the event occurs, the platform runs the function, handles provisioning, and scales automatically with the rate of incoming events. This on-demand invocation is the essence of its event-driven behavior. Manual scaling and persistent connections aren’t characteristic of this model: serverless aims to avoid long-lived state and hands off scaling to the platform, starting fresh for each event. So the statement that best captures the event-driven nature is that it runs in response to events.