{
  "Module 26: Wireshark & Packet Tools": [
    {
      "question": "1. In Wireshark's Packet Bytes pane, data is presented primarily in:",
      "options": [
        "A. Decimal",
        "B. Hexadecimal",
        "C. ASCII only",
        "D. Binary"
      ],
      "num_answers": 1,
      "answer": "B. Hexadecimal",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ Wireshark shows the raw packet bytes in hexadecimal with an ASCII view alongside.",
        "A": "❌ Decimal is not the primary representation for packet bytes in Wireshark.",
        "C": "❌ ASCII is shown, but the primary raw representation is hex.",
        "D": "❌ Binary is not the default representation in the Packet Bytes pane."
      }
    },
    {
      "question": "2. Which can serve as a CLI packet analyzer akin to Wireshark?",
      "options": [
        "A. Tcpdump",
        "B. John the Ripper",
        "C. Ethereal",
        "D. Nessus"
      ],
      "num_answers": 1,
      "answer": "A. Tcpdump",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ Tcpdump is a command-line packet capture and analysis tool similar to Wireshark.",
        "B": "❌ John the Ripper is a password-cracking tool.",
        "C": "❌ Ethereal was the old name of Wireshark, not a CLI equivalent.",
        "D": "❌ Nessus is a vulnerability scanner, not a packet analyzer."
      }
    },
    {
      "question": "3. What is the best option to monitor and analyze packets on a wireless network in Windows?",
      "options": [
        "A. Airsnort with Airpcap",
        "B. Wireshark with Airpcap",
        "C. Ethereal with Winpcap",
        "D. Wireshark with Winpcap"
      ],
      "num_answers": 1,
      "answer": "B. Wireshark with Airpcap",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ Airpcap provides wireless capture capabilities that Wireshark can use on Windows.",
        "A": "❌ Airsnort is outdated and not the typical Windows GUI packet analyzer.",
        "C": "❌ Ethereal is legacy, replaced by Wireshark.",
        "D": "❌ Winpcap is for wired capture; it doesn’t solve wireless monitor-mode limitations alone."
      }
    },
    {
      "question": "4. You want to show connections from 192.168.0.98 (snort) to 192.168.0.151 (kiwi) on syslog TCP port 514. Which Wireshark filter is most appropriate?",
      "options": [
        "A. tcp.dstport==514 && ip.dst==192.168.0.0/16",
        "B. tcp.srcport==514 && ip.src==192.168.151",
        "C. tcp.srcport==514 && ip.src==192.168.0.98",
        "D. tcp.dstport==514 && ip.dst==192.168.0.151"
      ],
      "num_answers": 1,
      "answer": "D. tcp.dstport==514 && ip.dst==192.168.0.151",
      "answer_keys": ["D"],
      "explanations": {
        "D": "✅ This filter matches packets with destination TCP port 514 and destination IP 192.168.0.151.",
        "A": "❌ This targets the whole /16, not the specific destination host.",
        "B": "❌ This assumes syslog is using source port 514 and has a malformed IP.",
        "C": "❌ This filters on packets sourced from 514, not destined to 514."
      }
    },
    {
      "question": "5. Which tool is used to analyze trace files produced by Wireshark, tcpdump, EtherPeek, and WinDump?",
      "options": [
        "A. Nessus",
        "B. Tcptraceroute",
        "C. OpenVAS",
        "D. Tcptrace"
      ],
      "num_answers": 1,
      "answer": "D. Tcptrace",
      "answer_keys": ["D"],
      "explanations": {
        "D": "✅ Tcptrace analyzes TCP connections in packet capture files and provides connection statistics.",
        "A": "❌ Nessus is a vulnerability scanner, not a PCAP analyzer.",
        "B": "❌ Tcptraceroute is for path discovery, not deep trace analysis.",
        "C": "❌ OpenVAS is also a vulnerability scanner."
      }
    },
    {
      "question": "6. Which Wireshark filter is best to highlight TCP handshake packets (initial connection attempts)?",
      "options": [
        "A. tcp.flags.syn==1",
        "B. tcp.flags.fin==1",
        "C. tcp.flags.rst==1",
        "D. tcp.len==0"
      ],
      "num_answers": 1,
      "answer": "A. tcp.flags.syn==1",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ SYN packets are used to initiate TCP connections and appear in the 3-way handshake.",
        "B": "❌ FIN flags indicate connection teardown, not handshake start.",
        "C": "❌ RST flags indicate abnormal termination or reset of a connection.",
        "D": "❌ tcp.len==0 does not necessarily indicate handshake packets."
      }
    },
    {
      "question": "7. During a TCP 3-way handshake, which packet contains the SYN+ACK flags set?",
      "options": [
        "A. The first packet from the client",
        "B. The second packet from the server",
        "C. The third packet from the client",
        "D. The final FIN packet"
      ],
      "num_answers": 1,
      "answer": "B. The second packet from the server",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ The server responds to the client's SYN with a SYN+ACK, which is the second packet.",
        "A": "❌ The first packet from the client contains SYN only.",
        "C": "❌ The third packet is an ACK from the client confirming the handshake.",
        "D": "❌ FIN is used later to close a TCP connection."
      }
    },
    {
      "question": "8. Which protocol typically uses port 53 and is visible in Wireshark captures for name resolution?",
      "options": [
        "A. DNS",
        "B. FTP",
        "C. Telnet",
        "D. RDP"
      ],
      "num_answers": 1,
      "answer": "A. DNS",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ DNS uses UDP/TCP port 53 for name resolution queries and responses.",
        "B": "❌ FTP uses ports 20 and 21.",
        "C": "❌ Telnet uses port 23.",
        "D": "❌ RDP typically uses port 3389."
      }
    },
    {
      "question": "9. What Wireshark filter shows DNS query packets (requests) only?",
      "options": [
        "A. dns && dns.flags.response==0",
        "B. port 53",
        "C. udp.port==53 && tcp.port==53",
        "D. dns.flags.response==1"
      ],
      "num_answers": 1,
      "answer": "A. dns && dns.flags.response==0",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ DNS packets with response flag 0 are queries (requests).",
        "B": "❌ This shows all traffic on port 53, including responses.",
        "C": "❌ This is not a valid combined filter and is overly broad.",
        "D": "❌ dns.flags.response==1 would show responses, not queries."
      }
    },
    {
      "question": "10. Which protocol sends credentials in clear text and is easily captured with Wireshark if not encrypted?",
      "options": [
        "A. HTTPS",
        "B. SSH",
        "C. Telnet",
        "D. FTPS"
      ],
      "num_answers": 1,
      "answer": "C. Telnet",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ Telnet transmits usernames and passwords in clear text, making them easy to sniff.",
        "A": "❌ HTTPS is encrypted using TLS.",
        "B": "❌ SSH encrypts traffic including credentials.",
        "D": "❌ FTPS (FTP over SSL/TLS) encrypts credentials."
      }
    },
    {
      "question": "11. Which Wireshark filter shows only HTTP GET requests?",
      "options": [
        "A. http.request.method==\"GET\"",
        "B. http.method==GET",
        "C. tcp.port==80",
        "D. http.get==true"
      ],
      "num_answers": 1,
      "answer": "A. http.request.method==\"GET\"",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ This is the correct filter syntax for HTTP GET requests.",
        "B": "❌ This is not valid Wireshark filter syntax.",
        "C": "❌ This shows all HTTP traffic on port 80, not just GET.",
        "D": "❌ http.get is not a standard Wireshark display field."
      }
    },
    {
      "question": "12. What is the default port for HTTPS that you can filter in Wireshark?",
      "options": [
        "A. 80",
        "B. 21",
        "C. 443",
        "D. 110"
      ],
      "num_answers": 1,
      "answer": "C. 443",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ HTTPS typically uses TCP port 443 for secure web traffic.",
        "A": "❌ Port 80 is used for plain HTTP.",
        "B": "❌ Port 21 is used for FTP control.",
        "D": "❌ Port 110 is used for POP3."
      }
    },
    {
      "question": "13. An analyst sees FTP USER and PASS commands in a Wireshark capture. What does this indicate?",
      "options": [
        "A. FTP over SSL is in use",
        "B. Encrypted credentials",
        "C. Plain text authentication",
        "D. Brute-force attack is guaranteed"
      ],
      "num_answers": 1,
      "answer": "C. Plain text authentication",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ Standard FTP sends USER and PASS in clear text, visible directly in the capture.",
        "A": "❌ FTPS would encrypt the credentials.",
        "B": "❌ Encrypted credentials would not show readable USER/PASS commands.",
        "D": "❌ This may or may not be a brute-force attempt; more context is needed."
      }
    },
    {
      "question": "14. Which Wireshark filter shows only UDP traffic?",
      "options": [
        "A. udp",
        "B. udp.flags==1",
        "C. tcp.port==53",
        "D. udp.only"
      ],
      "num_answers": 1,
      "answer": "A. udp",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ The simple filter 'udp' matches all UDP packets.",
        "B": "❌ udp.flags is not a standard field like tcp.flags.",
        "C": "❌ This shows only TCP packets on port 53, not UDP.",
        "D": "❌ 'udp.only' is not a valid Wireshark filter."
      }
    },
    {
      "question": "15. SMTP traffic commonly uses which port that can be filtered in Wireshark?",
      "options": [
        "A. tcp.port==21",
        "B. tcp.port==110",
        "C. tcp.port==25",
        "D. tcp.port==143"
      ],
      "num_answers": 1,
      "answer": "C. tcp.port==25",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ Port 25 is the traditional SMTP port for mail transfer.",
        "A": "❌ Port 21 is FTP control.",
        "B": "❌ Port 110 is POP3.",
        "D": "❌ Port 143 is IMAP."
      }
    },
    {
      "question": "16. Which of the following is a strong indicator of possible malware beaconing in a PCAP file?",
      "options": [
        "A. Repeated DNS TXT requests to suspicious domains",
        "B. Normal HTTP browsing to popular news sites",
        "C. Encrypted TLS traffic to known CDNs only",
        "D. Single ICMP echo request during startup"
      ],
      "num_answers": 1,
      "answer": "A. Repeated DNS TXT requests to suspicious domains",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ Malware often uses DNS TXT or other records to exfiltrate data or receive commands.",
        "B": "❌ Normal browsing is not inherently suspicious.",
        "C": "❌ Legitimate services also use encrypted CDN traffic.",
        "D": "❌ A single ping is not enough to classify as beaconing."
      }
    },
    {
      "question": "17. At which OSI layers does Wireshark primarily help you analyze protocol data?",
      "options": [
        "A. Layer 1 and 2",
        "B. Layer 2 and 3",
        "C. Layer 3 and above",
        "D. Layer 7 only"
      ],
      "num_answers": 1,
      "answer": "C. Layer 3 and above",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ Wireshark decodes IP (Layer 3), TCP/UDP (Layer 4), and many Layer 5–7 protocols.",
        "A": "❌ Layer 1 is physical; Wireshark doesn’t directly show electrical/optical details.",
        "B": "❌ It shows more than just Layers 2 and 3.",
        "D": "❌ It also displays lower-layer headers like IP, TCP, and Ethernet."
      }
    },
    {
      "question": "18. Which Wireshark feature is used to view reassembled TCP data streams in readable form?",
      "options": [
        "A. Follow → TCP Stream",
        "B. Packet Bytes pane",
        "C. Packet Details pane",
        "D. Statistics → IO Graphs"
      ],
      "num_answers": 1,
      "answer": "A. Follow → TCP Stream",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ 'Follow TCP Stream' reconstructs the client–server conversation into a readable flow.",
        "B": "❌ Packet Bytes shows raw bytes of individual packets.",
        "C": "❌ Packet Details shows header fields per packet, not full streams.",
        "D": "❌ IO Graphs are for traffic pattern visualization, not stream reconstruction."
      }
    },
    {
      "question": "19. To detect possible ARP spoofing or poisoning in Wireshark, which filter is most useful?",
      "options": [
        "A. arp.duplicate-address-detected",
        "B. dns && dns.flags.response==0",
        "C. ip.addr==0.0.0.0",
        "D. tcp.flags.syn==1"
      ],
      "num_answers": 1,
      "answer": "A. arp.duplicate-address-detected",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ Duplicate ARP address detection often signals ARP spoofing attempts.",
        "B": "❌ This filter is for DNS queries.",
        "C": "❌ 0.0.0.0 usually appears in DHCP or routing context, not specifically ARP spoofing.",
        "D": "❌ SYN flags indicate connection initiation, not ARP issues."
      }
    },
    {
      "question": "20. If Wireshark repeatedly flags 'TCP Retransmission' messages, what is the most likely cause?",
      "options": [
        "A. Session hijacking",
        "B. Network congestion or packet loss",
        "C. SYN flood attack",
        "D. TLS downgrade attack"
      ],
      "num_answers": 1,
      "answer": "B. Network congestion or packet loss",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ Retransmissions typically indicate packets were lost or delayed in the network.",
        "A": "❌ Session hijacking may alter sequences, but retransmissions alone don’t prove it.",
        "C": "❌ A SYN flood is a DoS pattern, not simply retransmissions of existing sessions.",
        "D": "❌ TLS downgrade attacks involve protocol negotiation, not standard retransmissions."
      }
    },
    {
      "question": "21. Which Wireshark feature provides summarized diagnostics (warnings and potential issues) that can help detect anomalies like slowloris-type behaviors?",
      "options": [
        "A. Statistics → Conversations",
        "B. Follow TCP Stream",
        "C. Expert Information",
        "D. Packet Bytes"
      ],
      "num_answers": 1,
      "answer": "C. Expert Information",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ Expert Information highlights potential protocol problems, unusual delays, and anomalies.",
        "A": "❌ Conversations shows endpoints and flows but not detailed warnings.",
        "B": "❌ Follow TCP Stream is for viewing conversation content.",
        "D": "❌ Packet Bytes shows raw data only."
      }
    },
    {
      "question": "22. Which protocol commonly shows USER, PASS, LIST, and RETR commands in Wireshark?",
      "options": [
        "A. FTP",
        "B. SMTP",
        "C. DNS",
        "D. HTTPS"
      ],
      "num_answers": 1,
      "answer": "A. FTP",
      "answer_keys": ["A"],
      "explanations": {
        "A": "✅ FTP uses commands like USER, PASS, LIST, and RETR for authentication and file operations.",
        "B": "❌ SMTP uses commands like HELO, MAIL FROM, RCPT TO.",
        "C": "❌ DNS uses query/response records, not these commands.",
        "D": "❌ HTTPS encrypts application-layer commands inside TLS."
      }
    },
    {
      "question": "23. Telnet packets captured in Wireshark will typically use which default port?",
      "options": [
        "A. 21",
        "B. 23",
        "C. 22",
        "D. 443"
      ],
      "num_answers": 1,
      "answer": "B. 23",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ Telnet traditionally listens on TCP port 23.",
        "A": "❌ Port 21 is FTP control.",
        "C": "❌ Port 22 is SSH.",
        "D": "❌ Port 443 is HTTPS."
      }
    },
    {
      "question": "24. To extract transferred files (such as HTTP objects) from captured traffic, which Wireshark feature should an analyst use?",
      "options": [
        "A. File → Save As",
        "B. Statistics → Endpoints",
        "C. File → Export Objects",
        "D. Follow UDP Stream"
      ],
      "num_answers": 1,
      "answer": "C. File → Export Objects",
      "answer_keys": ["C"],
      "explanations": {
        "C": "✅ 'Export Objects' allows you to extract files from HTTP, SMB, and other protocols.",
        "A": "❌ 'Save As' saves the capture, not embedded objects.",
        "B": "❌ Endpoints shows hosts/ports, not file contents.",
        "D": "❌ Follow UDP Stream can show data but does not directly export objects."
      }
    },
    {
      "question": "25. You see an HTTP 301 status followed by a redirect to an HTTPS URL in Wireshark. What does this usually indicate?",
      "options": [
        "A. SSL stripping attack is in progress",
        "B. Normal redirection from HTTP to HTTPS for secure access",
        "C. Incorrect DNS configuration",
        "D. TLS handshake failure"
      ],
      "num_answers": 1,
      "answer": "B. Normal redirection from HTTP to HTTPS for secure access",
      "answer_keys": ["B"],
      "explanations": {
        "B": "✅ Many sites use HTTP 301 or 302 to redirect clients from HTTP to HTTPS for secure sessions.",
        "A": "❌ SSL stripping would try to keep the user on HTTP, not redirect to HTTPS.",
        "C": "❌ DNS issues usually show as failed lookups or wrong IPs, not HTTP redirects.",
        "D": "❌ TLS handshake failures appear as TLS alerts, not standard HTTP 301 responses."
      }
    }
  ]
}
