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

Questions 26–27

1. 26foundation · easy

   In a canary deployment using Kubernetes, how can you initially route a small percentage of traffic to the new version?

   • ABy creating two Deployments and using a Service with a selector that matches both, then adjusting replica counts to control the proportion of traffic
   • BBy creating a single Deployment and using the kubectl rollout pause command
   • CBy updating the Service's clusterIP to a different address for each version
   • DBy using a ConfigMap to define which users should receive the new version
   Reveal Solution Discussion Select an answer first
2. 27expert · hard

   A team is running a canary deployment for a web application. They have 'web-v1' and 'web-v2' Deployments, each with its own Service. They are using an Ingress with a 50/50 weight split. They want to gradually increase traffic to v2 over time, but they also want to be able to roll back quickly if issues arise. They are considering two approaches: (1) manually updating the Ingress weights, or (2) using a progressive delivery tool. What is the primary advantage of using a progressive delivery tool in this scenario?

   • AIt can automatically analyze metrics and roll back if error rates increase, without manual intervention.
   • BIt automatically scales the canary Deployment to match the stable Deployment's replica count.
   • CIt eliminates the need for separate Services for each version.
   • DIt requires no changes to the Ingress or Service configuration.
   Reveal Solution Discussion Select an answer first