For which two reasons would you deploy an IDS sensor in promiscuous mode when designing a security solution? (Choose two.)

Promiscuous mode IDS cannot stop malicious traffic from reaching its destination because it only inspects copies of packets after they have already been forwarded - it has no ability to intercept or drop live traffic.

Denying or dropping packets inline requires the device to be deployed as an IPS in inline mode, where it physically sits in the traffic path; promiscuous mode has no mechanism to block packets.

Because promiscuous mode places the IDS sensor out-of-band to receive only copies of traffic rather than sitting inline in the data path, a sensor failure or reboot does not interrupt network connectivity, making the solution resistant to sensor failure.

Stream normalization requires the sensor to intercept, reassemble, and rewrite TCP streams before forwarding them, which is only possible in inline mode where the sensor controls the actual packet flow.

Promiscuous mode sensors receive full packet copies from a SPAN port or tap, providing all the data needed to compare traffic against known attack signatures, making signature-based pattern matching fully supported in this deployment mode.