New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud DevOps Engineer Exam - Topic 5 Question 46 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 46
Topic #: 5
[All Professional Cloud DevOps Engineer Questions]

Your product is currently deployed in three Google Cloud Platform (GCP) zones with your users divided between the zones. You can fail over from one zone to another, but it causes a 10-minute service disruption for the affected users. You typically experience a database failure once per quarter and can detect it within five minutes. You are cataloging the reliability risks of a new real-time chat feature for your product. You catalog the following information for each risk:

* Mean Time to Detect (MUD} in minutes

* Mean Time to Repair (MTTR) in minutes

* Mean Time Between Failure (MTBF) in days

* User Impact Percentage

The chat feature requires a new database system that takes twice as long to successfully fail over between zones. You want to account for the risk of the new database failing in one zone. What would be the values for the risk of database failover with the new system?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Verda
4 months ago
Wait, are we sure about the MTTR? That seems off.
upvoted 0 times
...
Shenika
4 months ago
I agree, 33% impact feels more realistic.
upvoted 0 times
...
Telma
4 months ago
50% impact seems high for a chat feature.
upvoted 0 times
...
Lettie
4 months ago
I think MTTR should be 20 minutes with the new system.
upvoted 0 times
...
Judy
5 months ago
MTTD is 5 minutes, that’s solid.
upvoted 0 times
...
Pearline
5 months ago
I’m a bit confused about the MTBF here. It seems like it should stay the same at 90 days, but I’m not entirely sure how the new system affects that.
upvoted 0 times
...
Rasheeda
5 months ago
I practiced a similar question, and I feel like the MTTR should definitely be 20 minutes since the new database takes longer to fail over.
upvoted 0 times
...
Chau
5 months ago
I think the impact percentage might be higher because of the longer failover time, maybe 50%? That seems reasonable given the new system.
upvoted 0 times
...
Cordell
5 months ago
I remember we discussed MTTD and MTTR in class, but I'm not sure if the MTTR should be 10 or 20 minutes with the new database.
upvoted 0 times
...
Abel
5 months ago
I'm a bit unsure about the resource request units. Do I need to specify the units explicitly, or will Kubernetes understand the values?
upvoted 0 times
...
Wenona
5 months ago
Hmm, this looks like a tricky one. I'll need to think through the options carefully.
upvoted 0 times
...
Starr
5 months ago
I'm feeling pretty confident about change management being the correct answer here. It's a well-established management discipline that focuses on the people side of organizational transitions.
upvoted 0 times
...

Save Cancel