> For the complete documentation index, see [llms.txt](https://atomoh.gitbook.io/kubernetes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomoh.gitbook.io/kubernetes/en/quiz-collection/gitops/argocd/05-traffic-management-quiz.md).
# Traffic Management Quiz
This quiz tests your understanding of progressive delivery and traffic management with ArgoCD and Argo Rollouts.
1. What is Argo Rollouts?
* A) A logging solution for ArgoCD
* B) A Kubernetes controller for progressive delivery strategies
* C) A Git branch management tool
* D) A traffic monitoring dashboard
Show Answer
**Answer: B) A Kubernetes controller for progressive delivery strategies**
**Explanation:** Argo Rollouts is a Kubernetes controller that provides advanced deployment capabilities like canary deployments, blue-green deployments, and progressive delivery with automated analysis.
2. Which deployment strategy gradually shifts traffic from the old version to the new version?
* A) Recreate
* B) Rolling Update
* C) Canary
* D) Blue-Green
Show Answer
**Answer: C) Canary**
**Explanation:** Canary deployments gradually shift traffic from the old version to the new version in increments (e.g., 10%, 25%, 50%, 100%), allowing for testing and validation at each step.
3. In a Blue-Green deployment with Argo Rollouts, what happens during promotion?
* A) The blue environment is deleted
* B) Traffic is switched from the stable (blue) to the preview (green) service
* C) Both versions run simultaneously forever
* D) A new environment is created
Show Answer
**Answer: B) Traffic is switched from the stable (blue) to the preview (green) service**
**Explanation:** In Blue-Green deployments, promotion switches traffic from the current stable version to the preview version by updating the active service selector. The old ReplicaSet is scaled down after promotion.
4. What is an AnalysisTemplate in Argo Rollouts?
* A) A template for creating new applications
* B) A definition of metrics and success criteria for automated canary analysis
* C) A logging configuration
* D) A resource quota template
Show Answer
**Answer: B) A definition of metrics and success criteria for automated canary analysis**
**Explanation:** AnalysisTemplates define metrics to query (from Prometheus, Datadog, etc.) and success/failure criteria. During a rollout, AnalysisRuns execute these templates to automatically determine if a deployment should proceed.
5. Which Ingress controller has native integration with Argo Rollouts for traffic splitting?
* A) Traefik only
* B) NGINX Ingress only
* C) Multiple including NGINX, ALB, Istio, and Traefik
* D) None, manual configuration is required
Show Answer
**Answer: C) Multiple including NGINX, ALB, Istio, and Traefik**
**Explanation:** Argo Rollouts has native traffic management integrations with multiple ingress controllers and service meshes including NGINX Ingress, AWS ALB, Istio, Linkerd, SMI, and Traefik.
6. What does the `setWeight` step do in a Canary strategy?
* A) Sets the CPU weight for pods
* B) Sets the percentage of traffic to route to the canary version
* C) Sets the importance of the deployment
* D) Sets the rollback threshold
Show Answer
**Answer: B) Sets the percentage of traffic to route to the canary version**
**Explanation:** The `setWeight` step in a canary strategy configures what percentage of traffic should be routed to the canary (new) version. For example, `setWeight: 20` routes 20% of traffic to the canary.
7. What happens when an AnalysisRun fails during a canary deployment?
* A) The deployment continues regardless
* B) An alert is sent but nothing else happens
* C) The rollout is automatically aborted and rolled back
* D) The cluster is shut down
Show Answer
**Answer: C) The rollout is automatically aborted and rolled back**
**Explanation:** When an AnalysisRun fails (metrics exceed failure thresholds), Argo Rollouts automatically aborts the rollout and initiates a rollback to the stable version, preventing bad deployments from affecting all traffic.
8. How can you pause a Rollout at a specific step for manual verification?
* A) Using the `pause` step with no duration
* B) Using the `stop` step
* C) Using the `wait` step with duration: forever
* D) It's not possible
Show Answer
**Answer: A) Using the `pause` step with no duration**
**Explanation:** Adding a `pause` step without a duration creates an indefinite pause that requires manual promotion (via CLI or UI) to continue. This is useful for manual verification gates in the deployment process.
9. How do you split canary traffic through the Kong Ingress Controller?
* A) Use the `trafficRouting.kong` field directly
* B) Manipulate an HTTPRoute via the Gateway API plugin (`trafficRouting.plugins`)
* C) Kong cannot be integrated with Argo Rollouts
* D) Route around it using an Istio VirtualService
Show Answer
**Answer: B) Manipulate an HTTPRoute via the Gateway API plugin (`trafficRouting.plugins`)**
**Explanation:** Kong has no native Argo Rollouts integration — there is no `trafficRouting.kong` field. It is supported only through argoproj-labs' Gateway API plugin, which manipulates a standard HTTPRoute resource. Other Gateway API-compliant controllers, such as Traefik and kgateway, use the same plugin.
10. What resource does the Argo Rollouts Gateway API plugin actually update at each canary weight step?
* A) The Service's `selector` labels
* B) The Ingress's `canary-weight` annotation
* C) The HTTPRoute's `backendRefs[].weight`
* D) The DestinationRule's subset labels
Show Answer
**Answer: C) The HTTPRoute's `backendRefs[].weight`**
**Explanation:** The Gateway API plugin directly updates the standard Gateway API HTTPRoute resource's `backendRefs[].weight` values at each setWeight step. This is a universal mechanism that applies identically to any controller implementing Gateway API — Kong, Traefik, kgateway, and others.