A customer wants to implement virtual provisioning on a new VMAX array and is concerned
about efficient use of available storage and application performance. The VMAX
environment will have file system, database and document repository hosts. The customer
reports the system hosts append data to the file system, the database hosts use auto-extend
and the document repository hosts have low performance and growth requirements. How
should you recommend the host storage be provisioned on the VMAX array?

An SRDF/S customer has implemented FAST VP at R1 and R2 sites. What will happen to a
thin R2 device when a thin R1 device extent is promoted?

A Symmetrix VMAX is configured with FAST DP. It contains three tiers of storage: 1. 200 GB
RAID 5 (3+1) EFD 2. 300 GB RAID 1 15K RPM Fibre Channel 3. 1 TB RAID 6 (6+2) 7200
RPM SATA The storage administrator would like to charge each department that uses the
VMAX for the amount and class of storage they use. Which FAST policy would best lend
itself to the chargeback system?

You are implementing a FAST VP solution for a customer and want to start with a
conservative FAST VP relocation rate. What would be the recommended value for the
relocation rate?

What is a valid FAST VP policy that would be recommended by Tier Advisor?

What is a valid FAST policy?

You are designing tiered storage for a new 2-engine VMAX. What is the minimum number of
Flash drives you should recommend not including hot spares?

Which FAST VP control parameter defines the amount of time FAST VP should wait after a
thin device is brought under FAST VP control before performing a data movement?

Which FAST VP control parameter specifies the maximum amount of time over which long
term activity rates will decay?

What is best practice for binding thin devices in a FAST VP environment?