Apply a Protection Policy to a Virtual Machine Created on a vVol POWERSTORE-OPERATE Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A storage admin applied a protection policy to a vVol-backed VM using PowerStore Manager. The policy is named 'Hourly-24h'. The admin checks the vVol's properties and confirms the policy is listed. However, after 24 hours, no snapshots have been created. What is the most likely reason?

   • AThe storage container has reached its maximum number of snapshots.
   • BThe VM is powered off, so snapshots cannot be taken.
   • CThe policy's snapshot schedule is not enabled, or the policy has no snapshot rule configured.
   • DThe vVol is not large enough to store snapshots.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A company is setting up a new vVol environment. They have created a storage container and registered the VASA provider. However, when they try to create a VM on a vVol datastore, the datastore does not appear in vCenter. What is the most likely cause?

   • AA default protection policy has not been set on the storage container.
   • BThe storage container has not been mounted as a datastore to the ESXi hosts via the VASA provider.
   • CThe VASA provider is not compatible with the version of vCenter being used.
   • DThe ESXi hosts do not have the PowerStore NFS client installed.
   Reveal Solution Discussion Select an answer first
4. 3expert · medium

   A company has a vVol-backed VM that is currently protected by a policy named 'Standard' with daily snapshots. The VM is running a critical application, and the team wants to switch to a policy named 'Critical' with 15-minute snapshots. However, the 'Critical' policy is currently applied to another VM in the same storage container. What is the correct way to apply the 'Critical' policy to the new VM?

   • ACreate a new policy named 'Critical-2' with the same settings and apply it to the new VM.
   • BApply the 'Critical' policy to the storage container as the default, then migrate the new VM to a new vVol in that container.
   • CModify the vVol's protection policy in PowerStore Manager, selecting 'Critical' from the list of available policies.
   • DRemove the 'Critical' policy from the other VM first, then apply it to the new VM.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   After applying a protection policy to a vVol-backed VM, where can an administrator verify that the policy is active?

   • AIn the ESXi host's configuration file
   • BIn PowerStore Manager under the VM's protection details
   • CIn the vSphere Client under the VM's storage policies tab
   • DIn the PowerStore system's syslog
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   An administrator wants to create a VM on a vVol datastore in a vSphere environment. Which two prerequisites must be in place before the VM can be created?

   • AThe vVol datastore must be formatted with VMFS and the VM must be created using the vSphere Web Client.
   • BA storage container must be configured on the PowerStore system and registered as a vVol datastore in vCenter Server.
   • CThe vSphere host must have a dedicated physical HBA for each vVol datastore and the storage container must be mapped to a single host.
   • DThe PowerStore system must be configured with NFS exports and the vVol datastore must be mounted via NFS.
   Reveal Solution Discussion Select an answer first