Linux Foundation CKS Practice Exam Dumps 2025

Linux Foundation Related Exams

Linux Foundation LFCS

Linux Foundation Certified System Administrator

View Detail

Linux Foundation CKA

Certified Kubernetes Administrator (CKA) Program

View Detail

Linux Foundation CKAD

Certified Kubernetes Application Developer (CKAD) Program

View Detail

Linux Foundation KCNA

Kubernetes and Cloud Native Associate

View Detail

Linux Foundation HFCP

Hyperledger Fabric Certified Practitioner (HFCP) Exam

View Detail

Linux Foundation LFCA

Linux Foundation Certified IT Associate

View Detail

Linux Foundation KCSA

Kubernetes and Cloud Native Security Associate (KCSA)

View Detail

Linux Foundation CGOA

Certified GitOps Associate Exam

View Detail

Linux Foundation CNPA

Certified Cloud Native Platform Engineering Associate

View Detail

Linux Foundation PCA

Prometheus Certified Associate Exam

View Detail

Last Week Results

32 Customers Passed Linux Foundation
CKS Exam

Average Score In Real Exam

86.7%

Questions came word for word from this dump

88.6%

Linux Foundation Bundle Exams

Duration: 3 to 12 Months

9 Certifications

11 Exams

Linux Foundation Updated Exams

Most authenticate information

Prepare within Days

Time-Saving Study Content

90 to 365 days Free Update

$249.6*

View Detail

Free CKS Exam Dumps

What our customers are saying

Western Sahara

Kane

Feb 3, 2026

My experience was great with certstopic as it provided detailed resource and important information which made me score 93% on the CKS test. Thanks!

Bangladesh

Brooklyn

Jan 30, 2026

Certstopics's CKS study material is comprehensive and reliable. With their support, I cleared my certification exam effortlessly. Guaranteed success!

South Georgia

Brady

Jan 24, 2026

Certstopics.com's Exam preparation course was detailed and effective. It gave me the edge I needed to pass my Linux Foundation CKS exam.

Cook Islands

Agim

Jan 23, 2026

I owe my success for sure to certstopics CKS exam material. Guaranteed success with their help!

Morocco

Sarah

Jan 12, 2026

CertsTopics is a very interesting platform to learn the Linux Foundation CKS exam course. Practicing with tests at the following levels will be very helpful while sitting for any exam or interview.

Certified Kubernetes Security Specialist (CKS) Questions and Answers

Question 1

You can switch the cluster/configuration context using the following command:

[desk@cli] $ kubectl config use-context test-account

Task: 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 5 days

3. at maximum, a number of 10 old audit log files are retained

A basic policy is provided at /etc/Kubernetes/logpolicy/audit-policy.yaml. It only specifies what not to log.

Note: The base policy is located on the cluster's master node.

Edit and extend the basic policy to log:

1. Nodes changes at RequestResponse level

2. The request body of persistentvolumes changes in the namespace frontend

3. ConfigMap and Secret changes in all namespaces at the Metadata level

Also, add a catch-all rule to log all other requests at the Metadata level

Note: Don't forget to apply the modified policy.

Options:

Buy Now

Answer:

See the explanation below

Explanation:

$ vim /etc/kubernetes/log-policy/audit-policy.yaml

- level: RequestResponse

userGroups: ["system:nodes"]

- level: Request

resources:

- group: "" # core API group

resources: ["persistentvolumes"]

namespaces: ["frontend"]

- level: Metadata

resources:

- group: ""

resources: ["configmaps", "secrets"]

- level: Metadata

$ vim /etc/kubernetes/manifests/kube-apiserver.yaml

Add these

- --audit-policy-file=/etc/kubernetes/log-policy/audit-policy.yaml

- --audit-log-path=/var/log/kubernetes/logs.txt

- --audit-log-maxage=5

- --audit-log-maxbackup=10

Explanation[desk@cli] $ ssh master1

[master1@cli] $ vim /etc/kubernetes/log-policy/audit-policy.yaml

apiVersion: audit.k8s.io/v1 # This is required.

kind: Policy

# Don't generate audit events for all requests in RequestReceived stage.

omitStages:

- "RequestReceived"

rules:

# Don't log watch requests by the "system:kube-proxy" on endpoints or services

- level: None

users: ["system:kube-proxy"]

verbs: ["watch"]

resources:

- group: "" # core API group

resources: ["endpoints", "services"]

# Don't log authenticated requests to certain non-resource URL paths.

- level: None

userGroups: ["system:authenticated"]

nonResourceURLs:

- "/api*" # Wildcard matching.

- "/version"

# Add your changes below

- level: RequestResponse

userGroups: ["system:nodes"] # Block for nodes

- level: Request

resources:

- group: "" # core API group

resources: ["persistentvolumes"] # Block for persistentvolumes

namespaces: ["frontend"] # Block for persistentvolumes of frontend ns

- level: Metadata

resources:

- group: "" # core API group

resources: ["configmaps", "secrets"] # Block for configmaps & secrets

- level: Metadata # Block for everything else

[master1@cli] $ vim /etc/kubernetes/manifests/kube-apiserver.yaml

apiVersion: v1

kind: Pod

metadata:

annotations:

kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: 10.0.0.5:6443

labels:

component: kube-apiserver

tier: control-plane

name: kube-apiserver

namespace: kube-system

spec:

containers:

- command:

- kube-apiserver

- --advertise-address=10.0.0.5

- --allow-privileged=true

- --authorization-mode=Node,RBAC

- --audit-policy-file=/etc/kubernetes/log-policy/audit-policy.yaml #Add this

- --audit-log-path=/var/log/kubernetes/logs.txt #Add this

- --audit-log-maxage=5 #Add this

- --audit-log-maxbackup=10 #Add this

output truncated

Note: log volume & policy volume is already mounted in vim /etc/kubernetes/manifests/kube-apiserver.yaml so no need to mount it.

[Reference: https://kubernetes.io/docs/tasks/debug-application-cluster/audit/, ]

Question 2

Task

Create a NetworkPolicy named pod-access to restrict access to Pod users-service running in namespace dev-team.

Only allow the following Pods to connect to Pod users-service:

Pods in the namespace qa

Pods with label environment: testing, in any namespace