What is the reason for this issue not being reported to OME?

A user installed OME on a PowerEdge R640 server. OME has discovered and is currently monitoring another 30 remote PowerEdge 14G servers.

Each server has the following configuration:

– 2x CPUs

– 384 GB RAM

– 6x 1TB drives in a RAID 6 virtual disk

– No hot spare drive

– PERC

– vFlash

– iDRAC9 Express license

At 9 PM on Monday evening, one of the remote servers has a disk failure but stays operational. The administrator monitoring OME does not find out about the issue until 5 PM in the following Friday. They place a support call to investigate why OME was not informed about the disk failure before then.

What is the reason for this issue not being reported to OME?
A . Remote servers are not configured with OME as the trap destination address. OME discovered the issue during a routing status check which is configured to run at 5 PM every Friday.
B . OME only updates its alert database at 5 PM every Friday.
C . Remote servers are not configured with OME as the trap destination address. OME was informed of the issue when remote servers sent alerts at 5 PM Friday.
D . Remote servers need to have the iDRAC Enterprise license installed to be able to send alerts.