Google Professional Cloud Database Engineer Exam - Topic 12 Question 22 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam

Question #: 22
Topic #: 12

[All Professional Cloud Database Engineer Questions]

You recently launched a new product to the US market. You currently have two Bigtable clusters in one US region to serve all the traffic. Your marketing team is planning an immediate expansion to APAC. You need to roll out the regional expansion while implementing high availability according to Google-recommended practices. What should you do?

AMaintain a target of 23% CPU utilization by locating:
cluster-a in zone us-central1-a
cluster-b in zone europe-west1-d
cluster-c in zone asia-east1-b

BMaintain a target of 23% CPU utilization by locating:
cluster-a in zone us-central1-a
cluster-b in zone us-central1-b
cluster-c in zone us-east1-a

CMaintain a target of 35% CPU utilization by locating:
cluster-a in zone us-central1-a
cluster-b in zone australia-southeast1-a
cluster-c in zone europe-west1-d
cluster-d in zone asia-east1-b

DMaintain a target of 35% CPU utilization by locating:
cluster-a in zone us-central1-a
cluster-b in zone us-central2-a
cluster-c in zone asia-northeast1-b
cluster-d in zone asia-east1-b

Show Suggested Answer

Suggested Answer: D

https://docs.google.com/forms/d/e/1FAIpQLSfZ77ZnuUL0NpU-bOtO5QUkC0cnRCe5YKMiubLXwfV3abBqkg/viewform

by Francine at Nov 23, 2023, 09:03 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Samira

4 months ago

Why are we using Europe zones for APAC expansion?

upvoted 0 times

...

Cyril

5 months ago

I disagree, option B is better for US traffic.

upvoted 0 times

...

Dana

5 months ago

35% CPU utilization? Seems a bit high, right?

upvoted 0 times

...

Delmy

5 months ago

I think option D makes the most sense for APAC.

upvoted 0 times

...

Lettie

5 months ago

Cluster locations matter a lot for latency!

upvoted 0 times

...

Tuyet

6 months ago

I recall that maintaining a target CPU utilization is crucial, but I can't remember if 23% is too low. I think we should aim for a balance between performance and cost.

upvoted 0 times

...

Kristin

6 months ago

I’m a bit confused about the zones. Shouldn't we prioritize clusters in the same region for lower latency? I’m not sure if spreading them out is the best approach.

upvoted 0 times

...

Veronika

6 months ago

I think we practiced a question similar to this where we had to choose clusters in different regions. I feel like option C might be the right choice since it covers more regions.

upvoted 0 times

...

Simona

6 months ago

I remember we discussed the importance of regional distribution for high availability, but I'm not sure if 23% or 35% CPU utilization is better for this scenario.

upvoted 0 times

...

Dean

6 months ago

I feel pretty confident about this one. The Google-recommended practices for high availability suggest using multiple clusters across different zones and regions. Based on the information provided, option D looks like the most comprehensive solution to meet the requirements.

upvoted 0 times

...

Venita

6 months ago

This is a tricky one. I'm not sure if I fully understand the implications of the different CPU utilization targets. I'll need to think through the trade-offs between redundancy, performance, and cost before deciding on the best approach.

upvoted 0 times

...

Francisca

6 months ago

Okay, I think I've got this. The key is to distribute the clusters across multiple zones and regions to ensure high availability. Based on the options, B and D seem like the best choices since they cover both the US and APAC regions.

upvoted 0 times

...

Carmen

6 months ago

Hmm, I'm a bit confused about the CPU utilization targets. Do we need to strictly maintain 23% or 35% in each cluster, or is that just a general guideline? I'll need to re-read the question carefully to make sure I understand the requirements.

upvoted 0 times

...

Barrett

6 months ago

This question seems straightforward - we need to set up a highly available Bigtable solution across multiple regions to support the expansion to APAC. The key is to maintain the target CPU utilization while ensuring redundancy.

upvoted 0 times

...

Jamal

6 months ago

Hmm, this question seems a bit tricky. Let me think through the 5G NSA Option 3x architecture and the different downlink data split modes that can be supported on the gNodeB side.

upvoted 0 times

...

Vicky

6 months ago

I think applying the Redundant Implementation pattern might help but seem to recall that it could complicate the architecture further.

upvoted 0 times

...

Keneth

6 months ago

I'm a little confused by the wording here. I'll need to re-read the question and options a few times to make sure I understand what they're asking.

upvoted 0 times

...

Keneth

6 months ago

Hmm, I'm a bit unsure about this one. I'm not super familiar with OpenTelemetry, so I'm not sure if that's the best option. Maybe I should look into the other choices a bit more before deciding.

upvoted 0 times

...

Barney

6 months ago

This one seems pretty straightforward. I think the answer is B - Ongoing surveys, since the question specifically mentions measuring the quality of a single call or incident.

upvoted 0 times

...

Ozell

11 months ago

Ah, the classic 'high availability' question. Gotta love it. I think option B is the safest bet, but if I'm feeling adventurous, maybe I'll go with C and see what happens.

upvoted 0 times

Dylan

10 months ago

Yeah, option B seems like the best option for maintaining high availability.

upvoted 0 times

...

Timothy

10 months ago

I would go with option B for a safer approach.

upvoted 0 times

...

Mabel

10 months ago

I think option C could be interesting to try out, but it might be riskier.

upvoted 0 times

...

Teddy

10 months ago

I agree, option B seems like the most reliable choice.

upvoted 0 times

...

Raymon

12 months ago

Haha, 'Bigtable clusters' - sounds like a supersized version of our regular database! I'm leaning towards option D, just to keep things interesting.

upvoted 0 times

Helene

10 months ago

Let's go with option D then, it seems like the best fit for our expansion to APAC.

upvoted 0 times

...

Bronwyn

10 months ago

Yeah, maintaining a target of 35% CPU utilization with those cluster locations makes sense.

upvoted 0 times

...

Nadine

11 months ago

I agree, option D seems like a solid plan for the regional expansion.

upvoted 0 times

...

Giuseppe

11 months ago

Option D does sound interesting! I think it's a good choice.

upvoted 0 times

...

Louvenia

12 months ago

Wait, we need to maintain a target of 23% CPU utilization? That's a pretty low bar. I'd go with option C and spread the clusters across multiple regions to improve availability.

upvoted 0 times

...

Alberta

12 months ago

I'm not sure, option C also looks promising with the 35% CPU utilization target.

upvoted 0 times

...

Norah

1 year ago

Hmm, this looks like a tricky one. I'm thinking option B might be the way to go, keeping the clusters in the same US region for now and then adding a third cluster in APAC later.

upvoted 0 times