Study for the CompTIA Cloud+ Test with our comprehensive material. Use interactive quizzes and detailed explanations to get ready for your certification exam!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


To achieve minimal downtime and quick rollback during deployment, which approach should the cloud administrator use?

  1. Use a rolling deployment to update all servers.

  2. Deploy the application to the PROD cloud environment and previous version to QA.

  3. Deploy the application to a subset of servers and route traffic accordingly.

  4. Deploy the application to a staging environment and force a failover.

The correct answer is: Use a rolling deployment to update all servers.

The approach that ensures minimal downtime and quick rollback during deployment is to use a rolling deployment to update all servers. Rolling deployments work by updating servers in a staggered fashion, meaning that some servers are taken down to receive the upgrade while others remain online and operational. This method allows for continuous service availability, as it avoids the scenario where the entire application or service is taken offline for an upgrade. By using a rolling deployment, if any issues arise, rolling back can be accomplished by simply stopping the deployment process and reverting the updated servers to their previous state, minimizing the impact on end-users. This strategy is particularly effective in cloud environments where resources can be managed dynamically and allows for quick adjustments as feedback is received. The other options do not effectively address both the need for minimal downtime and quick rollback. For example, deploying to the PROD cloud while having the previous version in QA does not allow for immediate rollback in a live environment, potentially leading to service interruption. Similarly, deploying to a subset of servers and routing traffic accordingly may introduce complexities in management and could still have service disruptions if the deployment fails. Finally, deploying to a staging environment and forcing a failover might not directly facilitate a quick rollback during live changes in the production environment.