nerdexam
Cisco

352-001 · Question #684

Which statement about TAP and TUN devices, which are used in a Linux/KVM cloud deployment model, is true?

The correct answer is A. TUN is for handing IP packets, but TAP is for handing Ethernet frames. TUN and TAP are Linux virtual network devices that differ by OSI layer: TUN handles Layer 3 IP packets while TAP handles Layer 2 Ethernet frames.

Network Virtualization

Question

Which statement about TAP and TUN devices, which are used in a Linux/KVM cloud deployment model, is true?

Options

  • ATUN is for handing IP packets, but TAP is for handing Ethernet frames.
  • BTUN is for handing Ethernet frames, but TAP is for handing IP packets.
  • CTUN is for tunneling IP packets, but TAP is for tapping IP packets.
  • DTUN is for tunnelingEthernet frames, but TAP is for tapping Ethernet frames.

How the community answered

(35 responses)
  • A
    91% (32)
  • B
    3% (1)
  • C
    6% (2)

Why each option

TUN and TAP are Linux virtual network devices that differ by OSI layer: TUN handles Layer 3 IP packets while TAP handles Layer 2 Ethernet frames.

ATUN is for handing IP packets, but TAP is for handing Ethernet frames.Correct

TUN (tunnel) is a Layer 3 virtual device that processes raw IP packets, making it suitable for IP-level tunneling such as VPNs. TAP (network tap) is a Layer 2 virtual device that processes full Ethernet frames, simulating a physical NIC and supporting protocols that operate below IP.

BTUN is for handing Ethernet frames, but TAP is for handing IP packets.

This reverses the correct association - TUN operates at Layer 3 with IP packets, not Ethernet frames, and TAP operates at Layer 2 with Ethernet frames, not IP packets.

CTUN is for tunneling IP packets, but TAP is for tapping IP packets.

The TUN/TAP distinction is not about tapping versus tunneling but about the OSI layer each device operates at - both can be used for tunneling depending on the use case.

DTUN is for tunnelingEthernet frames, but TAP is for tapping Ethernet frames.

TUN processes IP packets at Layer 3, not Ethernet frames, and TAP processes Ethernet frames at Layer 2 - this choice incorrectly reassigns both devices to the wrong layer and function.

Concept tested: Linux TUN/TAP virtual interface OSI layer distinction

Source: https://www.kernel.org/doc/html/latest/networking/tuntap.html

Topics

#TAP device#TUN device#Linux KVM#virtual networking

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice