What is the primary function of a stateful firewall policy in Fabric Composer?

Question

Options

• ABlocking HTTP traffic
• BAuthenticating users
• CInspecting packet headers and maintaining connection state
• DProviding DNS resolution

• A
  4% (2)
• C
  95% (53)
• D
  2% (1)

Explanation

Option C is correct because a stateful firewall operates by inspecting packet headers (source/destination IPs, ports, protocols) and tracking the state of active connections - meaning it remembers whether a packet belongs to an established, legitimate session rather than treating each packet in isolation. In Fabric Composer, stateful firewall policies use this connection-tracking mechanism to make intelligent allow/deny decisions based on traffic context.

Why the distractors are wrong:

• A (Blocking HTTP) - that describes a specific rule action (blocking a protocol), not a firewall's primary function; stateful firewalls can permit or block any protocol.
• B (Authenticating users) - authentication is handled by identity/AAA services (e.g., RADIUS, LDAP), not firewall policies.
• D (DNS resolution) - DNS is a separate network service entirely, unrelated to packet filtering or state tracking.

Memory tip: Think "stateful = state-aware." A stateful firewall remembers conversations - if your machine initiated the connection, return traffic is automatically trusted. Contrast with a stateless firewall, which checks every packet blindly against static rules, with no memory of prior packets.

No community discussion yet for this question.