‹ CKA tests

Certified Kubernetes Administrator (CKA) practice questions

10 questions in 1 test. Open one to answer it on its own, or take a whole test.

  1. You create a ClusterRole named pod-reader granting get, list, and watch on pods, then bind it to the user dev-user with a RoleBinding in the dev namespace. dev-user reports they… · RBAC & Authorization
  2. You are upgrading a kubeadm-built cluster one minor version. The control plane nodes have already been upgraded successfully and are serving traffic. You now need to upgrade the… · Cluster Upgrades
  3. A cluster has 3 nodes with GPUs, labelled hardware=gpu, and 12 nodes without. You need two things to be true: GPU workloads must run only on the GPU nodes, and all other… · Scheduling
  4. A Deployment's containers read their configuration from a ConfigMap using envFrom.configMapRef. An operator edits the ConfigMap with kubectl edit and confirms the new value is… · Workloads & Configuration
  5. You are deploying a 3-replica StatefulSet running a database that replicates between its members. Each member must be individually addressable by a stable DNS name so peers can… · Services & Networking
  6. In the prod namespace you apply a default-deny NetworkPolicy with an empty podSelector and policyTypes: [Ingress, Egress]. You then add a second NetworkPolicy that allows egress… · Network Policies
  7. A developer deleted a PersistentVolumeClaim that was bound to a dynamically provisioned PersistentVolume. The PersistentVolume disappeared along with the underlying cloud disk… · Storage
  8. A newly created Pod stays in the Pending phase. Running kubectl describe pod on it shows the following event: 0/4 nodes are available: 1 node(s) had untolerated taint… · Troubleshooting
  9. An application Pod running in the web namespace fails to connect to a database using the hostname db. From a shell inside that same Pod, resolving db.prod.svc.cluster.local… · Cluster DNS
  10. On a kubeadm-built cluster, every kubectl command fails with The connection to the server 10.0.0.10:6443 was refused - did you specify the right host or port?. You SSH to the… · Troubleshooting