What approach does QRadar take when it imposes EPS license (not hardware) limits on events that temporarily spike above that limit?
What approach does QRadar take when it imposes EPS license (not hardware) limits on events that temporarily spike above that limit?
When QRadar encounters a temporary spike in events per second (EPS) that exceeds the licensed limit, it handles the excess events by writing them to a queue. These queued events are then processed once the EPS rate drops back within the licensed threshold. This approach ensures that no data is lost during spikes and that the system can handle temporary increases in event rates efficiently.
The right answer is C
C - https://www.ibm.com/docs/en/qsip/7.4?topic=management-burst-handling
C - During the spike, excess events are written to a queue, and they are processed after the EPS rate drops.