Answer-first summary for fast verification
Answer: Deploy a new version of the application, and use traffic splitting to send a small percentage of traffic to it.
The correct approach is to deploy a new version of the application and use traffic splitting to direct a small portion of traffic to it. This method minimizes risk by allowing you to monitor the new version's performance with a fraction of your users before fully committing. If issues arise, you can quickly revert traffic to the stable version without significant downtime or impact. This strategy also avoids the increased costs and complexities associated with setting up duplicate environments or manually managing user transitions to new services. Traffic splitting within Google App Engine provides a cost-effective and efficient way to test changes in a live environment with minimal risk.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
After deploying a new application on Google App Engine for production traffic, you've identified issues in the application code and developed a fix. However, some scenarios in the fix can only be validated by end-users with access to specific production data. The Change Approval Board has concerns about the potential risk of the application going down due to the fix but agrees it's necessary. You're tasked with proposing a solution that minimizes both the impact of a potential failure and costs. What should you do?
A
Set up a second Google App Engine service, and then update a subset of clients to hit the new service.
B
Deploy a new version of the application, and use traffic splitting to send a small percentage of traffic to it.
C
Create a second Google App Engine project with the new application code, and onboard users gradually to the new application.
D
Deploy the new application version temporarily, capture logs and then roll it back to the previous version.
No comments yet.