Which deployment strategies will meet these requirements?
(Choose two.)
All-at-once
Rolling
Rolling with additional batch
Immutable
All-at-once with additional batch
Explanations:
The “All-at-once” strategy will deploy the new version of the application to all instances at once, which could lead to downtime and a potential loss of server capacity during deployment.
The “Rolling” strategy updates a few instances at a time. However, it may still cause downtime, as the instances being updated will temporarily be unavailable.
“Rolling with additional batch” ensures that new instances are added during the update process, maintaining the required server capacity and minimizing downtime.
“Immutable” deploys new instances with the updated version and swaps them in, ensuring no downtime or reduction in server capacity during deployment.
“All-at-once with additional batch” still involves a full deployment of the new version to all instances, which can cause downtime, even though it tries to maintain server capacity.
I deduce that the answer is:
Rolling with additional batch