You have a website hosted on App Engine standard environment.
You want 1% of your users to see a new test version of the website.
You want to minimize complexity.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
The correct answer for this scenario is B. Deploy the new version in the same application and use the --splits option to give a weight of 99 to the current version and a weight of 1 to the new version.
Explanation:
The App Engine standard environment is a platform as a service (PaaS) offering that allows developers to easily build and deploy web applications in the Google Cloud Platform (GCP) without having to manage the underlying infrastructure. The standard environment is a fully managed environment that provides automatic scaling, high availability, and security.
To test a new version of a website with a subset of users, the recommended approach is to use traffic splitting. Traffic splitting is a feature that allows you to split the incoming traffic between different versions of your application based on defined percentages. In this scenario, you want to route 1% of the incoming traffic to the new test version, and 99% of the traffic to the current version of the website.
Option A is not the correct answer as using the --migrate option will deploy the new version and migrate all traffic to the new version, which is not what is required in this scenario.
Option C is not the correct answer as creating a new App Engine application will increase the complexity of the setup, and using the App Engine library to proxy requests to the new version will add additional overhead to the application and slow down the response time.
Option D is not the correct answer as configuring a network load balancer to send 1% of the traffic to the new application will increase the complexity of the setup and may result in slower response times for the new version.
Therefore, option B is the correct answer, as it allows you to deploy the new version in the same application, which minimizes complexity, and use the --splits option to route 1% of the incoming traffic to the new test version, while still serving 99% of the traffic to the current version of the website.