Exam 3V0-752 topic 1 question 42 discussion

seems that the question here is whether or not space-efficient disk can or should be used with instant clones here is a possible scenario: if you build an instant clone pool with dedicated user assignment, you will be provided with an option to "refresh OS disk after logoff" with the following values: never, always, every, and at. Which means you can use an instant clone pool in the fashion of linked clones where the OS may actually never be refreshed. That implies the space-efficient disks may be useful in space reclamation while using instant clones pools. I know this is a highly unlikely scenario, but is totally possible. Most of the instant clone use cases are are set to refresh OS at user log off which makes SE sparse useless but the above example is the exception. https://docs.vmware.com/en/VMware-Horizon-7/7.12/virtual-desktops/GUID-2D97475B-7DDF-49CF-9A41-AA832388E968.html https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_Solutions/VDI_User_Guide/Best_Practices%3A_Configuration_and_Tuning BCD

BDE: https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-architecture-planning/GUID-4880340C-C80C-4CE1-95FA-8692A5BFA3BC.html "Due to short-lived nature of instant-clone desktops, instant clones do not support the space-efficient disk format (SE sparse), with its wipe and shrink process."

Correction: Space-Efficient is used on Linked Clone for Space Reclamation.

Yeap SESparse is for snapshot but what made Instant CLone possible. Answer is BCD

I think BDE, SESparse for snapshot