Topic 1 Question 239

Professional Cloud Developer

Topic 1 Question 239
You need to deploy an internet-facing microservices application to Google Kubernetes Engine (GKE). You want to validate new features using the A/B testing method. You have the following requirements for deploying new container image releases: • There is no downtime when new container images are deployed. • New production releases are tested and verified using a subset of production users.

What should you do?
- 1. Configure your CI/CD pipeline to update the Deployment manifest file by replacing the container version with the latest version.
  2. Recreate the Pods in your cluster by applying the Deployment manifest file.
  3. Validate the application's performance by comparing its functionality with the previous release version, and roll back if an issue arises.
- 1. Create a second namespace on GKE for the new release version.
  2. Create a Deployment configuration for the second namespace with the desired number of Pods.
  3. Deploy new container versions in the second namespace.
  4. Update the Ingress configuration to route traffic to the namespace with the new container versions.
- 1. Install the Anthos Service Mesh on your GKE cluster.
  2. Create two Deployments on the GKE cluster, and label them with different version names.
  3. Implement an Istio routing rule to send a small percentage of traffic to the Deployment that references the new version of the application.
- 1. Implement a rolling update pattern by replacing the Pods gradually with the new release version.
  2. Validate the application's performance for the new subset of users during the rollout, and roll back if an issue arises.
ユーザの投票
コメント(6)
- 正解だと思う選択肢: C
  https://cloud.google.com/architecture/implementing-deployment-and-testing-strategies-on-gke#perform_an_ab_test
  
  i would say C: To try this pattern, you perform the following steps:
  
  Deploy the current version of the application (app:current) on the GKE cluster. Deploy a new version of the application (app:new) alongside the current version. Use Istio to route incoming requests that have the username test in the request's cookie to app:new. All other requests are routed to app:current.
  
  👍 5
  Pime132023/02/27
- 正解だと思う選択肢: B
  This approach allows you to deploy new container images without downtime, as the traffic is only being redirected to the new namespace once the Deployment is ready. This also allows you to test and verify the new production release using a subset of production users by routing only a portion of the traffic to the new namespace.
  
  👍 3
  mrvergara2023/02/04
- 正解だと思う選択肢: D
  https://auth0.com/blog/deployment-strategies-in-kubernetes/ Rolling updates are ideal because they allow you to deploy an application slowly with minimal overhead, minimal performance impact, and minimal
  
  👍 1
  TNT872023/01/31
シャッフルモード

ユーザの投票

コメント(6)