Which Docker networking construct connects container interfaces to a parent host interface (or sub-interfaces)?

Which Docker networking construct connects container interfaces to a parent host interface (or sub-interfaces)?

• A. Bridge
• B. MACVLAN
• C. Overlay
• D. Host Driver

Answer: (B)

This tests how Docker can attach a container’s network to a real path on the host. MACVLAN is the driver that connects each container to a specific parent network interface on the host (for example, eth0) and can work with sub-interfaces such as VLANs. With MACVLAN, each container gets its own MAC address on the same layer-2 network as the host, so the container appears as a separate device on the physical LAN and can be routed or segmented just like a physical host. That direct linkage to the host’s interface (or its sub-interfaces) is what makes MACVLAN the right fit for this scenario. In contrast, the bridge driver uses a virtual bridge on the host, the overlay driver connects containers across multiple hosts via encapsulation, and the host driver shares the host’s network namespace without creating separate NICs for containers.

This tests how Docker can attach a container’s network to a real path on the host. MACVLAN is the driver that connects each container to a specific parent network interface on the host (for example, eth0) and can work with sub-interfaces such as VLANs. With MACVLAN, each container gets its own MAC address on the same layer-2 network as the host, so the container appears as a separate device on the physical LAN and can be routed or segmented just like a physical host. That direct linkage to the host’s interface (or its sub-interfaces) is what makes MACVLAN the right fit for this scenario. In contrast, the bridge driver uses a virtual bridge on the host, the overlay driver connects containers across multiple hosts via encapsulation, and the host driver shares the host’s network namespace without creating separate NICs for containers.