Question-1: One of the senior members of your DevOps team from the Corporate Technology department is monitoring your activity in relation to a common and recurring issue with the pipeline that they designed and built, with the help of which it is possible to deploy modifications to your source code to your infrastructure in instance groups in order to facilitate self-healing. Your key performance metric will suffer as a direct consequence of one of the adjustments. You are unsure of what the best course of action is, and the inquiry might take up to a week. What is it that you ought to do?
A. Connect to a server, and work on the fix in your own environment.
B. Revert the source code change, and rerun the deployment pipeline
C. Log into the servers with the bad code change, and swap in the previous code
D. Change the instance group template to the previous one, and delete all instances
Correct Answer

Get All 340 Questions and Answer for Google Professional Cloud Architect

: 2 Explanation: To begin, you will need to roll back the problematic code that was the initial cause of this issue. You are able to restore a poor template; but, if another user submits code changes to the repository, you will once again have the build with broken code, which will then be deployed to your servers. When you revert your problematic code, you are free to explore in another branch for a week without worrying that any other code change will deploy poor code again. This freedom comes at the expense of having to worry about whether or not any other code commit will deploy terrible code. Self-healing, not auto-healing, is the watchword here; this indicates that MIG is not being employed. Let's rule out the other possibilities first. Option 1: Connect locally to a server and work through the problem step-by-step: Because of the length of this phase, it must be eliminated. Option 2: Roll back the modification to the source code and reprocess the deployment pipeline: The source repository will be updated with a record of this reversion. We will proceed in this manner. Option-3:. logon to the servers with the changed faulty code, and then swap in the old code. This is a manual process that can be automatically performed by options 2 and 3, therefore it can be eliminated. Option 4: Revert the instance group template to the one that was used before, and remove all instances: This is comparable to option 2, but why carry out by hand something that may be done automatically? Hence remove. But the opposite is also true. The correct answer is option 4. But when considering the code lifespan, option 2 is the best choice.