
Ultimate access to all questions.
In your role as a cloud infrastructure administrator, you aim to empower your development team to deploy new features to an existing Cloud Run service in production. Your goal is to minimize the risk associated with a new revision by reducing the number of customers affected by a possible outage. Importantly, you wish to achieve this without incurring additional development or operational costs for your customers. To meet these requirements, you want to adhere to Google-recommended practices for managing revisions to a service. What steps should you take?
A
Ask your customers to retry access to your service with exponential backoff to mitigate any potential problems after the new revision is deployed.
B
Gradually roll out the new revision and split customer traffic between the revisions to allow rollback in case a problem occurs.
C
Send all customer traffic to the new revision, and roll back to a previous revision if you witness any problems in production.
D
Deploy your application to a second Cloud Run service, and ask your customers to use the second Cloud Run service.