Use Kubernetes Primitives to Implement Common Deployment Strategies (e.g. Blue/green or Canary) CKAD Practice Questions (Page 5)

Questions 21–25

1. 21expert · hard

   A team is performing a blue/green deployment. The green Deployment has a readiness probe that checks an HTTP endpoint. The probe has an initialDelaySeconds of 30 and a periodSeconds of 10. They update the Service selector to green immediately after creating the green Deployment. What is the most likely outcome?

   • AThe green pods will be Ready immediately because the readiness probe is not required for the Service to route traffic.
   • BThe Service will automatically wait for the green pods to become Ready before routing traffic.
   • CThe green pods will be Ready after 30 seconds, and the Service will route traffic to them without any errors.
   • DUsers may experience errors for the first 30-40 seconds because the green pods are not yet Ready, and the Service has no healthy endpoints.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   What is the primary advantage of keeping the old version running during a blue/green deployment?

   • AIt eliminates the need for health checks
   • BIt enables instant rollback by switching traffic back to the old version
   • CIt reduces the total number of pods running in the cluster
   • DIt allows both versions to serve traffic simultaneously for load balancing
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A company is using a blue/green deployment strategy. The blue Deployment (v1) is currently serving traffic via a Service with selector 'app=web, version=blue'. The green Deployment (v2) is running and healthy. The team wants to switch to green, but they also want to keep the blue Deployment running for a while to allow for a quick rollback. After switching the Service selector to green, what should they do with the blue Deployment?

   • ADelete the blue Deployment immediately to avoid confusion.
   • BScale the blue Deployment to zero replicas to save resources.
   • CLeave the blue Deployment running as-is, so it can be used for rollback by reverting the Service selector.
   • DUpdate the blue Deployment's image to match green, so both are identical.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   What is the minimum number of Deployments required to implement a blue/green deployment in Kubernetes?

   • AThree
   • BTwo
   • COne
   • DFour
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A team wants to test a new feature with a small subset of internal users before rolling it out to everyone. They have a stable v1 Deployment and a new v2 Deployment. They want to route traffic from specific internal IP addresses to v2, while all other traffic goes to v1. Which approach best achieves this?

   • AUse a NetworkPolicy to allow only internal IPs to access the v2 Service.
   • BScale v2 to a small number of replicas and rely on Kubernetes load balancing to send some traffic to it.
   • CCreate a second Service for v2 and update the main Service selector to include both versions.
   • DUse an Ingress with a header-based or IP-based routing rule to send requests from internal users to the v2 Service, and all other requests to the v1 Service.
   Reveal Solution Discussion Select an answer first