Which storage policy actions results in a component resync?
A. Enabling object checksum
B. Changing object space reservation to thick provisioning
C. Adding an IOPS Limit rule to a storage policy
D. Changing the failure tolerance method
Which storage policy actions results in a component resync?
The answer is D. FTT does start a resync.
Yes if Checksum is DISABLED and a new policy checksum is ENABLED then there is a resync.
But think about it, the question does not specify whether checksum is enabled or disabled.
For A to be correct it depends on the state of the checksum, whether it is ENABLED or DISABLED.
Changing the failure tolerance also creates resync.
I believe that correct answer is A. I based my answer on article below.
If checksum is already ENABLED, there is no resync or rebuild activity when it is DISABLED. However, if checksum is DISABLED, and a new policy with checksum ENABLED is applied to a VM/VMDK, then a rebuild of the components is takes place.