Public-works inspectors need a new image of the field-notes API with no Saturday outage. Which orchestration role updates replicas so clients keep working under the same service name?
Select an answer to reveal the explanation.
Short Explanation
Rolling replace is like swapping train cars while the train stays on the track. New replicas come up, old ones leave, and the service name keeps answering. A stop-the-world Saturday docker restart is what orchestration is meant to retire.
Full Explanation
A core orchestration role is rolling replacement of workloads: new replicas using the updated image are brought up and old replicas are drained or terminated under the same service identity so clients experience continuity. Cluster-wide delete/recreate and documentation-only tag changes do not perform a live rollout. Full stop/start maintenance windows are the pattern rolling updates replace.