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?
A.
Deploy the new version in the same application and use the --migrate option.
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.
C.
Create a new App Engine application in the same project. Deploy the new version in that application. Use the App Engine library to proxy 1% of the requests to the new version.
D.
Create a new App Engine application in the same project. Deploy the new version in that application. Configure your network load balancer to send 1% of the traffic to that new application.
more over, in app engine we cannot create "new application", we have to create a new Project to do that, an app engine projet has 1 application (which can have multiple versions and services)
The correct answer is B.
By using the App Engine's traffic splitting feature, we can easily direct a certain percentage of traffic to a specific version of our application. In this case, we want to send 1% of traffic to the new test version and keep the remaining 99% on the current version. This can be achieved by deploying the new version in the same application and using the `--splits` option to give a weight of 99 to the current version and a weight of 1 to the new version.
Answer A is incorrect because the `--migrate` option is used for migrating traffic to a new version after it has been fully tested and is ready for full deployment.
Answer C is incorrect because it requires additional configuration to proxy requests to the new version, increasing complexity unnecessarily.
Answer D is incorrect because it involves configuring a network load balancer, which is not necessary for this use case and adds unnecessary complexity.
While I agree with your choice and your explanation of B. I also believe C and D are wrong simply because you can only have one App Engine within a project https://cloud.google.com/appengine/docs/flexible/managing-projects-apps-billing#:~:text=Important%3A%20Each%20Cloud%20project%20can,of%20your%20App%20Engine%20application.
B! A very natural answer… Perfect for switching users over to new version. Imagine creating multiple projects to update App Engine deployments, isn’t that logically unnecessary?
b is my answer.
a: --migrate is for enabling gradual traffic migration as opposed to migrating traffic immediately
c & d: no need to create a project. You can split the traffic any time
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
yasu
Highly Voted 4 years, 1 month agosanhoo
2 years, 11 months agonmnm22
5 months, 3 weeks agoYAS007
2 years, 9 months agoGini
Highly Voted 4 years agoCaptain1212
Most Recent 7 months, 3 weeks agoBuruguduystunstugudunstuy
1 year, 2 months agoJelly_Wang
12 months agocslince
1 year, 4 months agoleogor
1 year, 6 months agoCornholio_LMC
1 year, 7 months agohabros
1 year, 8 months agoMadj
1 year, 10 months agoAzureDP900
1 year, 10 months agomplibunao
1 year, 10 months agoharoldbenites
1 year, 10 months agoDurgesh1997
2 years, 2 months agoPriyankahere
2 years, 3 months ago[Removed]
2 years, 3 months agovishnukumartr
2 years, 5 months agoJaira1256
2 years, 5 months ago