Leave a message
Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 0d 12h 46m 45s Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Linux Foundation Exam CKS Topic 1 Question 32 Discussion

Actual exam question for Linux Foundation's CKS exam
Question #: 32
Topic #: 1
[All CKS Questions]

Enable audit logs in the cluster, To Do so, enable the log backend, and ensure that

1. logs are stored at /var/log/kubernetes-logs.txt.

2. Log files are retained for 12 days.

3. at maximum, a number of 8 old audit logs files are retained.

4. set the maximum size before getting rotated to 200MB

Edit and extend the basic policy to log:

1. namespaces changes at RequestResponse

2. Log the request body of secrets changes in the namespace kube-system.

3. Log all other resources in core and extensions at the Request level.

4. Log "pods/portforward", "services/proxy" at Metadata level.

5. Omit the Stage RequestReceived

All other requests at the Metadata level

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Rebecka
26 days ago
Configuring audit logs is no easy task, but these instructions make it straightforward. I'm glad they included the example for running kube-apiserver as a Pod.
upvoted 0 times
Helga
12 days ago
Thanks for the detailed explanation. I appreciate the example provided for running kube-apiserver as a Pod.
upvoted 0 times
...
...
Ilene
29 days ago
This is a well-thought-out question. The details around the CIS Kubernetes Benchmark and the ability to configure the audit log backend are a nice touch.
upvoted 0 times
Malinda
9 days ago
Yes, it helps track all the requests and events happening in the cluster.
upvoted 0 times
...
Nikita
18 days ago
I think enabling audit logs in the cluster is crucial for security.
upvoted 0 times
...
...
Laticia
1 months ago
Haha, imagine if the audit logs were stored in /dev/null by mistake. The admins would be scratching their heads trying to find the logs!
upvoted 0 times
Arlene
16 days ago
Yeah, storing audit logs in /dev/null would definitely cause some confusion.
upvoted 0 times
...
Mica
17 days ago
That would be a nightmare! They would be searching for logs that don't exist.
upvoted 0 times
...
...
Mauricio
1 months ago
The policy configuration looks comprehensive, covering changes to namespaces, secrets, and other resources. I like how it includes logging at different stages like RequestResponse and Metadata.
upvoted 0 times
...
Steffanie
1 months ago
I agree, it's crucial to have a detailed audit trail for compliance purposes.
upvoted 0 times
...
Talia
1 months ago
Yes, it helps track all the requests and changes made in the cluster.
upvoted 0 times
...
Jesus
1 months ago
Enabling audit logs in the cluster is crucial for security and compliance. The instructions provided cover the key aspects well, like log file path, retention period, and rotation settings.
upvoted 0 times
Tegan
2 days ago
Set the maximum size before rotation to 200MB and configure the audit policy to log specific changes.
upvoted 0 times
...
Phillip
19 days ago
Don't forget to retain log files for 12 days and limit the number of old audit log files to 8.
upvoted 0 times
...
Candra
20 days ago
Make sure to enable the log backend and set the log file path to /var/log/kubernetes-logs.txt.
upvoted 0 times
...
...
Willodean
2 months ago
I think enabling audit logs in the cluster is important for security.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77
a