An administrator is working on reclamation options in a virtualization environment and has discovered that a Powered-Off VM (SRV-A) is showing as a candidate for reclamation. The administrator…

Question

Options

• AUnregister SRV-A from vCenter when it was powered-off, and register before power-on.
• BDelete SRV-A and virtual disks from vCenter.
• CNo action is needed. It should remain as an SRV-A in vCenter.
• DExclude SRV-A from reclamation.

• A
  5% (1)
• B
  11% (2)
• D
  84% (16)

Explanation

Excluding SRV-A from reclamation (D) is the correct and targeted solution - it tells the virtualization platform (e.g., VMware Aria Operations/vROps) to explicitly ignore this VM as a reclamation candidate, preserving it while acknowledging its legitimate but infrequent use pattern.

Why the distractors fail:

• A is operationally reckless - unregistering and re-registering a VM monthly risks losing inventory metadata, snapshot history, and policy associations, and solves nothing about reclamation logic.
• B is destructive - deleting the VM and its disks permanently removes the workload, which is the exact outcome the administrator is trying to prevent.
• C is incorrect because inaction leaves SRV-A vulnerable; without an explicit exclusion, an automated process or another admin could act on the reclamation recommendation.

Memory tip: Think of "Exclude" as a whitelist exception - when a VM is legitimate but looks suspicious to automation, you don't hide it or destroy it, you formally tell the system "I know about this one, hands off." If the answer involves preserving something unusual, look for the exclusion/exception option first.

No community discussion yet for this question.