Answer-first summary for fast verification
Answer: Introduce the new version with traffic splitting to direct a small fraction of traffic to it.
The optimal strategy is **D**, leveraging traffic splitting to safely test the new version with a subset of live traffic. This method minimizes risk by allowing for immediate rollback without affecting all users. - **Option A** is risky as deploying the new version as default could disrupt all users if the update fails. - **Option B**, while feasible, introduces unnecessary complexity with data synchronization and external traffic management. - **Option C** misuses App Engine services, which are designed for distinct service logic, not for version testing, requiring manual client-side adjustments. Traffic splitting is a feature designed for scenarios like this, enabling smooth transitions and A/B testing without downtime.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are managing an application on Google App Engine that handles live production traffic. A critical yet potentially disruptive update needs to be deployed. Given that the update's effectiveness can only be verified with actual user traffic, what is the best approach to test this feature?
A
Temporarily deploy the new version and revert if issues arise.
B
Isolate the new application in a separate project and gradually introduce users to it.
C
Establish a new App Engine service and redirect a portion of clients to it for testing.
D
Introduce the new version with traffic splitting to direct a small fraction of traffic to it.
No comments yet.