Question 37
Cloud Native ArchitectureWhat does "event-driven" architecture, often associated with serverless functions, mean?
Correct answer: B
Explanation
Event-driven architecture means work starts when a defined event happens, rather than on a fixed schedule or continuous polling. In serverless systems, functions are invoked by triggers such as an HTTP request or a message, matching the idea that "Code execution is triggered by the occurrence of specific events."
Why each option is right or wrong
A. Applications must be written using event sourcing patterns.
B. Code execution is triggered by the occurrence of specific events (e.g., HTTP request, message).
In event-driven systems, the trigger is the event itself: a function is invoked only when a defined occurrence happens, such as an HTTP request arriving, a queue message being published, or a file upload completing. This matches the serverless model used by platforms like AWS Lambda, where execution is initiated by configured event sources rather than by a cron-style schedule or continuous polling.
C. The platform uses events internally for scheduling, hidden from the user.
D. All application state must be stored within the event payload.
E. Only asynchronous communication patterns can be used.