What is a characteristic of Firepower NGIPS inline deployment mode?

Question

Options

• AIt cannot take actions such as blocking traffic.
• BASA with Firepower module cannot be deployed.
• Cit must have inline interface pairs configured.
• DIt is out-of-band from traffic.

• A
  4% (2)
• B
  2% (1)
• C
  90% (44)
• D
  4% (2)

Explanation

In inline deployment mode, the Firepower NGIPS sits directly in the path of live traffic, which requires inline interface pairs - two interfaces that act as a "bump in the wire," receiving traffic on one and forwarding it out the other after inspection.

Why the distractors are wrong:

• A is incorrect because inline mode can actively block traffic - that's its primary advantage over passive modes; it performs full prevention, not just detection.
• B is incorrect because ASA with Firepower module can be deployed inline; it's a common and supported deployment scenario.
• D describes passive (SPAN/tap) mode, not inline mode - passive deployments receive a copy of traffic out-of-band and cannot block anything.

Memory tip: Think of "inline" literally - the sensor is in the line of traffic, so it needs paired interfaces (in + out). If it's out-of-band, it's passive. Inline = pairs = prevention; Passive = copy = detection only.

No community discussion yet for this question.