Question
You have the servers shown in the following table.
| Name | Role |
|------|------|
| Server1 | Hyper-V |
| Server2 | Hyper-V |
| Server3 | DHCP Server |
Server1 contains a virtual machine named VM1 that runs Windows Server. Server1 has an external switch named Switch1. VM1 is connected to Switch1.
You provision containers on VM1.
You need to configure networking for VM1. The solution must meet the following requirements:
• Ensure that Server3 automatically assigns IP addresses to the containers.
• Ensure that the containers can communicate with Server2.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Explanation
On the network adapter for VM1, enable: MAC address spoofing — The containers inside VM1 each use their own MAC address. By default, the Hyper-V switch port on Server1 forwards only frames whose source MAC matches VM1's adapter, so container traffic would be dropped. Microsoft documents that the transparent network driver requires MAC address spoofing when the container host is a virtual machine. DHCP guard drops DHCP server messages sent from a VM, and Router guard drops router advertisement and redirect messages; neither lets the containers' traffic through.
On the container for VM1, set the network driver type to: Transparent — Containers on a transparent network connect directly to the physical network through an external Hyper-V switch, and their IP addresses come from the physical network either statically or dynamically from an external DHCP server. This lets Server3 assign their addresses and lets them reach Server2 directly. The l2bridge (Bridge) driver rewrites container traffic to the host's MAC address, and its IP addresses are allocated by the Host Networking Service from a provided subnet prefix, not by an external DHCP server. Overlay is for multi-host swarm or Kubernetes clusters, uses VXLAN encapsulation, and gets its addresses from swarm-managed prefixes.
