nerdexam
CompTIA

CV0-002 · Question #478

An administrator needs to deploy a new release of an application in a way that allows a quick rollback to the previous version of the application. Which of the following is the BEST strategy to apply?

The correct answer is D. Deploy the application to all servers in the datacenter or cloud environment. If a rollback is. To enable quick rollback of an application release, the best strategy involves deploying the new version to a separate environment while keeping the previous version active, allowing for an instant traffic switch if issues arise.

Deployment

Question

An administrator needs to deploy a new release of an application in a way that allows a quick rollback to the previous version of the application. Which of the following is the BEST strategy to apply?

Options

  • ADeploy the application to a set of servers in small batches. If a rollback is necessary, restore the
  • BDeploy the application to a subset of servers that expose the new application. Direct all traffic to
  • CDeploy the application to the servers in a backup datacenter or secondary cloud deployment.
  • DDeploy the application to all servers in the datacenter or cloud environment. If a rollback is

How the community answered

(36 responses)
  • A
    6% (2)
  • B
    6% (2)
  • C
    19% (7)
  • D
    69% (25)

Why each option

To enable quick rollback of an application release, the best strategy involves deploying the new version to a separate environment while keeping the previous version active, allowing for an instant traffic switch if issues arise.

ADeploy the application to a set of servers in small batches. If a rollback is necessary, restore the

Deploying in small batches (rolling deployment) can be slow for a full rollback, as each batch needs to be reverted sequentially, which is not as quick as an instantaneous switch.

BDeploy the application to a subset of servers that expose the new application. Direct all traffic to

Deploying to a subset (canary deployment) only allows quick rollback for that subset; reverting the entire application still requires more steps than an instant blue/green switch.

CDeploy the application to the servers in a backup datacenter or secondary cloud deployment.

Deploying to a backup datacenter is primarily for disaster recovery or geographic redundancy, not the most direct or efficient method for rolling back a problematic application release within the primary production environment.

DDeploy the application to all servers in the datacenter or cloud environment. If a rollback isCorrect

The best strategy for a quick rollback is a Blue/Green deployment. This involves deploying the new application release to an entirely separate, identical environment (the "green" environment) while the current production version (the "blue" environment) remains active. If issues are detected with the new release, traffic can be instantly switched back to the stable "blue" environment, ensuring minimal downtime for users.

Concept tested: Application deployment strategies - Blue/Green

Source: https://learn.microsoft.com/en-us/azure/devops/pipelines/release/deployment-strategies?view=azure-devops#blue-green-deployment

Topics

#Deployment strategies#Rollback#Release management#Application updates

Community Discussion

No community discussion yet for this question.

Full CV0-002 Practice