A group of virtual machines has been deployed using thin disk because of limited storage space availability. The storage team has expressed concern about extensive use of this type of provisioning.
What can be done to to inform an administrator when an unacceptably of virtual machines are being deployed using thin-disk provisioning?
A.
Modify the default datastore usage on disk alarm with a determined percentage. Create a trigger for the alarm with an email or SNMP notification option.
B.
Use the default host storage Status alarm. Crate a trigger for the alarm with an emailor SNMP notification option.
C.
Find the predefined Thin-Provisioned LUN Capacity Exceeded alarm for each datastore. Set an action to enable the email or SNMP notification option.
D.
Create an alarm for Disk Usage and determine the appropriate amount. Create a trigger for the alarm with an email or SNMP notification option.
I think it should be “A”. There should be an alarm for disk storage to avoid its filling.
According to info below it should be A.
Alarm Example: Setting an Alarm Action for Datastore Usage on a Disk
This example demonstrates a useful type of alarm action that you might configure for an object in the vSphere inventory, including responding to the alarm when it triggers.
Dozens of default alarm definitions are provided by the vSphere Client, which you can locate in the Alarms tab for an inventory object. One of these default alarms is Datastore usage on disk, which you use to monitor the percentage of disk usage. This kind of alarm is important if the virtual machines in the datastore have virtual disks in the thin provisioned format. With thin provisioning, at first a thin provisioned disk uses only as much datastore space as the disk initially needs. However, if the thin disk needs more space later, it can grow to the maximum capacity allocated to it.
With thin provisioning, it is possible to oversubscribe storage space if the virtual machines grow unattended. An alarm set on the datastore can notify you when the space issues threaten to become critical.
http://pubs.vmware.com/vsphere-50/index.jsp?topic=/com.vmware.vsphere.avail.doc_50/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html