Exam 3V0-21.21 topic 1 question 69 discussion

A-WRONG: The vCenter HA network MUST BE ON A DIFFERENT SUBNET than the management network. The three nodes can be on the same subnet or on different subnets. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-9B176C8A-4EEE-4A28-A3C1-24656D6402CF.html B-WRONG: MULTIPLE GIGABIT NETWORK INTERFACE CARDS (NICs) ARE REQUIRED. For each host supporting Fault Tolerance, a minimum of two physical NICs is recommended. For example, you need one dedicated to Fault Tolerance logging and one dedicated to vMotion. Use three or more NICs to ensure availability. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-12E9AF7F-50D0-405D-AFDF-51878E2949AD.html C-WRONG: DRS mainly balance workloads for performance. D-RIGHT: All hosts must have at least one management network in common. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-BA85FEC4-A37C-45BA-938D-37B309010D93.html

B: FT For FT, a dedicated NIC is 'recommended' but it's not a 'requirement'.

First, all of the VMware tests would be better if they hired Alpine or some other professional test dev company with a psychometrician. Many test question stems are incorrectly phrased, the detractors poorly worded, and they allow detractors against VMware's best practices. Keep it in mind when studying. Finally, the correct answer for this question is D, as all hosts have one MGMT network in common.

FT supported for VCSA https://kb.vmware.com/s/article/1024051?lang=en_US&queryTerm=1024051 FT reqs Use a 10-Gbit logging network for FT and verify that the network is low latency. A dedicated FT network is highly recommended. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-57929CF0-DA9B-407A-BF2E-E7B72708D825.html

Create one vmk to the existing PG on vswitch, set the rule of FT, its 10G very good, and put the vcsa vm on FT capabilities, its supported as its 4vcpu, upon the enterprise plus license it works, and thats all.

It is B -Use a 10-Gbit logging network for FT and verify that the network is low latency. A dedicated FT network is highly recommended. Recomended, not mandatory. https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-57929CF0-DA9B-407A-BF2E-E7B72708D825.html

The answer is D from my point of view. Reading the point that says "These is a single 10 GbE connected network" means that there is only one 10 GB Ethernet connected to the ESXi which do not line up with the FT requirements. Multiple gigabit Network Interface Cards (NICs) are required. For each host supporting Fault Tolerance, a minimum of two physical NICs is recommended. For example, you need one dedicated to Fault Tolerance logging and one dedicated to vMotion. Use three or more NICs to ensure availability. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-12E9AF7F-50D0-405D-AFDF-51878E2949AD.html

I think is D Focus: "It is not possible to create additional management networks at the remote site" So, it can't use FT

Es ist Antwort B meinen Recherchen zu folge. Es gibt zudem zwei Funktionen, die ihren Dienst komplett verweigern: vMotion und Storage vMotion sind reinrassige vCenter-Funktionen und fallen damit aus. Folglich ist ein Verschieben von VMs während einer vCenter-Downtime nicht möglich. Gleiches gilt für den Distributed Ressource Scheduler (DRS) ebenso wie für Storage DRS. Das ist nicht weiter verwunderlich, denn die DRS-Funktionalität bedient sich zur Umsetzung der vMotion-Funktion. Wie erwähnt, ist diese bei einem vCenter-Ausfall nicht aktiv und damit auch das DRS komplett offline. Völlig flach fällt außerdem der Update Manager – er ist mittlerweile integraler Bestandteil des vCenters und funktioniert nicht, wenn das vCenter offline ist. Kommen wir zu den Merkmalen, die zum Teil noch funktionieren: Da ist zum einen Fault Tolerance (FT)

I believe is B vCenter availability is a priority because "Virtual machine backups at the site will be dependent on the vCenter Server being available" B - Does FT apply in this case? YES - Small vCenter - 4vCPU (licensing is out of the question) - 10 Gbit for FT - VMware vSphere Fault Tolerance (FT) can be utilized to provide continuous availability for vCenter Server by having identical vCenter Server virtual machines running on separate hosts Possible limitation: "Use a 10-Gbit logging network for FT and verify that the network is low latency. A dedicated FT network is highly RECOMMENDED." > recommended is not a MUST, still SUPPORT D - It could have been 100% correct using DRS + HA... But it is risky with only "vSphere HA and to restart virtual machines based on guest operating system heartbeat monitoring" "The reset statistics are cleared when a virtual machine is powered off then back on, or when it is migrated using vMotion to another host. This causes the guest operating system to reboot, but is not the same as a 'restart' in which the power state of the virtual machine is changed."

I agreed with JoeTromundo because FT need "a 10-Gbit logging network for FT and verify that the network is low latency. A dedicated FT network is highly recommended" and the question say "It is not possible to create additional management networks at the remote site." So, my best choice is D

Isnt B - Fault Tolerance ruled out because of the constraint "There is a single 10 GbE connected network at the remote site to support all management services. It is not possible to create additional management networks at the remote site"? https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-57929CF0-DA9B-407A-BF2E-E7B72708D825.html

D. The cluster will be configured with vSphere HA and set to restart virtual machines based on guest operating system heartbeat monitoring. The vCenter HA network must be on a different subnet than the management network. So this is ruled out by "It is not possible to create additional management networks"