Which two statements about when you install/deploy Cisco Unified Contact Center Enterprise ESXi VMs on VMware ESXI hosts are true? (Choose two.)

Question

Options

• AYou can enable hyper-threading at the hypervisor level.
• BYou cannot enable hyper-threading, but you can over-subscribe the vCPU and vRAM.
• CYou can enable hyper-threading at the Guest OS level.
• DYou can enable hyper-threading at the hypervisor level, but you cannot over-subscribe the vCPU and vRAM.
• EYou cannot enable hyper-threading at the hypervisor level.

• A
  12% (5)
• B
  5% (2)
• C
  79% (34)
• D
  5% (2)

Explanation

When deploying Cisco UCCE VMs on VMware ESXi, Cisco's virtualization guidelines explicitly prohibit enabling hyper-threading at the hypervisor (ESXi/BIOS) level - making E correct - but still permit hyper-threading to be enabled within the Guest OS itself, making C correct. Additionally, Cisco mandates that vCPU and vRAM must not be over-subscribed to ensure deterministic, real-time contact center performance.

Why the distractors are wrong:

• A is wrong because hyper-threading is specifically disallowed at the hypervisor level.
• B is wrong on both counts: hyper-threading at the hypervisor is disallowed and over-subscription is also disallowed.
• D gets the hyper-threading part backwards (says you can enable it at the hypervisor level), even though the over-subscription clause is accurate.

Memory tip: Think of it as a "strict inside, forbidden outside" rule - Cisco locks down the hypervisor layer (no hyper-threading, no over-subscription) to protect performance, but the Guest OS retains its own control over hyper-threading settings. If you see any answer claiming hyper-threading is allowed at the hypervisor level, eliminate it immediately.

No community discussion yet for this question.