A VPlex administrator claims a 100GB Storage Volume that is thin provisioned on the storage
array and has 25GB physically allocated and creates a 1:1 encapsulated virtual volume. After a
local data mobility job for that Virtual Volume, the storage array administrator notices that the
allocated capacity has increased to 100GB.
Why did this happen?

What unique logical identifier is recommended when determining the relationship between a virtual
volume and the back-end storage array?

After an expansion of a RAID-0 device in VPLEX, the customer notices a slight degradation of
performance. What could cause this?

A customer wants to add a mirror to a VPLEX Local RAID-0 device.
Which RAID type is created after the command “device attach-mirror”?

What steps must be performed to encapsulate LUNs into virtual volumes?

In addition to HP-UX, RecoverPoint, SUN-VCS, and AIX, which host type option is available when
registering a host initiator in VPLEX?

Starting in Geosyncrony version 5.1 what are the minimum password requirements?

In Unisphere for VPLEX, which storage array does not require a mapping file when claiming
storage volumes?

What are the four basic dm migration commands for moving extents or devices?

What device types can be created in a VPLEX environment?