Which two tasks can be completed using vSphere LifeCycle Manager? (Choose two.)
Which two tasks can be completed using vSphere LifeCycle Manager? (Choose two.)
vSphere Lifecycle Manager can manage the firmware lifecycle of ESXi hosts that are part of a managed cluster with a single image. Additionally, it can check that the ESXi hosts are compliant with the recommended baseline and update the hosts accordingly. Other options like upgrading VMware vCenter or managing firmware lifecycle using baselines are not tasks that vSphere Lifecycle Manager can perform.
I think it should be A + B, although not 100% sure. B is certainly correct, and looking at https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-774C3626-332C-4C3E-BC9B-AE648E78CA89.html option A also seems valid since the firmware update is mentioned only under "compliance view for a cluster or a standalone host that you manage with a single image"
AB E- NO - in baseline only upgrade, path,extension
Correct A-B
Correct Answer is A and B,. D,E is incorrect because baselines is not support https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A20C2DA-F45F-4C9B-9D17-A89BCB62E6EF.html#the-desired-state-model-2
I think it should be A + B. Compare the operations between Baselines and Images: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A20C2DA-F45F-4C9B-9D17-A89BCB62E6EF.html Firmware updates and Hardware compatibility checks are not supported with baslines (only with iamges). .A - Manage the firmware lifecycle of ESXi hosts that are part of a managed cluster with a single image. - You can do it. B - Check that the ESXi hosts are compliant with the recommended baseline and update the hosts. - You can do it. C - Upgrade VMware vCenter from version 7 to 8. - Haha D - Check the hardware compatibility of the hosts in a cluster against the VMware Compatibility Guide (VCG) using baselines. - You cannot do it with baselines. E - Manage the firmware lifecycle of ESXi hosts are part of a managed cluster using baselines. - You cannot do it with baselines. I hope I don't talk shit.
Is this a trick question? I am confused for this question. After reading, https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-lifecycle-manager/GUID-74295A37-E8BB-4EB9-BFBA-47B78F0C570D.html. I feel that it can do all of the tasks. even for upgrade version 7 to 8. Refer to: https://core.vmware.com/resource/upgrading-vsphere-8#sec22122-sub2
LM doesn't upgrade VC, so C is not right.
I believe its A and D.. Key word is use of image for vCLM. Software & firmware updates happen simultaneously in a single workflow. Specifically, a vLCM Image is a combination of software, drivers, and firmware installs & upgrades all packaged together. When creating an Image, there are 4 potential components you can add: § ESXi version – this component is mandatory; others are optional § Vendor add-on § Firmware and drivers add-on § Any additional components Another advantage of vLCM is the ability to check ESXi Hosts hardware against the VMware Compatibility Guide (VCG).
Yes, you can check the hardware compatibility, but only for vSAN clusters, and with Image profile, not baselines. So D is not correct.
I go for B-E, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-774C3626-332C-4C3E-BC9B-AE648E78CA89.html#:~:text=In%20the%20Image%20pane%20of,ESXi%20hosts%20in%20the%20cluster.
Switching my Answer to A & B, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A20C2DA-F45F-4C9B-9D17-A89BCB62E6EF.html.
AB D is wrong, cause lilecycle manager only checks vsan hardware compatibility (network and storage devices)
B-E https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-774C3626-332C-4C3E-BC9B-AE648E78CA89.html#:~:text=In%20the%20Image%20pane%20of,ESXi%20hosts%20in%20the%20cluster.
vSphere Lifecycle Manager automates the process of validating the hardware compliance of hosts and clusters against a selected ESXi version