The cluster level backend IOPS performance graph shows a higher-than-average number of IOPS for back-end storage.
What is a possible reason for this situation?

• A.Not enough capacity for slack space is on vSAN datastore.
• B.Data ^synchronization is in progress.
• C.There is VM storage I/O traffic.
• D.DRS is invoking multiple vMotion migrations.

Comment: *

Name: *

Email: *

Verification: *

Which two characteristics are associated with vSAN Data-In-Transit Encryption? (Choose two.)

• A.Needs specific configuration on the Network switches in order to be enabled
• B.Can be enabled independently of the vSAN Data-At-Rest encryption
• C.Uses AES-256 bit encryption
• D.Requires an external KMS in order to work
• E.Needs to be enabled using vSAN Storage Policies

Comment: *

Name: *

Email: *

Verification: *

The Resyncing Objects view in the vCenter UI reports that some objects are currently resyncing.
Which two actions would cause this situation? (Choose two.)

• A.A change to the storage policy is applied to the objects.
• B.HA Virtual Machine Monitoring forced a VM to reboot.
• C.DRS is relocating VMs between vSAN nodes.
• D.A host failure occurs in the cluster.
• E.A VM snapshot is being deleted.

Comment: *

Name: *

Email: *

Verification: *

All of the virtual machines running on a hybrid vSAN datastore have this storage policy assigned:
Failures to Tolerate (FTT) rule is set to "2 Failures - RAID-1 (Mirroring)".
The vSAN administrator needs to reduce the amount of vSAN datastore capacity the virtual machines will consume.
Which action should the vSAN administrator take to meet this goal?

• A.Modify the FTT rule to "2 Failures - RAID-5 (Erasure Coding)".
• B.Disable Operations reserve and Host rebuild reserve and click "Apply".
• C.Change the FTT rule to "1 Failure - RAID-1 (Mirroring)", and select "Now" for Reapply to VMs.
• D.Add the "Flash read cache reservation" rule to the storage policy, and set to 0%.

Comment: *

Name: *

Email: *

Verification: *

After a server power failure, the administrator noticed the scheduled resyncing in the cluster monitor displays objects to be resynchronized under the pending category.
What are these objects in this category?

• A.The delay timer has not expired.
• B.Object resynchronization must be started manually.
• C.These objects belong to virtual machines, which are powered off.
• D.There are too may objects to be synchronized.

Comment: *

Name: *

Email: *

Verification: *