H13-821_V3.0 · Question #304
In scenarios where traffic increases rapidly in a short period of time, such as commodity spikes and snap-ups, in order to prevent the back-end application from being suppressed, Kafka can be used…
The correct answer is A. True. Option A is correct because Kafka functions as a message queue that acts as a buffer between front-end and back-end systems, absorbing sudden bursts of incoming requests so the back-end processes them at a controlled, sustainable rate rather than all at once. During traffic…
Question
In scenarios where traffic increases rapidly in a short period of time, such as commodity spikes and snap-ups, in order to prevent the back-end application from being suppressed, Kafka can be used to transfer requests between the front-end and back-end systems
Options
- ATrue
- BFalse
How the community answered
(38 responses)- A74% (28)
- B26% (10)
Explanation
Option A is correct because Kafka functions as a message queue that acts as a buffer between front-end and back-end systems, absorbing sudden bursts of incoming requests so the back-end processes them at a controlled, sustainable rate rather than all at once. During traffic spikes - such as flash sales or limited-quantity product grabs - without this buffer, the back-end could be overwhelmed, leading to crashes, timeouts, or degraded performance. Option B is incorrect because denying Kafka's role here contradicts its core design purpose: Kafka was built precisely for high-throughput, fault-tolerant, asynchronous message passing that decouples producers (front-end) from consumers (back-end).
Memory tip: Think of Kafka as a "shock absorber" on a car - the road (traffic) can be bumpy and unpredictable, but the shock absorber (Kafka) smooths out the ride so the passengers (back-end systems) never feel the full impact.
Topics
Community Discussion
No community discussion yet for this question.