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

This answer reverses the correct association - TUN handles Layer 3 IP packets and TAP handles Layer 2 Ethernet frames, not the other way around.

TUN (network TUNnel) is a virtual kernel interface that simulates a Layer 3 point-to-point device and processes raw IP packets, while TAP (network TAP) simulates a Layer 2 Ethernet interface and processes complete Ethernet frames including MAC headers - this Layer 2 vs Layer 3 distinction determines which virtual interface type is used when connecting VMs to virtual networks in KVM deployments.

TUN handles IP packets at Layer 3, not Ethernet frames, and TAP does not perform packet capture tapping in the network analysis sense - it emulates a full Layer 2 Ethernet adapter.

TUN and TAP do not both handle IP packets; TAP operates at Layer 2 and processes Ethernet frames, making the premise that both deal with IP packets incorrect.