In what two ways does this affect the datastore? (Choose two

A VMFS3 datastore has just been upgraded to VMFS5.

In what two ways does this affect the datastore? (Choose two.)

A VMFS3 datastore has just been upgraded to VMFS5.

In what two ways does this affect the datastore? (Choose two.)

A.
The existing VMFS3 block size is retained.

B.
The block size will be changed to 8MB.

C.
Any existing VMDK can be expanded up to 2TB.

D.
VMDKs retain their size limit from the VMFS3 block size.



Leave a Reply 8

Your email address will not be published. Required fields are marked *


Mohsin Alvi

Mohsin Alvi

@anonim both above mention articles are opposite each others , but i think the article you mentioned is more appropriate as it perform the thing via pratcial

Mike

Mike

How can C be correct if the size of datastore is not specified. It will be true for a 2TB datastore, but won’t be true for a 500GB one.
“***ANY*** existing VMDK can be expanded up to 2TB”

The question is too vague. The answer should be A. D is only applicable under certain conditions – size of datastore and disk type – think vs thick.

Jake

Jake

In the article listed above is says:
If you upgrade to VMFS-5 from VMFS-3 then regardless of the block size, VMFS-5 uses double-indirect addressing to cater for large files (up to a size of 2 TB – 512 B) on upgraded VMFS-3 volumes. For example, if the VMDK goes beyond 512 GB it will switch to using double-indirect addressing, which will allow for VMDKs up to 2 TB – 512 B.

I think C is correct?