Application Deployment

CKAD · 60 questions

• A city website cutover must keep the old version live until operators point traffic at the new version. How should blue/green be designed with Kubernetes primitives?
• A tax-payment API needs a canary so only a small fraction of users hit v2. Using Deployments and a Service (no service mesh), what approach fits?
• A release includes a breaking schema change that cannot safely mix v1 and v2 Pods behind the same Service. Which deployment approach is most appropriate?
• For a canary, v2 Pods are labeled version=canary while stable Pods use version=stable. How should the Service be labeled so both receive traffic?
• After green is validated and the Service points at green Pods, what is an appropriate teardown step for the old blue Deployment?
• A team calls every Deployment rolling update a “canary.” What distinction should they learn?
• When is a Deployment recreate strategy acceptable despite briefly taking the app offline?
• After a blue/green cutover attempt, clients still reach old blue Pods. Investigation shows the Service selector was never updated. What went wrong?
• A progressive delivery product is unavailable in the cluster. How should a CKAD candidate implement a basic canary?
• Green Deployment Pods are Ready, but users still hit blue because Ingress still references the blue Service name. What lesson applies?
• During canary analysis, operators want only healthy v2 Pods to receive Service traffic before scaling the canary up. What should they rely on?
• A city wants near-instant rollback from green back to blue. Blue Pods are still running at reduced scale. What advantage does blue/green offer?
• Operators start a rolling update on a Deployment while also adding a separate canary Deployment for the same release, and the plan becomes unclear. What guidance applies?
• A developer tries to implement a web API canary by creating a Job that runs the v2 image once. Why is that the wrong workload?
• Product wants header-based canary routing for internal testers. At CKAD depth with basic Service weighting only, what should the candidate conclude?
• A city API Deployment cannot drop capacity during updates. The rollingUpdate strategy sets maxUnavailable to 0 and maxSurge to 1. What behavior should the candidate expect?
• After updating a permitting portal Deployment image, a developer needs a CLI wait that blocks until the new ReplicaSet is progressing successfully. Which command is the right wait signal?
• A parks department Deployment hangs after a bad container image was rolled out. Which action restores traffic using the previous ReplicaSet revision?
• A permitting UI team needs to inspect past Deployment revisions and then undo to a specific older revision—not only the immediate previous one. Which approach matches that goal?
• An ops note says changing only a Deployment annotation can record a change-cause, while Pod template changes drive rollouts. Which statement is accurate for when a new rolling update begins?
• A batch invoice worker can tolerate brief downtime but must never run old and new code together. Which Deployment strategy type fits that downtime tolerance and mutual-exclusion need?
• A slow-starting civic reporting app passes its Ready condition quickly but still flakes under load for a few seconds. How does setting minReadySeconds on the Deployment help during a rolling update?
• A Deployment update stops making progress and the status later shows ProgressDeadlineExceeded. Which field primarily defines how long Kubernetes waits before marking that timeout?
• Traffic to a 311 API spikes overnight. The team needs more Pods but must not change the running container image. Which action correctly separates scale from a rolling image update?
• Old ReplicaSets for a library catalog Deployment keep accumulating and clutter etcd, but the team still wants some undo depth. Which field tunes how many old ReplicaSets are retained?
• During a canary-style bake, platform engineers want a Deployment to stop creating further new Pods mid-rollout until they manually continue. Which control matches that need?
• During a rolling update of a utility billing API, new Pods start but must not receive Service traffic until healthy. Which statement correctly ties readiness to rollout safety?
• A developer needs a quick, valid way to change one container image on a Deployment and start a rolling update without hand-editing the full manifest. Which approach is appropriate?
• A Deployment rollout appears stuck: new Pods remain Pending while old Pods still serve traffic. Image name and tags look correct. What should the candidate investigate first for this failure mode?
• A Deployment has 4 replicas and rollingUpdate.maxUnavailable set to 50%. During the update, how many Pods may be unavailable at once relative to the desired count?
• A city queue worker needs Redis from a public Helm chart already packaged by the community. Which command pattern correctly installs that existing chart as a named release?
• A municipal chart needs different database URLs per environment without forking the upstream chart. Which Helm approach customizes the release correctly?
• The municipal CMS Helm release must move to a newer chart version with updated values in place. Which command is the correct in-place update path?
• A Helm upgrade breaks the city’s permit search UI. Which action restores the prior successful release revision?
• An app team works only in namespace permitting-apps and needs to see Helm releases for their apps—not cluster-admin inventory. Which practice fits?
• A pilot Redis Helm release is no longer needed. Which command cleanly removes the release’s owned resources?
• helm install fails because the chart cannot be found; the team never configured chart repositories. What should they do first to consume published charts?
• Before installing a third-party chart into a production municipal namespace, a developer wants to inspect the rendered manifests without creating a release. Which command supports that review?
• Two developers accidentally choose the same Helm release name in namespace parks-web. What is the correct understanding of Helm release naming?
• A CKAD-style application chart’s values.yaml exposes replicaCount and image.tag. How do those common keys typically map when the chart templates a Deployment?
• After a flaky Helm upgrade of a city permitting dashboard, helm history lists several failed revisions. What should the developer do before choosing a rollback target?
• A municipal analytics team needs to install a widely packaged Kubernetes dashboard that already ships as a chart. Building a custom Operator just to install it would be overkill. Which approach best fits CKAD application deployment?
• A developer runs helm install for a parks recreation API and forgets to set a namespace flag, so the release lands in the wrong place. Which practice prevents that mistake?
• During a Helm upgrade of a billing chart, a one-shot migrate Job runs before the new Deployment pods start. At awareness depth, what Helm feature typically drives that Job?
• A Helm chart treats ConfigMaps as immutable and templates a new ConfigMap name when values change on upgrade. What side effect should the developer expect?
• A 311 API has one shared base of manifests and needs different settings for staging versus production. Which Kustomize layout matches that goal?
• An overlay must stamp app.kubernetes.io/ labels onto every resource in a Kustomize build. Which kustomization.yaml field injects those shared labels?
• Staging and production overlays for a grants portal share one cluster and would collide on resource names if left unchanged. How does Kustomize typically avoid that collision?
• A Kustomize overlay must bump a Deployment’s container image tag without hand-editing every base YAML file. Which field is designed for that change?
• Production should run five replicas of a ticket API while the staging overlay keeps one. Where in Kustomize should those environment-specific counts live?
• Only the staging overlay must change a Deployment’s readinessProbe path. Which Kustomize mechanism makes that surgical edit?
• A developer has a directory with kustomization.yaml and wants Kubernetes to build and apply that overlay in one step. Which kubectl invocation is appropriate?
• A Kustomize configMapGenerator builds a ConfigMap from local files and appends a content hash to the name. Why does that hash suffix matter for Deployments that reference the generated ConfigMap?
• An overlay needs Kubernetes Secrets derived from local key files without pasting raw secret YAML into every environment folder by hand. Which Kustomize feature addresses that pattern?
• A base kustomization.yaml must declare which YAML files belong in the build. Which field lists those manifests?
• A staging overlay directory must reuse the shared base manifests. How should its kustomization.yaml wire that relationship?
• Each environment overlay should place rendered objects into a different Kubernetes namespace without editing every resource’s metadata.namespace by hand. Which kustomization field does that?
• A team must install a third-party packaged chart with rich values, while another team only needs light YAML overlays on first-party manifests. Which tool choice is most appropriate?
• Before applying a Kustomize overlay for a inspections service, the developer wants to review the fully merged YAML. Which approach renders that output for inspection?
• A Kustomize patch is meant to update a Deployment named inspections-api, but the patch target lists the wrong kind or name and the change never appears in the build. What is the most likely cause?