Captive Portal, PDP and PEP run in what space?

Question

Options

• AKernel
• BUser
• CCPM
• DFWD

• A
  3% (1)
• B
  94% (30)
• D
  3% (1)

Explanation

Captive Portal, PDP (Policy Decision Point), and PEP (Policy Enforcement Point) run in user space because they are application-layer processes - they handle authentication logic, policy decisions, and enforcement coordination at the software level, not at the low-level hardware/OS interface level. User space is the appropriate execution environment for these higher-level security daemons and services.

Why the distractors are wrong:

• A. Kernel - Kernel space handles raw packet inspection and low-level forwarding; it's not where policy decision logic or web-based portals operate, as those require OS services and higher-level networking.
• C. CPM - CPM (Check Point Management) is a specific process/component, not an execution space; it's a distractor that sounds architectural but doesn't describe a process space.
• D. FWD - FWD (the Firewall Daemon) is itself a user-space process, not a space category; confusing a daemon name with an execution environment is the trap here.

Memory tip: Think of the split as "brains vs. brawn" - the kernel is the brawn (fast, raw packet handling), while user space is the brains (decisions, portals, policy logic). Captive Portal, PDP, and PEP all think and decide, so they live in user space.

No community discussion yet for this question.