Which of the following is NOT listed as a followable data stream type in Wireshark in the material?

• A. DNS Stream
• B. UDP Stream
• C. TCP Stream
• D. SSL Stream

Answer: (D)

When you use Wireshark to follow a data stream, you’re asking the tool to reconstruct the bytes exchanged in a conversation so you can see the whole request/response sequence in order. This works well for protocols that carry a continuous stream or discrete exchanges across a single connection, like TCP, UDP, and certain higher‑level protocols such as DNS that can be viewed as a single transaction.

In the material, DNS Stream, UDP Stream, and TCP Stream are given as followable types, because those protocols naturally produce a coherent, readable sequence you can reconstruct from the captures. SSL (TLS) traffic, however, is encrypted. Even if Wireshark offers a follow option for TLS/SSL, the content isn’t readable in plaintext without decrypting the traffic with the proper keys. Because the material is focusing on what can be followed to view readable data, SSL/TLS isn’t listed as a followable data stream type there. If you do follow TLS/SSL in a modern version of Wireshark, you’ll see the TLS records and handshake structure, but the application data remains encrypted unless you decrypt it.