nerdexam
Cisco

500-440 · Question #42

Which statement about when you deploy Cisco Unified CCE on UCS B/C Tested Reference Design TRC servers where each physical CPU core is mapped 1-1 with a vCPU is true?

The correct answer is B. You cannot overload/over-subscribe the vCPU/cores on the UCS servers even if you do not over-. Option B is correct because Cisco's UCS B/C Tested Reference Configuration (TRC) is a validated design where the 1:1 physical core-to-vCPU mapping is a hard constraint - oversubscribing CPU resources violates the tested configuration and can introduce latency and…

Design Cisco Unified CCE Deployment

Question

Which statement about when you deploy Cisco Unified CCE on UCS B/C Tested Reference Design TRC servers where each physical CPU core is mapped 1-1 with a vCPU is true?

Options

  • AYou can overload/over-subscribe the vCPU/cores on the UCS servers as long as you do not over-
  • BYou cannot overload/over-subscribe the vCPU/cores on the UCS servers even if you do not over-
  • CYou can overload/over-subscribe the vCPU/cores on the UCS servers as long as the memory
  • DYou can overload/over-subscribe the vCPU/cores on the UCS servers as long as the total CPU

How the community answered

(17 responses)
  • B
    94% (16)
  • D
    6% (1)

Explanation

Option B is correct because Cisco's UCS B/C Tested Reference Configuration (TRC) is a validated design where the 1:1 physical core-to-vCPU mapping is a hard constraint - oversubscribing CPU resources violates the tested configuration and can introduce latency and unpredictability that is unacceptable in real-time contact center environments.

Options A, C, and D are all distractors that attempt to introduce conditional exceptions (e.g., "as long as memory isn't oversubscribed," "as long as memory requirements are met," or "as long as total CPU stays below a threshold"), but no such exception exists in the TRC - CPU oversubscription is prohibited unconditionally regardless of memory or aggregate utilization figures.

Memory tip: Think of TRC as a "no exceptions" contract with Cisco - the "T" in TRC stands for Tested, meaning any deviation (including CPU oversubscription) moves you outside the tested and supported boundary. When you see "TRC + 1:1 core mapping," the answer is always "no oversubscription, period."

Topics

#vCPU allocation#UCS TRC deployment#resource constraints#CCE architecture

Community Discussion

No community discussion yet for this question.

Full 500-440 Practice