Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware Exam 2V0-21.23 Topic 6 Question 32 Discussion

Actual exam question for VMware's 2V0-21.23 exam
Question #: 32
Topic #: 6
[All 2V0-21.23 Questions]

A group of new virtual machines have been deployed using thin-provisioned disks due to the limited storage space available in an environment. The storage team has expressed concern about extensive use of this type of provisioning.

An administrator is tasked with creating a custom alarm to notify the storage team when thin provisioning reaches a certain capacity threshold.

Where must the administrator define this alarm?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Kayleigh
3 days ago
Data center? Really? I think the storage team would be pretty upset if I tried to set an alarm at that level. Gotta be more specific than that.
upvoted 0 times
...
Cary
5 days ago
Virtual machine? Haha, no way! The alarm has to be on the actual storage, not the VMs. This one's a no-brainer.
upvoted 0 times
...
Paulene
10 days ago
Datastore cluster, right? That's where all the storage resources are managed, so that's gotta be the place to set the alarm.
upvoted 0 times
...
Tamar
18 days ago
The alarm should be defined on the datastore, since that's where the thin-provisioned disks are stored. Makes sense to me.
upvoted 0 times
Delmy
1 days ago
A: I think the alarm should be defined on the datastore.
upvoted 0 times
...
...
Micheline
20 days ago
I believe the alarm should be defined at the Datastore cluster level for better monitoring.
upvoted 0 times
...
Elenora
21 days ago
I agree with Chantell, Datastore is the right place to define the alarm.
upvoted 0 times
...
Chantell
25 days ago
I think the alarm should be defined at the Datastore level.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77