What is one reason for deploying an external VM Direct Engine when deploying PowerProtect Data Manager with PowerProtect DD?

Question

Options

• ANew storage device backups are needed.
• BA File Level Restore is needed.
• CA Hot-Add Mode is needed.
• DAn Instant Access Restore VM is needed.

• A
  4% (1)
• B
  4% (1)
• C
  80% (20)
• D
  12% (3)

Explanation

Hot-Add Mode requires the VM Direct Engine to be deployed as an actual virtual machine (VM) on the VMware infrastructure so it can directly attach and read the target VM's virtual disks without sending data over the network - this transport mode is physically impossible with an internal/embedded engine that isn't itself a VM.

Why the distractors are wrong:

• A (New storage device backups): Adding new storage targets is handled through PPDM's storage configuration, not by deploying an external VM Direct Engine.
• B (File Level Restore): FLR is supported by the internal VM Direct Engine; no external deployment is required.
• D (Instant Access Restore VM): Instant Access mounts backup data directly from PowerProtect DD and can function without an external VM Direct Engine.

Memory tip: Link "Hot-Add" to the idea that you need a real VM to add disks to - the proxy must live inside the VMware environment as a guest VM to perform disk-level hot attachment, which forces an external deployment.

No community discussion yet for this question.