You need to deploy an update to an application in Google App Engine. The update is risky, but it can only be tested in a live environment. What is the best way to introduce the update to minimize…

Question

Options

• ADeploy a new version of the application but use traffic splitting to only direct a small number of
• BDeploy the application temporarily and be prepared to pull it back if needed.
• CWarn users that a new app version may have issues and provide a way to contact you if there are
• DCreate a new project with the new app version, then redirect users to the new version.

• A
  92% (24)
• B
  4% (1)
• C
  4% (1)

Explanation

A (Correct Answer) - Deploying a new version without assigning it as the default version will not create downtime for the application. Using traffic splitting allows for easily redirecting a small amount of traffic to the new version and can also be quickly reverted without application B - Deploy the application temporarily and be prepared to pull it back if needed. Deploying the application new version as default requires moving all traffic to the new version. This could impact all users and disable the service during the new version’s live time. C - Warn users that a new app version may have issues and provide a way to contact you if there are problems. We won’t recommend this practice. D - Create a new project with the new app version, then redirect users to the new version. Deploying a second project requires data synchronization and having an external traffic splitting solution to direct traffic to the new application. While this is possible, with Google App Engine, these manual steps are not required.

No community discussion yet for this question.