You support a website with a global audience. The website has a frontend web service and a backend database service that runs on different clusters. All clusters are scaled to handle at least 1/3 of the total user traffic. You use 4 different regions in Google Cloud Platform and Cloud Load Balancing to direct traffic to a region closer to the user. You are applying a critical security patch to the backend database. You successfully patch the database in the first two regions, but you make a configuration error while patching the third region. The unsuccessful patching causes 50% of user requests to the third region to time out. You want to mitigate the impact of unsuccessful patching on users. What should you do?
A. Add more capacity to the frontend of third Region.
B. Revert the third Region backend database and run it without the patch.
C. Drain the requests to the third Region and redirect new requests to other regions.
D. Back up the database in the backend of third Region and restart the database.
Disclaimer
This is a practice question. There is no guarantee of coming this question in the certification exam.
Answer
C
Explanation
Key points are underlined.
You support a website with a global audience. The website has a frontend web service and a backend database service that runs on different clusters. All clusters are scaled to handle at least 1/3 of the total user traffic. You use 4 different regions in Google Cloud Platform and Cloud Load Balancing to direct traffic to a region closer to the user. You are applying a critical security patch to the backend database. You successfully patch the database in the first two regions, but you make a configuration error while patching the third region. The unsuccessful patching causes 50% of user requests to the third region to time out. You want to mitigate the impact of unsuccessful patching on users. What should you do?
A. Add more capacity to the frontend of third Region. (It will increase traffic on the third Region, with broken backend.)
B. Revert the third Region backend database and run it without the patch. (Since this is a critical security patch, not patching the backend database will make the backend database vulnerable. And revert will cause restart/reset, negative impact to users.)
C. Drain the requests to the third Region and redirect new requests to other regions.
D. Back up the database in the backend of third Region and restart the database. (Backing up database will only save data, nothing to do with mitigating the impact.)