During a requirements gathering workshop, the customer provides the following requirement (REQ) and constraints (CON):
✑ REQ01: The customer is looking for a way to limit database virtual machine (VM) placement to save on CPU licensing costs.
✑ CON01: There is a single cluster with no budget to scale.
✑ CON02: All virtual machines must run on the consolidated cluster.
Which two design decisions should the architect make to meet the customer requirement? (Choose two.)
To limit database VM placement and save on CPU licensing costs while operating within a single cluster with no budget to scale, two design decisions should be made. First, VM-Host affinity rules should be used to ensure the database VMs are always run on specific hosts, which aligns with the need to limit placement and manage licensing costs effectively. Second, using vSphere VM and host DRS groups will enable the grouping of VMs with specific hosts, ensuring that the VMs run only on the designated hosts within the consolidated cluster. Together, these approaches efficiently address the customer's requirements and constraints.
I'd say D and E
D & E. We want to pin the DB VM's to specific host(s) in the cluster.
I agree, must be D & E
I believe that the correct answers are D and E. https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.mscs.doc/GUID-1F39CF51-CDA5-40B7-B5AA-8CBA37C65314.html
The main requirement is to have the VMs running always at the same place to save CPU licences : so the database VMs should always run on the same host(s). A : We don't have any requirement to separate VMs. B: DRS should be in automated mode to always ensure the VMs are running on the right host C : Very heavy solution to do something DRS is able to do D : Yes. We ensure the VMs are running on specific host(s) E : Yes. The VMs and hosts must be placed in related DRS groups