Which three reasons to deploy an IDS sensor in promiscuous mode when you design a security solution are true? (Choose three.)

Because the promiscuous sensor is not inline and only receives mirrored copies of traffic, a sensor failure does not disrupt network connectivity - the network continues to forward traffic unaffected by sensor outages.

Stream normalization requires the sensor to hold, reorder, and reassemble actual packets before forwarding them to defeat evasion techniques, which is only possible when the sensor operates inline in IPS mode with access to the live packet stream.

Promiscuous mode places the sensor entirely outside the forwarding path so it adds zero latency or jitter to live traffic, which is critical for real-time voice applications that are sensitive to any forwarding delay.

An IDS in promiscuous mode can inspect full packet copies and apply deep signature-based pattern matching against known attack patterns, fulfilling the core IDS detection function without affecting original traffic flow.

Blocking or denying packets requires the sensor to be inline in the traffic path where it can intercept and drop packets before delivery; a promiscuous sensor only receives copies and has no ability to prevent the original packet from reaching its destination.