CV0-003 · Question #148
A company has purchased two new servers to host several virtualized database servers. Each server has two 3GHz quad-core processors each, 64GB RAM each, 200GB DAS, and two 10GbE NICs each. Which of…
The correct answer is D. NIC. With several virtualized database servers sharing only two physical NICs, the network adapters become the bottleneck as bandwidth is divided among all guest VMs. The SAN option is a distractor because these servers use DAS, not SAN.
Question
A company has purchased two new servers to host several virtualized database servers. Each server has two 3GHz quad-core processors each, 64GB RAM each, 200GB DAS, and two 10GbE NICs each. Which of the following is the MOST likely bottleneck for these systems?
Options
- AProcessors
- BSAN
- CRAM
- DNIC
How the community answered
(25 responses)- A8% (2)
- B16% (4)
- C4% (1)
- D72% (18)
Why each option
With several virtualized database servers sharing only two physical NICs, the network adapters become the bottleneck as bandwidth is divided among all guest VMs. The SAN option is a distractor because these servers use DAS, not SAN.
Two quad-core 3GHz processors provide 8 physical cores per server, which is adequate headroom for hosting several virtualized workloads.
The servers are equipped with DAS (Direct Attached Storage), not a SAN, so SAN cannot be the bottleneck for hardware that does not exist in this configuration.
64GB of RAM per server is a substantial amount that provides sufficient memory for distributing among several guest VMs.
Multiple guest VMs sharing two physical 10GbE NICs means available bandwidth is split across all guests simultaneously. Database workloads generate significant network traffic for queries and responses, so two shared physical NICs become the constraining resource when several VMs compete for throughput.
Concept tested: NIC bandwidth as virtualization bottleneck
Source: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-hyper-v-networking-in-windows-server
Topics
Community Discussion
No community discussion yet for this question.