You are managing an application deployed on Cloud Run for Anthos, and you need to define a strategy for deploying new versions of the application. You want to evaluate the new code with a subset of production traffic to decide whether to proceed with the rollout. What should you do?
Deploying a new revision to Cloud Run with the new version allows you to manage the traffic effectively between different versions. This way, you can assign a specific percentage of production traffic to the new version, which facilitates a gradual rollout and evaluation. This approach ensures you can test the new version under real production conditions without requiring additional services or complex configurations, making it the most efficient strategy.
Correct Answer: A o Each deployment to a service creates a revision. A revision consists of a specific container image, along with environment settings such as environment variables, memory limits, or concurrency value. o Once the new revision is deployed to a Service you can manage the traffic using MANAGE TRAFFIC option inside the revision tab https://cloud.google.com/run/docs/resource-model
The correct answer is A. Deploy a new revision to Cloud Run with the new version. Configure traffic percentage between revisions. Cloud Run for Anthos allows you to deploy new revisions of your application with a specific percentage of traffic, which allows you to perform a gradual rollout of the new version. To do this, you can follow these steps: Deploy a new revision of your application to Cloud Run with the new version. In the Cloud Run for Anthos console, navigate to the service that you want to roll out the new version for. In the "Revisions" tab, you should see the new revision listed alongside the current revision. Use the traffic percentage slider to specify the percentage of traffic that you want to send to the new revision. You can set the percentage to a small value initially, such as 5%, and gradually increase it over time as you evaluate the new version. Once you have set the traffic percentage, Cloud Run for Anthos will start directing a portion of the traffic to the new revision, allowing you to evaluate the new version with a subset of production traffic.
Option B, deploying a new service and adding a Cloud Load Balancer instance in front of both services, is not recommended because it would require you to create and manage a separate service for the new version, which would be more complex and less efficient than deploying a new revision. Option C, using continuous deployment with Cloud Build and substitution variables, is not relevant to this scenario because it involves deploying new versions automatically based on changes to a development branch, rather than manually deploying new revisions with a specific percentage of traffic. Option D, using Traffic Director, is also not relevant because Traffic Director is used for managing traffic between different services or clusters, rather than between revisions of the same service.
Extremely convinced by your explanations..Have u given this exam?
Those Answers are surely generated by ChatgGPT
Yes, chatgpt did the exam, LOL
https://cloud.google.com/anthos/run/docs/rollouts-rollbacks-traffic-migration
C is ok as we want to DEFINE A STRATEGY
whats wrong with C is configuring deployment from 'development branch' this is supper ugly
A is correct currently there is possibility to use tags to test in production without receiving real traffic: https://cloud.google.com/anthos/run/docs/rollouts-rollbacks-traffic-migration#tags
A is correct - https://cloud.google.com/anthos/run/docs/rollouts-rollbacks-traffic-migration#gradual
https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#gradual
A. Deploy a new revision to Cloud Run with the new version. Configure traffic percentage between revisions.
you can do a lab on this >>>Deploy Your Website on Cloud Run<<< Manage traffic is there
A is ok
Selected A
Answer is A
You all forget that in the exam they expect you to choose the most complete answer, and C is the most efficient and complete one, where you show knowledge of Cloud Build also, and in the real life that is how you should implement this solution.
C is saying "from development branch"!
https://cloud.google.com/anthos/run/docs/rollouts-rollbacks-traffic-migration
La Opción A - El uso de dashboards predefinidos proporciona una visión inmediata y eficiente del estado del sistema, y la capacidad de agregar métricas personalizadas y crear políticas de alertas permite una respuesta rápida y efectiva a los incidentes. Generar un Dashboard por incidente introduce complejidad innecesaria.
A: https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration#gradual