CKAD Application Observability and Maintenance • Complete Question Bank
Complete CKAD Application Observability and Maintenance question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. ``` $ kubectl describe pod nginx-pod ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 10m default-scheduler Successfully assigned default/nginx-pod to node-2 Normal Pulled 10m kubelet Container image "nginx:latest" already present on machine Normal Created 10m kubelet Created container nginx Normal Started 10m kubelet Started container nginx Warning Unhealthy 5m kubelet Readiness probe failed: HTTP probe failed with statuscode: 503 Warning Unhealthy 4m kubelet Readiness probe failed: HTTP probe failed with statuscode: 503 Normal Killing 3m kubelet Container nginx is not ready, stopping it Normal Pulled 3m kubelet Container image "nginx:latest" already present on machine Normal Created 3m kubelet Created container nginx Normal Started 3m kubelet Started container nginx Warning Unhealthy 2m kubelet Readiness probe failed: HTTP probe failed with statuscode: 503 ```
Refer to the exhibit.
$ kubectl logs myapp-6b4d9f8c7d-abcde
Error: listening on :8080: bind: address already in use
$ kubectl describe pod myapp-6b4d9f8c7d-abcde | grep -A5 Last State
Last State: Terminated
Reason: Error
Exit Code: 1
Message: listening on :8080: bind: address already in useRefer to the exhibit. ``` kubectl get pods -n production NAME READY STATUS RESTARTS AGE app-backend-6b4c9d8f7-2x4z5 0/1 CrashLoopBackOff 5 3m app-backend-6b4c9d8f7-7y8u9 1/1 Running 0 5m app-frontend-5f6a7b8c9d-1a2b3 1/1 Running 0 10m ```
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.
Maximum resources a container can use
Determines when to restart containers in a pod
Checks if container is running; restarts if fails
Checks if container is ready to serve traffic
Inject a secret value as an environment variable
Drag a concept onto its matching description — or click a concept then click the description.
apps/v1
v1 (core)
networking.k8s.io/v1
autoscaling/v2
networking.k8s.io/v1
You deploy a pod with the following specification:
apiVersion: v1 kind: Pod metadata: name: probe-pod spec: containers: - name: app image: nginx livenessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 periodSeconds: 10 failureThreshold: 3
The application listens on port 80, not 8080. What will happen to the pod?