Exam 3V0-21.21 All QuestionsBrowse all questions from this exam
Go to Exam
Question 69

An architect is designing an environment for a retail customer. The design will use a single small vCenter Server Appliance and a cluster of eight ESXi hosts at a remote site. 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. Virtual machine backups at the site will be dependent on the vCenter Server being available.

Which design decision should the architect make to maximize availability for backups?

    Correct Answer: D

    vSphere HA (High Availability) is the best design decision to maximize availability for backups in this scenario. It ensures that if an ESXi host in the cluster fails, the virtual machines, including the vCenter Server Appliance, are restarted on another host in the cluster. This setup runs on the single management network available, thus it aligns perfectly with the given constraint that no additional management networks can be created. Configuring HA to restart virtual machines based on guest OS heartbeat monitoring adds an extra layer of reliability for the availability of virtual machines, including the vCenter Server Appliance, which is critical for VM backups.

Discussion
JoeTromundoOption: D

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

nemisis95

It's B - FT https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-54BD5561-C79E-4845-8C13-AE88C9CB6681.html HA won't provide the availability required.

mnq59986

No and yes - FT requires additional things like dedicated low latency FT network is highly recommended, also VCSA comes with CPU hotplug by default which needs to be disabled for FT and from link provided by you FT is intended for workloads not supporting any other means of clustering for which here VC HA exist. Also to configure FT you need vCenter and I am not sure what happens if it goes down on FT and more importantly, FT protects only for ESXi/HW failure but not when OS fails which HA would solve by heartbeating. So personally I'd go with D.

Aolivera

Ft still requires an extra network. With that restriction only D is possible

c11Option: B

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

AOSpaDesOption: D

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

chistensenOption: B

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

JLF_VMWOption: D

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

hanselOption: A

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

nemisis95

Correct. Also they note "small vCenter Server Appliance" which 4 vCPU which is covered by vSphere Enterprise Plus Licensing The number of vCPUs supported by a single fault tolerant VM is limited by the level of licensing that you have purchased for vSphere. Fault Tolerance is supported as follows: vSphere Standard and Enterprise. Allows up to 2 vCPUs vSphere Enterprise Plus. Allows up to 8 vCPUs

hansel

Difficult one as the document above states "Use a 10-Gbit logging network for FT and verify that the network is low latency. A dedicated FT network is highly recommended. " With the constraint of not being able to create additional management networks at the remote site i thought A and B would be incorrect. C and D don't seem to apply either though. Perhaps B is correct if the recommendation above is ignored

nemisis95Option: D

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"

mrtwinklle

why not FT for VCSA.

nemisis95

A. The solution should utilize dual network connections to eliminate single points of failure E. The solution should allow logs to be retained for a period of 30 days Good point, I'll change my asnwer to B - Fault Tolerance Small vCenter which uses 4 vCPU https://kb.vmware.com/s/article/1024051 In vSphere 6.0, the SMP-FT feature was introduced. 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. A transparent failover occurs if the host running the Primary vCenter Server virtual machine fails, in which case the Secondary vCenter Server virtual machine is immediately activated to replace the failed virtual machine. A new secondary virtual machine is started and Fault Tolerance redundancy is reestablished automatically. Because support of FT for up to 4 virtual CPUs (vCPU) is available only in vSphere 6.0 Enterprise Plus edition, FT can only be used to protect vCenter Server for the tiny and small deployment type, 2 vCPU and 4 vCPU, respectively.

nemisis95

Changed my answer to B - Fault Tolerance

HIC3540Option: D

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.

AlchotOption: B

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

mvojka1990Option: B

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.

mvojka1990

smth to add, just create the vmk using the same subnet as per existing management network, no need to be other network.

TaherShakerOption: D

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

DeiwelOption: B

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)

primanturinOption: B

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."

JLF_VMW

But, FT need a new management network and the question say "It is not possible to create additional management networks at the remote site". I think, if a can do a new management network, the best choice is VC HA...

primanturin

vCenter availability is a priority because of VM backups constrain --> This rolls out option D You can enable FT logging VMkernel using the management network already in placed. Again, it is recommended a dedicated FT network, but it is perfectly supported. I agree with you on your last statement. If it would be possible to create a new management network, the best choice is A (vC HA)