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

Questions 6–10

1. 6expert · hard

   A company is performing a blue/green deployment for a critical application. They have blue (v1) and green (v2) Deployments. The green Deployment has a readiness probe configured. They update the Service selector to point to green. Immediately after the switch, they notice that some users are getting errors. The green pods are all Ready. What is the most likely cause?

   • AThe green application has a bug that only manifests under real user traffic, which the readiness probe does not catch.
   • BThe green Deployment was scaled too quickly, causing resource exhaustion.
   • CThe Service selector was not updated correctly and is still pointing to blue.
   • DThe green Deployment does not have a liveness probe, so unhealthy pods are not being restarted.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   In a Kubernetes blue/green deployment, how is traffic switched from the blue version to the green version?

   • ABy updating the Service selector to match the labels of the green Deployment's pods
   • BBy deleting the blue Deployment and creating a new one with the same name
   • CBy updating the Ingress resource to use a different hostname for the green version
   • DBy scaling the blue Deployment to zero and the green Deployment to the desired replicas
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   In a blue/green deployment, what is the typical role of the 'blue' environment?

   • AThe environment that is always kept idle and never receives traffic
   • BThe environment that contains the new version before traffic is switched
   • CThe environment used for development and testing only
   • DThe environment that receives all production traffic initially
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A team is running a canary deployment for an API. They have 'api-v1' and 'api-v2' Deployments, each with its own Service. They are using an Ingress with a 90/10 weight split. They want to shift to a 50/50 split, but they also want to ensure that the v2 Service is healthy before increasing its traffic share. What should they do?

   • AUpdate the Ingress weights to 50/50 and then check the v2 Service's health.
   • BScale the v2 Deployment to match v1's replica count, then update the Ingress weights.
   • CCreate a new Service for v2 with a different name and update the Ingress to point to it.
   • DCheck the v2 Service's endpoints and the readiness of the v2 pods, then update the Ingress weights to 50/50.
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   In a blue/green deployment, what is the simplest way to roll back to the previous version after traffic has been switched to green?

   • AUse kubectl rollout undo on the green Deployment
   • BScale the green Deployment to zero and the blue Deployment to the desired replicas
   • CUpdate the Service selector back to 'version: blue'
   • DDelete the green Deployment and recreate it with the blue image
   Reveal Solution Discussion Select an answer first