Exam 350-401 topic 1 question 257 discussion

B is correct

In inline mode the NGFW acts as a gatekeeper, analyzing and enforcing policies on all traffic in real-time.

From the option provided, only option 'B' can block traffic. When Inline Pair Mode is in use, packets can be blocked since they are processed inline. When Tap Mode is enabled, a copy of the packet is inspected and dropped internally while the actual traffic goes through FTD unmodified. Inline pair mode is an active mode, Tap mode is a passive mode. https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200924-configuring-firepower-threat-defense-int.html#toc-hId-1297094981:~:text=Yes-,Inline%20Pair,No,-Configure%20Inline%20Pair

B is correct In a Next-Generation Firewall (NGFW), the "inline" mode makes the NGFW actively inspects and filters traffic as it passes through, allowing or blocking flows based on defined security policies.

provided answer is correct

https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200924-configuring-firepower-threat-defense-int.html Check out the table under "Here is a high level overview of the various FTD deployment and interface modes". Tap doesn't exist and Inline Pair is the only mode traffic CAN be dropped in. Of course the question implies its asking what mode will block ALL flows, I suspect that's a grammar problem.

Provided answer is correct

Should be B. In the reference, there is table: "Traffic can be DROPPED" column, inline pair - Yes, inline TAP - No.

B is correct . only inline mode place the FTD in the path of actual data and the FTD can drop packets. Inline Tap just log the bad packets but do not disturb the flow . and passive mode FTD is sit out of the data path and receive mirrored data from SPAN port.

should be D. INLINE allows those traffic from paired interfaces. INLINE TAP blocks all traffic. PASSIVE does nothing on traffics, allows all.

Answer B is correct for every sort of firewall. if it is not INLINE in the traffic it cannot block anything.

https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200924-configuring-firepower-threat-defense-int.html#anc4