Question 398 of 997
System HardeningeasyMultiple ChoiceObjective-mapped

Checking AppArmor Profiles on a Node Using aa-status

This CKS practice question tests your understanding of system hardening. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: appArmor. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which kubectl command is used to check whether AppArmor is enabled and which profiles are loaded on a node?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

aa-status

AppArmor is a Linux Security Module (LSM) enforced at the node level, not a Kubernetes resource. Kubernetes does not expose AppArmor status via kubectl. To check whether AppArmor is enabled and which profiles are loaded, you must execute `aa-status` directly on the node (e.g., via SSH). This command queries the AppArmor kernel module and lists all loaded profiles. Therefore, while the question asks for a 'kubectl command,' the correct approach is to use a node-level command like `aa-status`.

Key principle: AppArmor

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • kubectl get seccomp

    Why it's wrong here

    This is for seccomp, not AppArmor.

  • kubectl get apparmor

    Why it's wrong here

    There is no kubectl command for AppArmor. AppArmor is a node-level feature.

  • aa-status

    Why this is correct

    Correct. aa-status shows AppArmor status and loaded profiles.

    Related concept

    AppArmor

  • systemctl status apparmor

    Why it's wrong here

    This shows if the AppArmor service is running, but does not list loaded profiles.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume AppArmor can be managed like a Kubernetes resource using kubectl, but it is a node-level security module that must be checked with Linux-native commands, not Kubernetes API objects.

Trap categories for this question

  • Command / output trap

    There is no kubectl command for AppArmor. AppArmor is a node-level feature.

Detailed technical explanation

How to think about this question

AppArmor operates as a mandatory access control (MAC) system using Linux Security Modules (LSM), and its profiles are stored in `/etc/apparmor.d/`. The `aa-status` command reads from the kernel's AppArmor interface (via `/sys/kernel/security/apparmor/`) to report the current enforcement mode and loaded profiles. In Kubernetes, AppArmor is applied to pods using annotations like `container.apparmor.security.beta.kubernetes.io/<container_name>`, but the node must have the corresponding profile loaded for it to work; `aa-status` is the definitive way to verify this.

KKey Concepts to Remember

  • AppArmor
  • aa-status
  • kubectl

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

AppArmor

Real-world example

How this comes up in practice

A practitioner preparing for the CKS exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. AppArmor Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Review appArmor, then practise related CKS questions on the same topic to reinforce the concept.

Related practice questions

Related CKS practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CKS practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CKS question test?

System Hardening — This question tests System Hardening — AppArmor.

What is the correct answer to this question?

The correct answer is: aa-status — AppArmor is a Linux Security Module (LSM) enforced at the node level, not a Kubernetes resource. Kubernetes does not expose AppArmor status via kubectl. To check whether AppArmor is enabled and which profiles are loaded, you must execute `aa-status` directly on the node (e.g., via SSH). This command queries the AppArmor kernel module and lists all loaded profiles. Therefore, while the question asks for a 'kubectl command,' the correct approach is to use a node-level command like `aa-status`.

What should I do if I get this CKS question wrong?

Review appArmor, then practise related CKS questions on the same topic to reinforce the concept.

What is the key concept behind this question?

AppArmor

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

3 more ways this is tested on CKS

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Which kubectl command is used to check the AppArmor status on a Kubernetes node?

easy
  • A.kubectl describe node <node> | grep AppArmor
  • B.kubectl get apparmor
  • C.kubectl node-shell <node> -- aa-status
  • D.kubectl exec <pod> -- aa-status

Why C: Option C is correct because `kubectl node-shell` provides a shell into the node's filesystem, allowing you to run `aa-status` directly on the node to check the AppArmor status. This is the standard method to verify AppArmor profiles and their enforcement state on a Kubernetes node, as AppArmor operates at the host kernel level and is not managed via the Kubernetes API.

Variation 2. Which of the following is a valid way to check the status of AppArmor profiles on a node?

easy
  • A.Use 'apparmor_parser --status'
  • B.Run 'kubectl get apparmorprofiles'
  • C.Read the file /sys/kernel/security/apparmor/profiles
  • D.Run 'aa-status' on the node

Why D: Option D is correct because `aa-status` is the standard command-line tool for checking the status of AppArmor profiles on a Linux node. It displays which profiles are loaded, which processes are confined, and the enforcement mode (enforce/complain). This is the direct, node-level utility for AppArmor status verification.

Variation 3. Which of the following commands shows all loaded AppArmor profiles?

easy
  • A.apparmor_parser
  • B.aa-status
  • C.aa-disable
  • D.aa-enforce

Why B: The `aa-status` command displays the current status of AppArmor, including all loaded profiles, their enforcement mode (enforce/complain), and which processes are confined by them. This is the standard tool for listing active AppArmor profiles on a system.

Keep practising

More CKS practice questions

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This CKS practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKS exam.