ExamTopics Logo
Mail Us[email protected]
Menu
Google Discussions
exam questions

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam
Go to Exam

Exam Professional Cloud Developer topic 1 question 239 discussion

Actual exam question from Google's Professional Cloud Developer
Question #: 239
Topic #: 1
[All Professional Cloud Developer Questions]

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?

  • A. 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.
  • B. 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.
  • C. 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.
  • D. 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.
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️
by TNT87 at Feb. 1, 2023, 8:32 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Pime13
Highly Voted 1 year, 4 months ago
Selected Answer: 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.
upvoted 6 times
...
__rajan__
Most Recent 9 months, 2 weeks ago
Selected Answer: C
C is correct.
upvoted 1 times
...
purushi
11 months ago
Selected Answer: C
C looks good since "send a small percentage of traffic to the Deployment that references the new version of the application" for A/B testing. D is close but not perfect for the said requirements.
upvoted 1 times
...
zanhsieh
1 year, 1 month ago
Selected Answer: C
C. The keywords, "A/B testing", "verified using a subset of production users", mean we need canary deployment. A: No. In-place deployment. B: No. This is Blue/Green deployment, but Ingress config (=manifest) does not have way to specify subset of traffic routing to different namespace. C: Yes. D: No, there's no mechanism on Ingress / Services manifests that can specify a subset of users, plus this is rolling update (=in-place deployment)
upvoted 2 times
...
NewComer200
1 year, 2 months ago
Selected Answer: C
I couldn't find the wrong point in Option C. And it's cool way. I think in option B, some accidents possibly occur in the case the communication occurred between some microservices includeing new container.
upvoted 1 times
...
TNT87
1 year, 5 months ago
Selected Answer: B
Actually according to this link , its B https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app#deploying_a_new_version_of_the_sample_app
upvoted 1 times
...
mrvergara
1 year, 5 months ago
Selected Answer: 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.
upvoted 4 times
mrvergara
1 year, 5 months ago
Option D, which implements a rolling update pattern, can result in some downtime as Pods are gradually replaced with the new release version. While this approach can minimize the impact of any issues with the new release, it does not meet the requirement of "no downtime when new container images are deployed." Option D would be a suitable approach for situations where downtime is acceptable and can be managed, but it does not meet the requirements specified in this scenario.
upvoted 2 times
...
...
TNT87
1 year, 5 months ago
Selected Answer: 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
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
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.

SaveCancel