Choose the best description of the canary deployment pattern in software delivery.
Think about how to reduce risk when releasing new software.
Canary deployment means releasing a new version to a small group first to catch issues early before full rollout.
Given the command below, what will it show?
docker service ls --filter name=myapp_canary
Check how Docker filters services by name.
The command filters and lists services with names matching 'myapp_canary', showing the canary deployment service.
Choose the correct Docker Compose service configuration to deploy a canary version receiving 10% of traffic using Docker Swarm.
version: '3.8' services: web: image: myapp:stable deploy: replicas: 9 web_canary: image: myapp:canary deploy: replicas: 1
Think about how replica counts relate to traffic distribution in Docker Swarm.
Setting 9 replicas for stable and 1 for canary means 10% of total replicas run canary, approximating 10% traffic.
You deployed a canary service with 1 replica alongside 9 stable replicas. However, no user traffic reaches the canary. What is the most likely cause?
Consider how traffic routing works in a multi-service deployment.
If the load balancer routes only to stable replicas, canary replicas get no traffic despite being up.
Arrange these steps in the correct order to perform a canary deployment safely.
Think about deploying first, then routing traffic, monitoring, and finally full rollout.
First deploy canary replicas, then route traffic to them, monitor results, and if all is good, roll out fully.