One advantage of an application-level firewall is the ability to

Question

Options

• Afilter packets at the network level.
• Bfilter specific commands, such as http:post.
• Cretain state information for each packet.
• Dmonitor tcp handshaking.

• A
  9% (2)
• B
  82% (18)
• C
  5% (1)
• D
  5% (1)

Explanation

Application-level firewalls (also called proxy firewalls) operate at Layer 7 of the OSI model, giving them deep visibility into application protocols - which is precisely why B is correct: they can inspect and filter specific application commands like HTTP POST, HTTP GET, or FTP PUT, blocking dangerous operations that lower-level firewalls can't even parse.

Why the distractors are wrong:

• A is wrong because packet-level filtering is the job of a packet-filtering firewall (Layer 3/4), not an application-level one.
• C is wrong because retaining state per packet describes a stateful inspection firewall, which tracks TCP session state but doesn't reach into application content.
• D is wrong because monitoring TCP handshaking (SYN/SYN-ACK/ACK) is also a stateful firewall capability, not unique to application-level firewalls.

Memory tip: Think "application = app commands." If the firewall understands the language of the app (HTTP, FTP, SMTP verbs), it's application-level - the key giveaway on the exam is any mention of specific protocol commands or content inspection.

No community discussion yet for this question.