Application Observability and Maintenance
CKAD · 45 questions
- A city’s Ingress manifest still declares a removed beta apiVersion and fails on a current cluster. What should the application developer do?
- While applying application manifests, kubectl prints a warning that a resource type is deprecated. What is the correct response before the API is removed?
- A developer writing new workload YAML needs to know which apiVersion the cluster prefers for a resource kind. Which approach helps choose the preferred version?
- A scheduled reports CronJob still uses batch/v1beta1 and fails on a newer cluster. Which migration fixes the application schedule object?
- kubectl warns that a field in a Deployment manifest is deprecated, yet the apply still succeeds today. What should the application developer do?
- A city permits API still ships Deployment manifests using an API version that staging accepts on an older cluster, but production rejects the apply. What should the team do first?
- After a cluster upgrade, a parks-and-recreation Deployment YAML still references a deprecated API. What maintenance approach updates the manifests correctly?
- A 311 Operator ships a new CRD version and marks the old one deprecated. How should the application team that owns Custom Resources respond?
- A web Pod for a tax-filing helper fails its liveness probe and restarts in a loop, yet the process is only slow to finish initializing. What probe change best stops premature kills?
- A civic API Pod’s readinessProbe fails while its livenessProbe still passes. What is the expected Service behavior?
- A city open-data API exposes HTTP health on path /healthz at container port 8080. How should an httpGet probe be configured?
- A TCP-only batch worker for meter readings has no HTTP server. Which probe type correctly checks that its listen port is open?
- A licensing microservice needs a custom in-container check that runs a shell command and uses its exit code. Which probe handler fits?
- Operators want faster failure detection on a civic chat Pod without flapping on brief blips. Which probe timing approach balances speed and stability?
- A readinessProbe on every permits API Pod calls a shared external payment dependency. During a brief payment outage, all Pods become NotReady. What is the main pitfall?
- A modern cluster runs an app that needs several minutes to warm caches. Engineers only set a large initialDelaySeconds on liveness. What is the preferred modern pattern?
- A busy records-search API is healthy but occasionally slow under load. An aggressive liveness httpGet treats latency as death and restarts Pods, causing a thundering herd. What design lesson applies?
- A Deployment defines a container port named http on 8080. How can a probe reference that port clearly?
- After readiness failures, a flaky health endpoint flickers. Which probe field requires multiple consecutive successes before marking the Pod ready again?
- A multi-container Pod has a main city-maps API and a log-shipping sidecar. Probes were attached only to the sidecar, which never serves /healthz. What should the developer fix?
- A failing parks mobile backend needs a quick first look at Pod status and which node hosts each replica. Which kubectl command is the best first monitoring step?
- A Deployment’s Pods stay Pending or fail image pulls. Which kubectl view best surfaces the Events explaining scheduling or image errors?
- Platform metrics are available. Engineers need live CPU and memory usage for a permits API Pod to right-size requests. Which built-in CLI command helps?
- On-call needs a chronological view of what happened in the permits namespace during an incident. Which approach helps reconstruct the timeline?
- A bad rollout leaves unclear which ReplicaSet owns the struggling Pods. What kubectl listing helps monitor the Deployment ownership chain together?
- A busy shared namespace hosts many apps. How should an operator list only the 311 application Pods for monitoring?
- Users report connection failures to a Service even though Pods look Running. What should the developer check to see if the Service has backends?
- During a release, engineers want a live stream of Pod phase changes without repeatedly re-running get. Which kubectl feature fits?
- A developer needs the current stdout/stderr from Pods managed by Deployment myapp. Which command pattern retrieves those application logs?
- A container restarted after a crash and current logs only show the new instance. How can the developer read logs from the previous terminated container?
- A civic permitting Pod runs containers named app and sidecar. A developer runs kubectl logs permitting-7f and sees an error asking which container. What should they do next?
- During a short outage window for a library catalog API, an engineer needs recent lines with wall-clock times rather than the entire container history. Which kubectl logs approach fits best?
- A municipal reporting Pod restarts repeatedly. The last log lines cut off mid-request, and kubectl describe pod shows the previous container terminated with reason OOMKilled. What is the best conclusion?
- A parks-and-rec team wants one kubectl command that aggregates application logs from every Pod across the cluster like a production logging platform. What should you clarify?
- A fee-payment API Pod is Running, but application logs repeatedly show authentication failures to Postgres. kubectl describe shows the expected Secret volume mount path is empty or missing keys. What should the developer investigate first?
- A readiness HTTP probe hits /healthz every few seconds, and the app logs every probe as INFO, drowning useful traffic logs. What is the most appropriate application-side response?
- After deploying a new tax-forms API image, Pods enter CrashLoopBackOff. What systematic first path best identifies why the container exits?
- A new Deployment for a court-calendar UI stays in ImagePullBackOff. Which cause is most consistent with that status?
- A grants-intake Pod remains Pending. Events mention insufficient CPU on nodes, and a second similar Pod is Pending waiting for a PVC to bind. What should the developer do?
- A civic GIS app Pod is Running but returns wrong basemap tiles. The developer wants to inspect files under /etc/gis and test DNS from inside the container. Which approach fits?
- From inside a permits API Pod, resolving the Service name permits-db fails, while the Pod itself is Ready. What is the best next debugging focus?
- An engineer swears the billing-api Deployment vanished: kubectl get deploy prints nothing, yet the CI job reports a successful apply. What should they check first?
- A license-renewal container listens on port 8080, but the Pod’s containerPort and the Service targetPort are set to 80. Users hit connection failures. How should the developer diagnose and fix?
- A distroless payment container has no shell, so kubectl exec ... -- sh fails. The developer still needs tools inside the Pod’s network namespace for debugging. What is the appropriate approach?
- A Deployment for a records-search API shows zero ready Pods. What ownership chain should the developer walk to find the broken application template?