Which of the following are differences between AppArmor and SELinux? (Choose TWO correct answers)

Question

Options

• AAppArmor is implemented in user space only. SELinux is a Linux Kernel Module.
• BAppArmor is less complex and easier to configure than SELinux.
• CAppArmor neither requires nor allows any specific configuration. SELinux must always be
• DSELinux stores information in extended file attributes. AppArmor does not maintain file specific
• EThe SELinux configuration is loaded at boot time and cannot be changed later on. AppArmor

• B
  94% (48)
• C
  4% (2)
• E
  2% (1)

Explanation

B and D are correct because AppArmor genuinely uses a simpler, path-based profile system that most admins find far more approachable than SELinux's complex label-based mandatory access control (MAC), which requires writing and managing detailed policy modules. Additionally, SELinux stores security context labels directly in a file's extended attributes (security.selinux xattr), which means every labeled file carries that metadata on disk - AppArmor has no such per-file storage mechanism; it simply matches actions against path-based profiles.

Why the distractors fail:

• A is backwards - both AppArmor and SELinux are Linux Security Modules (LSMs) operating in kernel space; neither is purely user-space.
• C is false - AppArmor absolutely requires profile configuration to restrict applications; without profiles, applications run unconfined.
• E is false - SELinux policies and enforcement modes can be changed at runtime (e.g., setenforce 0 switches to permissive mode without rebooting); AppArmor profiles can similarly be loaded or removed dynamically.

Memory tip: Use the initials - AppArmor = Accessible (simpler paths), SELinux = Stored labels (xattrs on files). If you remember "SELinux labels stick to files," option D locks in immediately.

No community discussion yet for this question.