You must complete this task on the following cluster/nodes:
Cluster:apparmor
Master node:master
Worker node:worker1
You can switch the cluster/configuration context using the following command:
[desk@cli] $kubectl config use-context apparmor
Given: AppArmor is enabled on the worker1 node.
Task:
On the worker1 node,
1. Enforce the prepared AppArmor profile located at:/etc/apparmor.d/nginx
2. Edit the prepared manifest file located at/home/cert_masters/nginx.yamlto apply the apparmor profile
3. Create the Pod using this manifest
Suggested Answer: A
Get Premium CKS Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
LI
Lizbeth
12 months ago
I’m surprised it’s that straightforward to set up!
OR
Oren
1 year ago
Totally agree, annotations are key for AppArmor profiles!
GL
Gladys
1 year ago
Wait, do we really need to edit the manifest for this?
JE
Jettie
1 year ago
Yup, just enforce the profile with apparmor_parser!
FE
Felicidad
1 year ago
AppArmor is enabled on worker1, right?
LA
Latrice
1 year ago
I feel a bit confused about the order of operations. Do we need to check the status of the profile before applying the manifest?
ES
Estrella
1 year ago
I think we had a similar question in our last mock exam where we had to edit a manifest file. Just need to remember to add the annotations correctly.
LY
Lynette
1 year ago
I remember we practiced enforcing AppArmor profiles, but I'm not entirely sure about the exact command syntax for the parser.
MU
Muriel
1 year ago
I recall that the AppArmor profile needs to be enforced first, but I hope I don't mix up the commands for SSH and kubectl.
JA
Janessa
1 year ago
This question seems straightforward, but I want to make sure I understand the key concepts around operational risk management before selecting an answer.
KA
Katina
1 year ago
I'm a bit confused by the different permission levels mentioned. I'll need to review the details carefully.