P.S. Free & New CKS dumps are available on Google Drive shared by Real4test: https://drive.google.com/open?id=1mhBHLjwNjd-hN0kH-D3rxh7wBKTBRRY_
Perhaps you agree that strength is very important, but there are doubts about whether our CKS study questions can really improve your strength. It does not matter, we can provide you with a free trial version of our CKS exam braindumps. You can free downlod the demos of our CKS learning prep easily on our website, and there are three versions according to the three versions of ourCKS practice engine. It is really as good as we say, you can experience it yourself.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Cluster Hardening | 15% | - API access restriction - RBAC configuration - Service account security - Component updates & vulnerability mitigation |
| Topic 2: Monitoring, Logging and Runtime Security | 20% | - Incident investigation - Audit log configuration - Container immutability - Threat detection (Falco) - Behavioral analytics |
| Topic 3: Minimize Microservice Vulnerabilities | 20% | - Pod Security Standards - Isolation & multi-tenancy - Secret management - OPA/Gatekeeper implementation - Security contexts |
| Topic 4: Cluster Setup | 15% | - CIS benchmark compliance - Binary verification - Secure Ingress configuration - Network security policies - Node metadata protection |
| Topic 5: System Hardening | 10% | - Minimize OS attack surface - Network access control - Kernel hardening (AppArmor, seccomp) - Least privilege IAM |
| Topic 6: Supply Chain Security | 20% | - Image security & scanning - Static analysis tools - Permitted registries - Signed artifacts & verification - SBOM & CI/CD security |
>> Intereactive CKS Testing Engine <<
We can resort to electronic CKS exam materials, which is now a commonplace, and the electronic materials with the highest quality which consists of all of the key points required for the CKS exam can really be considered as the royal road to learning. Fortunately, the CKS practice test compiled by our company are the best choice for you, you just lucky enough to click into this website, since you are sure to pass the CKS Exam as well as getting the related certification under the guidance of our CKS study guide which you can find in this website easily.
NEW QUESTION # 55
SIMULATION
Create a PSP that will prevent the creation of privileged pods in the namespace.
Create a new PodSecurityPolicy named prevent-privileged-policy which prevents the creation of privileged pods.
Create a new ServiceAccount named psp-sa in the namespace default.
Create a new ClusterRole named prevent-role, which uses the newly created Pod Security Policy prevent-privileged-policy.
Create a new ClusterRoleBinding named prevent-role-binding, which binds the created ClusterRole prevent-role to the created SA psp-sa.
Also, Check the Configuration is working or not by trying to Create a Privileged pod, it should get failed.
Answer:
Explanation:
Create a PSP that will prevent the creation of privileged pods in the namespace.
$ cat clusterrole-use-privileged.yaml
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: use-privileged-psp
rules:
- apiGroups: ['policy']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames:
- default-psp
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: privileged-role-bind
namespace: psp-test
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: use-privileged-psp
subjects:
- kind: ServiceAccount
name: privileged-sa
$ kubectl -n psp-test apply -f clusterrole-use-privileged.yaml
After a few moments, the privileged Pod should be created.
Create a new PodSecurityPolicy named prevent-privileged-policy which prevents the creation of privileged pods.
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: example
spec:
privileged: false # Don't allow privileged pods!
# The rest fills in some required fields.
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
runAsUser:
rule: RunAsAny
fsGroup:
rule: RunAsAny
volumes:
- '*'
And create it with kubectl:
kubectl-admin create -f example-psp.yaml
Now, as the unprivileged user, try to create a simple pod:
kubectl-user create -f- <<EOF
apiVersion: v1
kind: Pod
metadata:
name: pause
spec:
containers:
- name: pause
image: k8s.gcr.io/pause
EOF
The output is similar to this:
Error from server (Forbidden): error when creating "STDIN": pods "pause" is forbidden: unable to validate against any pod security policy: [] Create a new ServiceAccount named psp-sa in the namespace default.
$ cat clusterrole-use-privileged.yaml
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: use-privileged-psp
rules:
- apiGroups: ['policy']
resources: ['podsecuritypolicies']
verbs: ['use']
resourceNames:
- default-psp
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: privileged-role-bind
namespace: psp-test
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: use-privileged-psp
subjects:
- kind: ServiceAccount
name: privileged-sa
$ kubectl -n psp-test apply -f clusterrole-use-privileged.yaml
After a few moments, the privileged Pod should be created.
Create a new ClusterRole named prevent-role, which uses the newly created Pod Security Policy prevent-privileged-policy.
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
name: example
spec:
privileged: false # Don't allow privileged pods!
# The rest fills in some required fields.
seLinux:
rule: RunAsAny
supplementalGroups:
rule: RunAsAny
runAsUser:
rule: RunAsAny
fsGroup:
rule: RunAsAny
volumes:
- '*'
And create it with kubectl:
kubectl-admin create -f example-psp.yaml
Now, as the unprivileged user, try to create a simple pod:
kubectl-user create -f- <<EOF
apiVersion: v1
kind: Pod
metadata:
name: pause
spec:
containers:
- name: pause
image: k8s.gcr.io/pause
EOF
The output is similar to this:
Error from server (Forbidden): error when creating "STDIN": pods "pause" is forbidden: unable to validate against any pod security policy: [] Create a new ClusterRoleBinding named prevent-role-binding, which binds the created ClusterRole prevent-role to the created SA psp-sa.
apiVersion: rbac.authorization.k8s.io/v1
# This role binding allows "jane" to read pods in the "default" namespace.
# You need to already have a Role named "pod-reader" in that namespace.
kind: RoleBinding
metadata:
name: read-pods
namespace: default
subjects:
# You can specify more than one "subject"
- kind: User
name: jane # "name" is case sensitive
apiGroup: rbac.authorization.k8s.io
roleRef:
# "roleRef" specifies the binding to a Role / ClusterRole
kind: Role #this must be Role or ClusterRole
name: pod-reader # this must match the name of the Role or ClusterRole you wish to bind to apiGroup: rbac.authorization.k8s.io apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata:
namespace: default
name: pod-reader
rules:
- apiGroups: [""] # "" indicates the core API group
resources: ["pods"]
verbs: ["get", "watch", "list"]
NEW QUESTION # 56
SIMULATION
Context
The kubeadm-created cluster's Kubernetes API server was, for testing purposes, temporarily configured to allow unauthenticated and unauthorized access granting the anonymous user duster-admin access.
Task
Reconfigure the cluster's Kubernetes API server to ensure that only authenticated and authorized REST requests are allowed.
Use authorization mode Node,RBAC and admission controller NodeRestriction.
Cleaning up, remove the ClusterRoleBinding for user system:anonymous.
Answer:
Explanation:
See the Explanation below
Explanation:
NEW QUESTION # 57
Your Kubernetes cluster runs a Deployment named 'database' which exposes a database service. You need to implement a NetworkPolicy that allows only pods belonging to a specific namespace to access the database service.
Answer:
Explanation:
Solution (Step by Step) :
1. Create a NetworkPolicy:
- Define a NetworkPolicy resource with a 'podSelector' that matches the 'database' Deployment.
- Create an 'ingress' rule that allows traffic from pods in the specified namespace.
- Use the 'from' field to specify the namespace and set the 'namespacesaector' to the desired namespace.
- Ensure that the port used by the database service is included in the 'ports' field.
2. Apply the NetworkPolicy: - Apply the YAML file using 'kubectl apply -f database-access-policy.yaml 3. Verify the NetworkPoIicy: - Use 'kubectl get networkpolicies' to list the available network policies. - Use 'kubectl describe networkpolicy database-access-policy' to view the details ot the applied policy. 4. Test the NetworkPolicy: - Deploy a pod in the 'allowed-namespace' and attempt to connect to the database service. Verify that the connection is successful. - Deploy a pod in a different namespace and attempt to connect to the database service. Verify that the connection is denied.
NEW QUESTION # 58
Cluster: scanner
Master node: controlplane
Worker node: worker1
You can switch the cluster/configuration context using the following command:
[desk@cli] $ kubectl config use-context scanner
Given:
You may use Trivy's documentation.
Task:
Use the Trivy open-source container scanner to detect images with severe vulnerabilities used by Pods in the namespace nato.
Look for images with High or Critical severity vulnerabilities and delete the Pods that use those images.
Trivy is pre-installed on the cluster's master node. Use cluster's master node to use Trivy.
Answer:
Explanation:
[controlplane@cli] $ k get pods -n nato -o yaml | grep "image: "
[controlplane@cli] $ trivy image <image-name>
[controlplane@cli] $ k delete pod <vulnerable-pod> -n nato
[desk@cli] $ ssh controlnode
[controlplane@cli] $ k get pods -n nato
NAME READY STATUS RESTARTS AGE
alohmora 1/1 Running 0 3m7s
c3d3 1/1 Running 0 2m54s
neon-pod 1/1 Running 0 2m11s
thor 1/1 Running 0 58s
[controlplane@cli] $ k get pods -n nato -o yaml | grep "image: "
[controlplane@cli] $ k delete pod thor -n nato
[controlplane@cli] $ k delete pod neon-pod -n nato Reference: https://github.com/aquasecurity/trivy
[controlplane@cli] $ k delete pod neon-pod -n nato Reference: https://github.com/aquasecurity/trivy
NEW QUESTION # 59
SIMULATION
Create a network policy named restrict-np to restrict to pod nginx-test running in namespace testing.
Only allow the following Pods to connect to Pod nginx-test:-
1. pods in the namespace default
2. pods with label version:v1 in any namespace.
Make sure to apply the network policy.
Answer: A
NEW QUESTION # 60
......
Dear customers, we would like to make it clear that learning knowledge and striving for certificates of exam is a self-improvement process, and you will realize yourself rather than offering benefits for anyone. So our CKS practice materials are once a lifetime opportunity you cannot miss. With all advantageous features introduced as follow, please read them carefully.
Reliable CKS Dumps Ebook: https://www.real4test.com/CKS_real-exam.html
What's more, part of that Real4test CKS dumps now are free: https://drive.google.com/open?id=1mhBHLjwNjd-hN0kH-D3rxh7wBKTBRRY_