SK0-003 · Question #740
A hypervisor has 4GB of RAM, 1TB of RAID 5 SATA storage, two Xeon 2.4GHz Quad Core Processors, and four gigabit NIC cards. The hypervisor is running twelve guest operating systems and users are…
The correct answer is B. RAM. The question asks to identify the most likely bottleneck causing slow response times for twelve guest operating systems on a hypervisor with specific hardware resources.
Question
A hypervisor has 4GB of RAM, 1TB of RAID 5 SATA storage, two Xeon 2.4GHz Quad Core Processors, and four gigabit NIC cards. The hypervisor is running twelve guest operating systems and users are reporting slow response times. Which of the following is MOST likely the cause?
Options
- AProcessor
- BRAM
- CHDD
- DNIC
How the community answered
(35 responses)- A20% (7)
- B69% (24)
- C6% (2)
- D6% (2)
Why each option
The question asks to identify the most likely bottleneck causing slow response times for twelve guest operating systems on a hypervisor with specific hardware resources.
Two Xeon 2.4GHz Quad Core Processors (total 8 cores) are generally adequate for twelve guest operating systems, making the processor less likely to be the primary cause of system-wide slow response times.
With only 4GB of RAM for twelve guest operating systems, memory is the most significant bottleneck. Each guest OS, along with the hypervisor itself, requires a certain amount of RAM, and 4GB is grossly insufficient, leading to excessive swapping to disk and severe performance degradation for all virtual machines.
While RAID 5 SATA storage might not be the fastest, it is less likely to be the most critical bottleneck compared to severely under-allocated RAM for twelve VMs.
Four gigabit NIC cards provide substantial network bandwidth, making network capacity an unlikely primary cause for overall slow response times for the hypervisor and its guests.
Concept tested: Virtualization resource allocation bottlenecks
Source: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-hyper-v-on-windows-server
Topics
Community Discussion
No community discussion yet for this question.