nerdexam
CompTIA

CV0-003 · Question #269

A development team released a new version of an application and wants to deploy it to the cloud environment with a faster rollback and minimal downtime. Which of the following should the cloud…

The correct answer is A. Use a rolling deployment to update all the servers in the PROD cloud environment with the new. This question asks which deployment strategy provides minimal downtime and supports faster rollback when releasing a new application version.

Deployment

Question

A development team released a new version of an application and wants to deploy it to the cloud environment with a faster rollback and minimal downtime. Which of the following should the cloud administrator do to achieve this goal?

Options

  • AUse a rolling deployment to update all the servers in the PROD cloud environment with the new
  • BDeploy the application to the PROD cloud environment and the previous version to QA. To switch
  • CDeploy the application to a subset of servers in the environment and route traffic to these servers.
  • DDeploy the application to a staging environment and force a failover to this environment. To

How the community answered

(27 responses)
  • A
    78% (21)
  • B
    11% (3)
  • C
    4% (1)
  • D
    7% (2)

Why each option

This question asks which deployment strategy provides minimal downtime and supports faster rollback when releasing a new application version.

AUse a rolling deployment to update all the servers in the PROD cloud environment with the newCorrect

A rolling deployment updates servers incrementally in batches rather than all at once, so a portion of production servers always continues serving traffic and downtime is minimized. If a defect is detected early in the roll, only the already-updated instances need to be reverted, making rollback faster and less disruptive than a full cutover.

BDeploy the application to the PROD cloud environment and the previous version to QA. To switch

Deploying the new version directly to PROD while keeping the old version in QA does not protect production users during the transition and complicates rollback.

CDeploy the application to a subset of servers in the environment and route traffic to these servers.

Routing traffic only to a subset of updated servers is a canary deployment pattern, which is useful for risk reduction but does not minimize overall downtime as efficiently as rolling all instances progressively.

DDeploy the application to a staging environment and force a failover to this environment. To

Forcing a failover from staging to production treats the staging environment as the active tier, which is non-standard and introduces risk from environment configuration differences.

Concept tested: Rolling deployment for minimal downtime and rollback

Source: https://learn.microsoft.com/en-us/azure/devops/pipelines/process/deployment-jobs

Topics

#deployment strategy#rollback#rolling deployment#minimal downtime

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CV0-003 Practice