What type of VM/Host rule must be configured to keep domain controllers running on separate ESXi hosts?

To ensure that domain controllers are running on separate ESXi hosts, the appropriate VM/Host rule to configure is one that specifies the separation of virtual machines. This type of rule is specifically designed to prevent specified virtual machines from being placed on the same host, thereby enhancing availability and fault tolerance.

By implementing a “Separate Virtual Machine” rule, it guarantees that each domain controller, which is critical for the Active Directory infrastructure, operates on a distinct ESXi host. This configuration minimizes the risk of a single point of failure, as the failure of one host would not impact all domain controllers. This level of separation is crucial for maintaining service continuity and ensuring high availability of essential services.

In contrast, other types of rules you might consider—such as those that group virtual machines together or link virtual machines to the same host—would not achieve the goal of keeping domain controllers isolated. For example, using a rule that keeps virtual machines together could inadvertently place multiple domain controllers on the same host, which is counterproductive to the desired outcome.