Question-44: One kind of disaster recovery plan is known as a rollback plan, and its primary objective is to revert the system to its previous, working form. It might include restoring data from a cassette or reloading the configuration file into memory. The rollback plan is an emergency evacuation strategy that aims to get the system back online before the allotted period of time has passed. You have got to cut down on the quantity of erroneous production deployments that result in unexpected rollbacks on the web hosting platform that your firm uses. The QA and testing procedures were improved, which resulted in a decrease of 80 percent. Which two more strategies are available to you so that you may cut down on the rollbacks even further? (Choose two.)
A. Introduce a green-blue deployment paradigm
B. Canary releases should be used in place of the quality assurance environment.
C. Break up the monolithic platform into smaller services called microservices.
D. Reduce the dependence of the platform on the relational database.
E. Rather than using relational database systems, the platform should use a NoSQL database.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 1,3 Explanation: Option-1 & Option-3, Option-4 and Option-5 are pointless in this context. Option-3 is certainly a good practice. Now between Option-1 and Option-2. Blue green deployment is an application release model that gradually transfers user traffic from a previous version of an app or microservice to a nearly identical new release both of which are running in production. Option-3 In software, a canary process is usually the first instance that receives live production traffic about a new configuration update, either a binary or configuration rollout. The new release only goes to the canary at first. The fact that the canary handles real user traffic is key: if it breaks, real users get affected, so canarying should be the first step in your deployment process, as opposed to the last step in testing in production. While both green-blue and canary releases are useful, Option-2 suggests replacing QA with canary releases - which is not good. QA got the issue down by 80%. Hence Option-1 and Option-3, A canary release is the same as a regular release as software is being pushed to production, even if it's to a small subset of users. - A canary release doesn't guarantee detection of all issues with a small percentage of users using it as users won't be testing the app the way testers do, or may not be using all the features at a time. - In certain domains, there is a risk of reputational damage, regulatory violations and lawsuits if a canary release were to impact the user. - Given the risk associated, having a canary release capability doesn’t rule out the requirement of an exploratory tester.