C9510-418 · Question #23
When deploying a new edition of an application, which edition rollout configuration option should be used to ensure that the two editions of the application are not active at the same time?
The correct answer is A. Atomic. Performing an atomic rollout to an edition replaces an edition on half of the cluster at a time to serve all user requests with a consistent edition of the application. All user requests are served by either the previous or the new edition; user requests are never served by…
Question
When deploying a new edition of an application, which edition rollout configuration option should be used to ensure that the two editions of the application are not active at the same time?
Options
- AAtomic
- BGrouped
- CSoft reset
- DHard reset
How the community answered
(29 responses)- A86% (25)
- B3% (1)
- C3% (1)
- D7% (2)
Explanation
Performing an atomic rollout to an edition replaces an edition on half of the cluster at a time to serve all user requests with a consistent edition of the application. All user requests are served by either the previous or the new edition; user requests are never served by both editions. An atomic rollout ensures that all application requests are served by a consistent edition, for example, either edition 1.0 or 2.0, but not by both.
Topics
Community Discussion
No community discussion yet for this question.