How to Fix Negative Performance Impact of Source Code Changes
Question
You created a pipeline that can deploy your source code changes to your infrastructure in instance groups for self-healing.
One of the changes negatively affects your key performance indicator.
You are not sure how to fix it, and investigation could take up to a week.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B.
In this scenario, you have created a pipeline that can deploy your source code changes to your infrastructure in instance groups for self-healing. However, one of the changes you made negatively affects your key performance indicator, and you are not sure how to fix it. The investigation could take up to a week, so you need to take some immediate action to mitigate the issue.
Option A: Log in to a server, and iterate on the fix locally This option is not recommended as it requires direct access to the server and could introduce further issues if the iteration process is not done correctly. Moreover, it is not scalable, and it does not ensure that the code changes will be properly propagated to all instances in the instance group.
Option B: Revert the source code change, and rerun the deployment pipeline This is the recommended option in this scenario. Reverting the source code change ensures that the previous working version of the code is deployed, which will mitigate the negative impact on the key performance indicator. Rerunning the deployment pipeline will ensure that all instances in the instance group are updated with the previous working version of the code. This option is scalable, and it minimizes the risk of introducing further issues.
Option C: Log into the servers with the bad code change, and swap in the previous code This option is not recommended as it requires direct access to the servers, which is not scalable and could introduce further issues if the swapping process is not done correctly. Moreover, it does not ensure that all instances in the instance group are updated with the previous working version of the code.
Option D: Change the instance group template to the previous one, and delete all instances. This option is not recommended as it is too drastic and will delete all instances, including those that are running the previous working version of the code. This option is not necessary in this scenario as the issue can be mitigated by reverting the source code change and rerunning the deployment pipeline.
In summary, the recommended option in this scenario is to revert the source code change and rerun the deployment pipeline to ensure that all instances in the instance group are updated with the previous working version of the code.
