2V0-21.23 Question 41
Select 3An administrator manages a VMware vSphere environment with VMware Distributed Resource Scheduler (DRS) enabled on a cluster. The administrator notices that virtual machines are not being migrated between hosts, even though one of the hosts is heavily utilized. What could be the possible reason?
- A
DRS is set to manual mode, requiring administrator intervention for migrations.
- B
The virtual machines on the heavily utilized host have DRS affinity rules preventing them from being moved.
- C
The cluster is in maintenance mode, which prevents DRS from functioning.
- D
The DRS threshold is set to the most conservative level, minimizing migrations.
- E
The ESXi hosts do not have shared storage configured, which is required for vMotion.
Show answer and explanation
Correct answers: A, B, D
Explanation
VMware Distributed Resource Scheduler (DRS) works by dynamically balancing workloads across hosts in a cluster. If DRS is set to manual mode, migrations must be manually approved, which can prevent automatic load balancing. Affinity rules can also restrict migrations, and a conservative DRS threshold reduces the likelihood of migrations unless there is a significant imbalance. Understanding these factors helps administrators troubleshoot and optimize DRS behavior in their environment.
- A. Correct.
If DRS is set to manual mode, it will only recommend migrations and will not automatically perform them, requiring the administrator to take action. This could explain why virtual machines are not being migrated.
- B. Correct.
Affinity or anti-affinity rules can restrict the movement of virtual machines between hosts, which may prevent DRS from balancing the load effectively.
- C. Incorrect.
While entering maintenance mode does restrict many operations, the scenario does not mention the cluster being in maintenance mode, making this an unlikely cause.
- D. Correct.
A conservative DRS threshold reduces the aggressiveness of migrations, so DRS may not act even when one host is heavily utilized.
- E. Incorrect.
While shared storage is a prerequisite for vMotion, the scenario does not indicate that shared storage is absent, and other operations in the environment would likely fail if this were the case.