Summer Sale - Special Limited Time 55% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: 44314956B5

Good News !!! CKS Certified Kubernetes Security Specialist (CKS) is now Stable and With Pass Result

CKS Practice Exam Questions and Answers

Certified Kubernetes Security Specialist (CKS)

Last Update 6 days ago
Total Questions : 48

CKS is stable now with all latest exam questions are added 6 days ago. Just download our Full package and start your journey with Linux Foundation Certified Kubernetes Security Specialist (CKS) certification. All these Linux Foundation CKS practice exam questions are real and verified by our Experts in the related industry fields.

CKS PDF

CKS PDF (Printable)
$54
$119.99

CKS Testing Engine

CKS PDF (Printable)
$63
$139.99

CKS PDF + Testing Engine

CKS PDF (Printable)
$79.65
$176.99
Question # 1

Question # 1

Context

Your organization’s security policy includes:

  • ServiceAccounts must not automount API credentials
  • ServiceAccount names must end in "-sa"

The Pod specified in the manifest file /home/candidate/KSCH00301 /pod-m

nifest.yaml fails to schedule because of an incorrectly specified ServiceAccount.

Complete the following tasks:

Task

1. Create a new ServiceAccount named frontend-sa in the existing namespace qa. Ensure the ServiceAccount does not automount API credentials.

2. Using the manifest file at /home/candidate/KSCH00301 /pod-manifest.yaml, create the Pod.

3. Finally, clean up any unused ServiceAccounts in namespace qa.

Options:

Discussion 0
Question # 2

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

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

Context:

A Role bound to a Pod's ServiceAccount grants overly permissive permissions. Complete the following tasks to reduce the set of permissions.

Task:

Given an existing Pod named web-pod running in the namespace database.

1. Edit the existing Role bound to the Pod's ServiceAccount test-sa to only allow performing get operations, only on resources of type Pods.

2. Create a new Role named test-role-2 in the namespace database, which only allows performing update operations, only on resources of type statuefulsets.

3. Create a new RoleBinding named test-role-2-bind binding the newly created Role to the Pod's ServiceAccount.

Note: Don't delete the existing RoleBinding.

Options:

Discussion 0
Question # 3

use the Trivy to scan the following images,

1.  amazonlinux:1

2.  k8s.gcr.io/kube-controller-manager:v1.18.6

Look for images with HIGH or CRITICAL severity vulnerabilities and store the output of the same in /opt/trivy-vulnerable.txt

Options:

Discussion 0
Question # 4

Question # 4

Context

A CIS Benchmark tool was run against the kubeadm-created cluster and found multiple issues that must be addressed immediately.

Task

Fix all issues via configuration and restart the affected components to ensure the new settings take effect.

Fix all of the following violations that were found against the API server:

Question # 4

Fix all of the following violations that were found against the Kubelet:

Question # 4

Question # 4

Fix all of the following violations that were found against etcd:

Question # 4

Options:

Discussion 0
Question # 5

Create a RuntimeClass named untrusted using the prepared runtime handler named runsc.

Create a Pods of image alpine:3.13.2 in the Namespace default to run on the gVisor runtime class.

Options:

Discussion 0
Question # 6

Cluster: dev

Master node: master1

Worker node: worker1

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

[desk@cli] $ kubectl config use-context dev 

Task:

Retrieve the content of the existing secret named adam in the safe namespace.

Store the username field in a file names /home/cert-masters/username.txt, and the password field in a file named /home/cert-masters/password.txt.

1. You must create both files; they don't exist yet.

2. Do not use/modify the created files in the following steps, create new temporary files if needed. 

Create a new secret names newsecret in the safe namespace, with the following content:

Username: dbadmin

Password: moresecurepas

Finally, create a new Pod that has access to the secret newsecret via a volume:

  • Namespace:safe
  • Pod name:mysecret-pod
  • Container name:db-container
  • Image:redis
  • Volume name:secret-vol
  • Mount path:/etc/mysecret

Options:

Discussion 0
Question # 7

You must complete this task on the following cluster/nodes: Cluster: immutable-cluster

Master node: master1

Worker node: worker1

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

[desk@cli] $  kubectl config use-context immutable-cluster 

Context: It is best practice to design containers to be stateless and immutable.

Task:

Inspect Pods running in namespace prod and delete any Pod that is either not stateless or not immutable.

Use the following strict interpretation of stateless and immutable:

1. Pods being able to store data inside containers must be treated as not stateless. 

Note: You don't have to worry whether data is actually stored inside containers or not already.

2. Pods being configured to be privileged in any way must be treated as potentially not stateless or not immutable.

Options:

Discussion 0
Get CKS dumps and pass your exam in 24 hours!

Free Exams Sample Questions