Exam 350-901 topic 1 question 177 discussion

correct answer: B&E VIP will direct the requests to the up-and-running containers while rolling upgrades will perform one upgrade at a time: Stop the first task. Schedule update for the stopped task. Start the container for the updated task. If the update to a task returns RUNNING, wait for the specified delay period then start the next task. https://docs.docker.com/engine/swarm/swarm-tutorial/rolling-update/

B and E are correct VIP will direct the requests to the up-and-running containers while rolling upgrades will perform one upgrade at a time: Stop the first task. Schedule update for the stopped task. Start the container for the updated task. If the update to a task returns RUNNING, wait for the specified delay period then start the next task. If, at any time during the update, a task returns FAILED, pause the update. https://docs.docker.com/engine/swarm/swarm-tutorial/rolling-update/

I think BE is correct.

service needs something in front of containers to direct to available running ones

Update a service🔗 docker service update --limit-cpu 2 redis Perform a rolling restart with no parameter changes docker service update --force --update-parallelism 1 --update-delay 30s redis In this example, the --force flag causes the service’s tasks to be shut down and replaced with new ones even though none of the other parameters would normally cause that to happen. The --update-parallelism 1 setting ensures that only one task is replaced at a time (this is the default behavior). The --update-delay 30s setting introduces a 30 second delay between tasks, so that the rolling restart happens gradually. https://docs.docker.com/engine/reference/commandline/service_update/ https://github.com/douglasmiranda/lab/tree/master/docker-swarm-replicated-example-caddy%2Bflask