Free Google Professional Cloud DevOps Actual Exam Questions - Question 8 Discussion
You have an application that runs on Cloud Run. You want to use live production traffic to test a new
version of the application while you let the quality assurance team perform manual testing. You want
to limit the potential impact of any issues while testing the new version, and you must be able to roll
back to a previous version of the application if needed. How should you deploy the new version?
Choose 2 answers
Maybe E and B. E lets you gradually send a small portion of real user traffic to the new version, so you can catch issues early without fully switching over. B is good because deploying with a tag and no traffic means QA can test the new revision manually without affecting users. This combo balances real traffic testing and manual checks while keeping rollback simple. A or C don’t really help with controlled traffic management, and D seems risky since it routes traffic directly to the new version’s URL without proper control.
Not C, because deploying without a tag but no traffic still exposes risk if traffic is accidentally routed. B keeps it isolated, and E lets you control traffic split for safe rollout and quick rollback.
Makes sense to pick B because it keeps the new version isolated for QA. E works well to slowly roll out and limit risk with real traffic. So, B and E fit best here.
It’s B and E—tagged revision for isolated QA, then split traffic to test live safely.
Option B makes sense because deploying a new revision with a tag and no traffic lets QA test manually without affecting users. Then Option E fits since splitting traffic allows live testing with minimal risk and easy rollback if things go wrong. This combo keeps the new version isolated initially and then gradually exposes it to production, which is exactly what the question wants. Also, option A is off since creating a new service complicates rollback and traffic management, so not ideal here.
This is tricky, but I’d pick C and E. Deploying without a tag but no traffic keeps it ready but isolated, and splitting traffic lets you test with limited user exposure while still being able to roll back fast.
Could someone clarify if the QA testing has to happen on live user traffic or just isolated from it? That might affect whether we can split traffic or need no-traffic deploy first. Thinking about B and E here.