Intermittent faults describe problems that appear, disappear, and reappear under the same conditions. In ESD events, a strike can temporarily alter a circuit so it misbehaves for a while and then returns to normal without lasting damage. This can happen due to momentary changes in transistor behavior, a marginal contact that briefly opens or closes, or a charge path that dissipates after power conditions settle. Because the issue isn’t constant and can recur unpredictably, it fits the idea of intermittent damage. If the damage were permanent, the device would fail steadily after the event; if catastrophic, the device would be destroyed. The term inconsistent isn’t the standard way to describe this scenario.

Rogue access points create a network under the attacker's control, so the traffic from users connected to it passes through the attacker’s device. That enables a man-in-the-middle scenario, where the attacker can observe, capture, or even alter the data as it travels between the user and its intended destination. This means credentials, personal information, and session data can be exposed, especially if users don’t rely on strong encryption or if the attacker tricks devices into trusting a fake certificate. In short, the main risk is interception and potential manipulation of traffic between the user and services, which is the essence of a man-in-the-middle attack.

Communications that do not require a pre-established end-to-end connection are described as connectionless. In this mode, each data unit (packet) is sent independently, with no setup of a session or circuit before transmission. Because there’s no handshake or ongoing connection, resources aren’t reserved for the entire exchange, and delivery and ordering aren’t guaranteed by the network. This is typical of IP networks using UDP, where packets can take different routes and arrive out of order or not at all, leaving reliability to higher-layer protocols or applications. In contrast, a connection-oriented approach establishes a session first, providing a stable path and often in-order, reliable delivery (think TCP). Circuit-switched networks create a dedicated path for the duration of the communication. Reliability isn’t about the mode itself; it’s a property that can apply in different modes, but it doesn’t define whether a connection is established.

Datagram communications describe sending data as independent packets without establishing a connection first. UDP is the transport-layer protocol that provides this connectionless, datagram-based service, so this pairing fits best. TCP is connection-oriented and creates a reliable stream rather than discrete datagrams; IP operates at the network layer and, while it routes datagrams, it isn’t the transport service described here; ICMP is for control messages, not delivering application data.