2V0-13.25 · Question #50
An architect is designing a VMware Cloud Foundation (VCF) fleet. The following information has been provided by the customer: - Due to budget constraints, the solution must utilize the existing…
The correct answer is B. Use separate vSphere Lifecycle Manager composite images for the management and workload. In VMware Cloud Foundation 9.0, vSphere Lifecycle Manager (vLCM) with composite images is the recommended method for managing host lifecycle. However, when using hardware of different generations, it's not advisable to use a single composite image across clusters with hardware…
Question
An architect is designing a VMware Cloud Foundation (VCF) fleet. The following information has been provided by the customer:
- Due to budget constraints, the solution must utilize the existing
server hardware.
- The existing server hardware consists of server models from the same
vendor but different generations.
- There are ten servers available for use in this solution.
- Management and Business workloads should be hosted in different
clusters. What design decision should the architect make for the lifecycle management of the solution based on this information?
Options
- AUse a single vSphere Lifecycle Manager composite image for the management domain cluster.
- BUse separate vSphere Lifecycle Manager composite images for the management and workload
- CUse vSphere Lifecycle Manager baselines for the management domain cluster.
- DUse a single vSphere Lifecycle Manager composite image for the management and workload
How the community answered
(26 responses)- A12% (3)
- B65% (17)
- C4% (1)
- D19% (5)
Explanation
In VMware Cloud Foundation 9.0, vSphere Lifecycle Manager (vLCM) with composite images is the recommended method for managing host lifecycle. However, when using hardware of different generations, it's not advisable to use a single composite image across clusters with hardware inconsistencies due to potential compatibility mismatches with firmware and drivers. By using separate vLCM composite images for each cluster (i.e., management and workload), the architect ensures that each cluster's image is optimized for its specific hardware generation, reducing the risk of driver/firmware issues during updates or drift remediation. This design aligns with the principle of cluster-level lifecycle independence, especially important when working with a mix of hardware generations.
Topics
Community Discussion
No community discussion yet for this question.