The development team has deployed multiple deployment versions using AWS CodeDeploy.
One of the Deployment sessions with overwrite content option has failed.
You need to immediately roll back to the previously working application version with all the necessary files required for the application.
Which of the following options is most suited to meet this requirement?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - A.
When there is a deployment phase with a content overwrite option as “Overwrite”, it will delete all files from the previous deployment session.
If this deployment fails, to restore to the previous working deployment, either Manual or Automatic rollback must be enabled.
Also, deleted files as a part of the failed deployment phase need to be added manually.
Option B is incorrect as Manually Rollback must be done to the previous working application version & not to a previous failed version.
Option C is incorrect as Automatic Rollback will deploy a new version but will not copy files that are deleted by the previous deployment.
Option D is incorrect as Manually Rollback will deploy a new version but will not copy files that are deleted by the previous deployment.
For more information on AWS CodeDeploy Rollbacks, refer to the following URL-
https://docs.aws.amazon.com/codedeploy/latest/userguide/deployments-rollback-and-redeploy.html#deployments-rollback-and-redeploy-content-optionsThe most appropriate option to roll back to the previously working application version with all the necessary files required for the application is option C - "Automatically rollback to the last known application version which will add files required for application revision".
AWS CodeDeploy is a deployment service that enables developers to automate deployment of their applications to instances and update the code running on those instances. CodeDeploy can deploy application revisions to one or many instances at the same time. It can also deploy the same application revision to different environments. AWS CodeDeploy supports two types of deployments: In-place deployment and Blue/Green deployment.
When an AWS CodeDeploy deployment fails, it automatically rolls back to the last known application version that was successfully deployed, depending on the deployment settings. Option C suggests automatically rolling back to the last known application version, and it also mentions that this version will include the necessary files required for the application.
This option is most suitable as it ensures that the previously working application version is restored with all the necessary files required for the application. It saves time and effort, as it automatically restores the working version without requiring any manual intervention. Additionally, it minimizes the chances of errors and mistakes that could occur during a manual rollback or revision process.
Option A suggests automatically rolling back to the last known application version, but it also suggests manually adding the files required for the application revision. This option is not appropriate, as it introduces the possibility of human error during the manual addition of files. Option B suggests manually rolling back to the previous deployment phase and adding the files required for the application revision. This option is also not appropriate, as it requires more manual effort and is more time-consuming.
Option D suggests manually rolling back to the last known application version and adding the files required for the application revision. This option is not appropriate, as it is time-consuming and increases the risk of errors and mistakes.
In conclusion, the most appropriate option to roll back to the previously working application version with all the necessary files required for the application is option C - "Automatically rollback to the last known application version which will add files required for application revision".