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.
Emeline
12 hours agoChantell
10 days agoFrancine
12 days agoPhuong
23 days agoRory
26 days agoStefany
28 days agoVirgina
1 months ago