1Y0-312 Performance and Scalability Optimization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use full clone VMs to ensure performance parity.

  Why it's wrong here

  Full clones require significant storage space because each VM contains a complete copy of the operating system. This is highly inefficient for a non-persistent environment where the OS is identical for all users. Shared images are the standard for minimizing storage footprint in virtualized desktop deployments.

• ✓

  Use MCS with thin provisioning and shared base images.

  Why this is correct

  Thin provisioning allows for dynamic disk growth, and shared base images mean that multiple VMs point to a single source, saving massive amounts of space. This configuration is the industry standard for optimizing storage capacity in pooled non-persistent environments while still maintaining high performance and simplified management.

• ✗

  Assign a dedicated 100GB disk for user profiles to each VM.

  Why it's wrong here

  Assigning large, static disks to each VM results in massive storage waste, especially in non-persistent environments where user data should be stored elsewhere. This prevents thin provisioning from being effective and forces the organization to purchase expensive, underutilized storage capacity that provides no benefit to the users.

• ✗

  Convert all VDAs to persistent mode to avoid profile management.

  Why it's wrong here

  Persistent mode forces each VM to maintain its own unique state, requiring significant storage for each individual user's OS changes. This negates the storage benefits of pooling and makes image management much more difficult, as updates must be applied to every individual persistent disk rather than a single master image.