You have an App Engine application that needs to be updated. You want to test the update with production traffic before replacing the current application version. What should you do?
A.
Deploy the update using the Instance Group Updater to create a partial rollout, which allows for canary testing.
B.
Deploy the update as a new version in the App Engine application, and split traffic between the new and current versions.
C.
Deploy the update in a new VPC, and use Google's global HTTP load balancing to split traffic between the update and current applications.
D.
Deploy the update as a new App Engine application, and use Google's global HTTP load balancing to split traffic between the new and current applications.
B. Deploy the update as a new version in the App Engine application, and split traffic between the new and current versions.
To test an update to an App Engine application with production traffic before replacing the current version, you can deploy the update as a new version in the App Engine application and split traffic between the new and current versions. This is known as a "blue-green" deployment, and it allows you to test the new version with a portion of production traffic while the current version is still serving the remainder of traffic.
To split traffic between the new and current versions, you can use the App Engine traffic splitting feature. This feature allows you to specify the percentage of traffic that should be sent to each version, and it can be used to gradually ramp up traffic to the new version over time. This allows you to test the new version with a small portion of traffic initially, and gradually increase the traffic as you become more confident in the update.
Other options, such as deploying the update in a new VPC or as a new App Engine application, are not recommended for testing updates with production traffic, as they can be more complex and may require additional steps to set up.
Answer B : You can use traffic splitting to specify a percentage distribution of traffic across two or more of the versions within a service. Splitting traffic allows you to conduct A/B testing between your versions and provides control over the pace when rolling out features.
Traffic splitting is applied to URLs that do not explicitly target a version. For example, the following URLs split traffic because they target all the available versions within the specified service:
https://cloud.google.com/appengine/docs/standard/splitting-traffic
B is right , Option D is just to confuse you.
Deploy the update as a new version in the App Engine application, and split traffic between the new and current versions.
No mate, only one app engine per project can be deployed, you can have multiple version on the same app tho. D is to confuse you. B is the only feasible answer in here.
B – Deploy the update as a new version in AppEngine app, and split traffic between the new and current versions.
Traffic Splitting is feature of AppEngine for A/B testing.
https://cloud.google.com/appengine/docs/standard/python/splitting-traffic
Answer - B
Configure how much traffic the version that you just deployed should receive.
By default, the initial version that you deploy to your App Engine application is automatically configured to receive 100% of traffic. However, all subsequent versions that you deploy to that same App Engine application must be manually configured, otherwise they receive no traffic.
For details about how to configure traffic for your versions, see Migrating and Splitting Traffic.
https://cloud.google.com/appengine/docs/admin-api/migrating-splitting-traffic
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.
KouShikyou
Highly Voted 4 years agokumarp6
3 years agonitinz
2 years, 8 months agoADVIT
Highly Voted 3 years, 8 months agoomermahgoub
Most Recent 10 months, 2 weeks agoomermahgoub
10 months, 2 weeks agoTonytheTiger
11 months agomegumin
11 months, 4 weeks agoAzureDP900
1 year agoDrishaS4
1 year, 3 months agoghadxx
1 year, 8 months agoharoldbenites
1 year, 11 months agoale_brd_111
11 months, 2 weeks agovincy2202
1 year, 11 months agorobotgeek
1 year, 12 months agoMaxNRG
2 years ago[Removed]
2 years agounnikrisb
2 years agovictory108
2 years, 5 months agoun
2 years, 5 months agogetzsagar
2 years, 6 months ago