Which three storages I/O Control conditions might trigger the Non-VI workload detected on the datastore alarm?

Which three storages I/O Control conditions might trigger the Non-VI workload detected on the datastore alarm? (Choose three)

A.
The datastore is connected to an ESX/ESXi 4.0 host that does not support Storage I/O Control.

B.
The datastore is on an array that is performing system tasks such as replication.

C.
The datastore is utilizing active/passive multipathing or NMP (Native Multi-Pathing)

D.
The datastore is storing virtual machines with one or more snapshots.

E.
The datastore is connected to an ESX/ESXi 4.0 host that is not managed by vCenter

Explanation:
http://kb.vmware.com/kb/1020651
…
* One or more hosts accessing the datastore are running an ESX version older than 4.1.
* One or more hosts accessing the datastore are not managed by vCenter Server.
* Not all of the hosts accessing the datastore are managed by the same vCenter Server.
* The storage media (spindles, SSD) where this datastore is located are shared with other datastores that are not SIOC enabled.
* Datastores in the configuration have multiple extents.

http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.troubleshooting.doc_50/GUID-38F95285-DB4F-462F-AFD7-0F4D812B085F.html
or
Page 39 on vsphere-esxi-vcenter-server-50-troubleshooting-guide.pdf

Unsupported Host Connected to Datastore
In the vSphere Client, an alarm is triggered when vCenter Server detects that a workload from a host might be affecting performance.
Problem
The alarm Pre-4.1 host connected to SIOC-enabled datastore is triggered.
Cause
The datastore is Storage I/O Control-enabled, but it cannot be fully controlled by Storage I/O Control because of the external workload.
This condition can occur if the Storage I/O Control-enabled datastore is connected to a host that does not support Storage I/O Control.
Solution
Ensure that all hosts that are connected to the datastore support Storage I/O Control.