Which two statements about installation and deployment of Cisco UCCE VMs on VMware ESXi hosts are true? (Choose two.)

Question

Options

• AYou cannot enable hyper-threading at the hypervisor level.
• BDisable hyper-threading, but you can over-subscribe the vCPU and vRAM.
• CEnable hyper-threading at the Guest OS level.
• DEnable hyper-threading at the hypervisor level.
• EEnable hyper-threading at the hypervisor level, but you cannot over-subscribe the vCPU and vRAM.

• A
  88% (21)
• B
  8% (2)
• E
  4% (1)

Explanation

For Cisco UCCE deployments on VMware ESXi, hyper-threading must be disabled at the hypervisor (ESXi host) level because UCCE is a real-time contact center workload that demands dedicated, predictable CPU cycles - allowing ESXi to schedule vCPUs onto hyper-threaded logical cores introduces CPU contention that degrades call processing performance. Option C is correct because, separately, hyper-threading can be enabled within the Guest OS itself, as that setting controls how the guest OS perceives and schedules its own virtual CPUs, which doesn't carry the same risk as HT at the physical scheduler level.

Why the distractors are wrong:

• B is wrong because while disabling HT is correct, UCCE strictly prohibits over-subscribing vCPU and vRAM - Cisco mandates 1:1 pCPU-to-vCPU ratios and no memory ballooning.
• D is the direct opposite of the correct guidance - enabling HT at the hypervisor level is exactly what you must avoid.
• E gets the "no over-subscription" part right but fails by saying to enable HT at the hypervisor level, which is still forbidden.

Memory tip: Think of it as "Hyper-threading: Outside No, Inside Yes" - UCCE bans HT at the outside (hypervisor/hardware) level to protect real-time performance, but allows it inside the guest OS. The over-subscription rule is a separate absolute restriction that eliminates B and any answer that permits it.

No community discussion yet for this question.