IT Service Management and Systems Audit
Several approved changes are bundled into a release and deployed to the production environment. Which of the following is an appropriate way to carry out release management?
- AA release that has been tested in an environment close to production is deployed after a deployment procedure and a back-out plan for returning to the original state on failure have been prepared
- BBecause it was confirmed to work correctly in the development environment, testing in an environment close to production is skipped and the release is deployed at night when usage is low
- CA deployment procedure document is prepared, but the procedure for returning to the original state is worked out only after deployment, once a problem has occurred
Show answer and explanation
Answer: A. A release that has been tested in an environment close to production is deployed after a deployment procedure and a back-out plan for returning to the original state on failure have been prepared
In release management, a release that bundles approved changes is planned, tested in an environment close to production and deployed to the production environment by a set procedure. A back-out plan for returning to the original state is prepared in advance in case the deployment fails or a serious problem is found after deployment. After deployment, the result is checked and the configuration management information is updated.
- A. Correct. A tested release is deployed with a deployment procedure and a back-out plan prepared.
- B. The development and production environments differ in settings, data volume, connected equipment and so on, so problems that occur only in production are missed.
- C. Working out how to go back only after a problem occurs makes recovery slow and the impact large.
Continue: 9 more IT Service Management and Systems Audit questions