PROFESSIONAL-CLOUD-DEVELOPER · Question #242
Before promoting your new application code to production, you want to conduct testing across a variety of different users. Although this plan is risky, you want to test the new version of the…
The correct answer is B. Deploy your application on Google Kubernetes Engine with Anthos Service Mesh. Use traffic. The key requirements are: (1) route traffic based on operating system, (2) test with real production users (canary/traffic splitting), and (3) enable fast rollback. Google Kubernetes Engine with Anthos Service Mesh (built on Istio) is the correct choice because Istio supports…
Question
Before promoting your new application code to production, you want to conduct testing across a variety of different users. Although this plan is risky, you want to test the new version of the application with production users and you want to control which users are forwarded to the new version of the application based on their operating system. If bugs are discovered in the new version, you want to roll back the newly deployed version of the application as quickly as possible. What should you do?
Options
- ADeploy your application on Cloud Run. Use traffic splitting to direct a subset of user traffic to the
- BDeploy your application on Google Kubernetes Engine with Anthos Service Mesh. Use traffic
- CDeploy your application on App Engine. Use traffic splitting to direct a subset of user traffic to the
- DDeploy your application on Compute Engine. Use Traffic Director to direct a subset of user traffic
How the community answered
(28 responses)- A11% (3)
- B75% (21)
- C11% (3)
- D4% (1)
Explanation
The key requirements are: (1) route traffic based on operating system, (2) test with real production users (canary/traffic splitting), and (3) enable fast rollback. Google Kubernetes Engine with Anthos Service Mesh (built on Istio) is the correct choice because Istio supports fine-grained, attribute-based traffic routing - including routing based on HTTP headers such as User-Agent, which carries OS information. Cloud Run (A) and App Engine (C) traffic splitting is percentage-based or IP/cookie-based, not OS-based. Compute Engine with Traffic Director (D) can do header-based routing but requires significantly more infrastructure management. GKE + Anthos Service Mesh also supports instant rollback by shifting traffic weights back to the previous version.
Topics
Community Discussion
No community discussion yet for this question.