Which two factors cause broadcast amplification in virtualized (VM) environments?

Broadcast amplification in virtualized environments occurs due to two primary factors. First, the Layer 2 domain can be significantly larger in virtual machine environments compared to physical networks. A single vSwitch might connect numerous VMs, all residing within the same broadcast domain. This means that a single broadcast packet needs to be delivered to a much larger number of potential recipients. Second, virtual machines, like physical hosts, rely heavily on broadcast communication for various essential functions, such as ARP requests to resolve IP addresses to MAC addresses, DHCP requests for IP address assignment, and neighbor discovery protocols. When these broadcasts occur in a large Layer 2 domain, the vSwitch must replicate and forward them to all connected VMs, leading to amplified broadcast traffic and increased CPU utilization on the hypervisor. The other options are incorrect: vSwitch interrupting the server CPU to process broadcast packets is a consequence of broadcast amplification, not a cause. Communication between vSwitch and network switch is typically unicast, multicast, or broadcast, but the primary communication method is not broadcast-based, and this interaction doesn't directly cause amplification within the virtual environment itself. Communication between vSwitch and network switch is not primarily multicast-based for general data plane traffic.