QRadar's solution to the 'Accumulator is falling behind' issue? Throw a tarp over the problem and hope no one notices. It's the IT equivalent of putting a sock on the doorknob.
D is the answer. Time-series graphs and reports omitting columns? Sounds like a clever way for QRadar to hide its shortcomings from the user. Classic IT move!
I'm going with C. The 'Accumulator is falling behind' warning means the events are being stored, not processed in real-time. That's the only way to explain the warning message.
B has to be the right answer. Automatically dropping the incoming events and flows is the only way QRadar can prevent the system from falling further behind. Aggregating data sounds too complicated.
I think the correct answer is A. QRadar tries to aggregate the events and flows during the next 60 seconds to catch up with the backlog. That seems like the most reasonable approach to handling the 'Accumulator is falling behind' warning.
Rasheeda
23 days agoEmeline
24 days agoVanna
3 days agoRosamond
17 days agoDion
19 days agoChantell
1 months agoEun
4 days agoWilliam
9 days agoFrancine
1 months agoPhuong
2 months agoAsuncion
20 days agoDonte
24 days agoRory
2 months agoStefany
2 months agoVirgina
2 months ago