An architect is responsible for the availability design of a solution. The following information has been provided: - Virtual machines (VMs) run 8 or less vCPUs - All hosts have a minimum of two…

Question

Options

• AvSphere High Availability Restart Priority set to default at the cluster level
• BvSphere NIC Teaming policy: Route based on originating port ID set on the distributed port group
• CvSphere Fault Tolerance configured on the virtual machines
• DvSphere Round Robin storage multi-pathing policy set on each ESXi host
• EVMware Tools configured to automatically update on reboot for all virtual machines
• FDynamic Link Aggregation (LACP) configured on the distributed virtual switch

• A
  4% (1)
• B
  56% (15)
• C
  4% (1)
• E
  26% (7)
• F
  11% (3)

Explanation

vSphere High Availability Restart Priority set to default at the cluster level This option ensures that vSphere HA will automatically restart the virtual machines (VMs) on another available host in the cluster if a host fails. Setting the restart priority at the cluster level ensures that the VMs are restarted in an order that helps maintain the availability of critical workloads first, enhancing the overall availability during a host failure. vSphere NIC Teaming policy: Route based on originating port ID set on the distributed port group This setting for NIC Teaming ensures that network traffic is distributed effectively across the NICs, improving network availability. In the event of a failure of one physical switch or NIC, the Route based on originating port ID policy ensures that network connectivity for the VMs is maintained via the remaining NICs, enhancing network resilience. vSphere Round Robin storage multi-pathing policy set on each ESXi host Setting the Round Robin storage multi-pathing policy helps distribute I/O across multiple paths to the storage system, ensuring that VM storage remains highly available. If one path fails, traffic is automatically rerouted to other available paths, ensuring minimal disruption to VM storage and improving overall availability in the event of storage path failures.

No community discussion yet for this question.