Question 1mediummultiple choice
Read the full Troubleshooting explanation →CKA Troubleshooting • Complete Question Bank
Complete CKA Troubleshooting question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. $ kubectl get pods -n production NAME READY STATUS RESTARTS AGE api-6f4d7b9d4c-abcde 0/1 CrashLoopBackOff 5 3m $ kubectl describe pod api-6f4d7b9d4c-abcde -n production ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 3m40s default-scheduler Successfully assigned production/api-6f4d7b9d4c-abcde to node-1 Normal Pulled 3m30s kubelet Container image "nginx:1.21" already present on machine Normal Created 3m30s kubelet Created container api Normal Started 3m30s kubelet Started container api Warning BackOff 1s (x5 over 3m) kubelet Back-off restarting failed container
Refer to the exhibit. $ kubectl describe pod nginx-pod ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 2m default-scheduler Successfully assigned default/nginx-pod to node-1 Warning FailedMount 2m kubelet MountVolume.SetUp failed for volume "config" : secrets "my-secret" not found Warning FailedMount 1m kubelet MountVolume.SetUp failed for volume "config" : secrets "my-secret" not found Warning FailedMount 30s kubelet MountVolume.SetUp failed for volume "config" : secrets "my-secret" not found
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Simple label-based constraint
Expressive scheduling rules using labels
Repels Pods unless they tolerate the taint
Allows a Pod to be scheduled on a tainted Node
Determines scheduling precedence based on priority class
Drag a concept onto its matching description — or click a concept then click the description.
Log aggregator and forwarder
Metrics collection and alerting system
Dashboard and visualization tool
Exposes cluster object metrics
Provides resource usage metrics for autoscaling
You create a Deployment with the following YAML:
apiVersion: apps/v1 kind: Deployment metadata: name: myapp spec: replicas: 3 selector: matchLabels: app: myapp template: metadata: labels: app: myapp spec: containers: - name: myapp image: myapp:latest resources: limits: cpu: "500m" memory: "256Mi" requests: cpu: "200m" memory: "128Mi"
After applying it, the pods are in 'CrashLoopBackOff'. You check logs and see 'Error: container process exited with error'. What is the MOST likely cause?
You are debugging a CrashLoopBackOff. The pod YAML includes the following container spec:
```yaml containers: - name: app image: myapp:1.0 livenessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 3 periodSeconds: 3 ```
The application starts successfully but crashes after about 10 seconds. What is the most likely cause?
You deploy a pod with the following YAML:
apiVersion: v1 kind: Pod metadata: name: test-pod spec: containers: - name: test image: nginx resources: requests: memory: "64Mi" cpu: "250m" limits: memory: "128Mi" cpu: "500m"
The pod starts, but after a few minutes it is killed with OOMKilled. What is the MOST likely reason?
You deploy a pod with the following YAML and it remains in 'Pending' state. What is the most likely cause?
```yaml apiVersion: v1 kind: Pod metadata: name: myapp spec: containers: - name: myapp image: nginx resources: requests: memory: "64Gi" ```
A pod is in CrashLoopBackOff. The YAML for the initContainer is:
apiVersion: v1 kind: Pod metadata: name: myapp spec: initContainers: - name: init image: busybox command: ['sh', '-c', 'sleep 5 && exit 1'] containers: - name: app image: nginx
What is the most likely reason for the CrashLoopBackOff?