You deploy a new release of an internal application during a weekend maintenance window when there is minimal user traffic. After the window ends, you learn that one of the new features isn't working as expected in the production environment. After an extended outage, you roll back the new release and deploy a fix. You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in the future.
What should you do? Choose 2 answers
- Before merging new code, require 2 different peers to review the code changes.
- Adopt the blue/green deployment strategy when releasing new code via a CD server.
- Integrate a code linting tool to validate coding standards before any code is accepted into the repository.
- Require developers to run automated integration tests on their local development environments before release.
- Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.