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

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

Question #: 95
Topic #: 5

[All Professional Cloud DevOps Engineer Questions]

[Building and implementing service monitoring strategies]

Your organization is running multiple Google Kubernetes Engine (GKE) clusters in a project. You need to design a highly-available solution to collect and query both domain-specific workload metrics and GKE default metrics across all clusters, while minimizing operational overhead. What should you do?

AUse Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Ensure that a Thanos sidecar is enabled on every Prometheus instance. Configure Thanos in the central cluster. Query the central Thanos instance.

BUse Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Configure remote-write to one central Prometheus. Query the central Prometheus instance.

CEnable managed collection on every GKE cluster. Query the metrics in Cloud Monitoring.

DEnable managed collection on every GKE cluster. Query the metrics in BigQuery.

Show Suggested Answer

Suggested Answer: C

by Reena at Aug 02, 2025, 04:08 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Gregoria

3 months ago

Wait, can managed collection really handle all that?

upvoted 0 times

...

Bronwyn

3 months ago

I agree, remote-write simplifies things a lot!

upvoted 0 times

...

Youlanda

3 months ago

I like option C for its simplicity and integration with Cloud Monitoring.

upvoted 0 times

...

Chandra

3 months ago

Option A is overkill, Thanos is not always necessary.

upvoted 0 times

...

Lauryn

3 months ago

I think option B is the best for centralizing metrics.

upvoted 0 times

...

Denise

4 months ago

I feel like using BigQuery for querying metrics could be overkill, but I’m not entirely sure how it compares to the other options.

upvoted 0 times

...

Elbert

4 months ago

I practiced a similar question where we had to choose between Prometheus and Cloud Monitoring, and I think Cloud Monitoring might be less operationally heavy.

upvoted 0 times

...

Valene

4 months ago

I think enabling managed collection sounds simpler, but I can't recall if it provides all the metrics we need.

upvoted 0 times

...

Karl

4 months ago

I remember discussing Prometheus and Thanos in class, but I'm not sure if I should go with the sidecar option or just use remote-write.

upvoted 0 times

...

Willie

5 months ago

I'm leaning towards option A with Prometheus and Thanos. It seems like the most comprehensive solution that would meet all the requirements, even if it might be a bit more complex to set up initially. The high availability and centralized querying capabilities are really important for this use case.

upvoted 0 times

...

Kayleigh

5 months ago

Option C looks tempting - using the managed collection in Cloud Monitoring could be a simpler solution. But I'm not sure if that would give me the same level of control and flexibility as running my own Prometheus setup. I'll have to weigh the trade-offs carefully.

upvoted 0 times

...

Ines

5 months ago

Hmm, I'm a bit unsure about this one. The question is asking for a "highly-available" solution, and I'm not sure if the remote-write approach in option B would be as robust as the Thanos setup in option A. I'll need to think this through carefully.

upvoted 0 times

...

Ling

5 months ago

This looks like a pretty straightforward question on monitoring strategies for GKE clusters. I think I'll go with option A - using Prometheus Operator and Thanos to set up a centralized monitoring solution. Thanos should give me the high availability and querying capabilities I need across all the clusters.

upvoted 0 times

...

Reita

6 months ago

I agree with Daron, using Prometheus Operator with Thanos sidecar seems like a good solution.

upvoted 0 times

...

Shawna

7 months ago

Remote-write to Prometheus? That's like the monitoring equivalent of copy-pasting code from StackOverflow. Gotta love it!

upvoted 0 times

...

Lina

7 months ago

Prometheus and Thanos, huh? Reminds me of the old days when we had to build our own monitoring stack from scratch. Ah, the good old days!

upvoted 0 times

...

Deangelo

7 months ago

BigQuery, eh? Interesting choice, but I'm not sure how well it would handle real-time metric queries.

upvoted 0 times

...

Leigha

7 months ago

Managed collection in Cloud Monitoring? Sounds convenient, but I wonder how much control we'd have.

upvoted 0 times

...

Daron

7 months ago

I think option A is the best choice.

upvoted 0 times

...

Cory

7 months ago

Remote-write to a central Prometheus? Nice and simple, I like it.

upvoted 0 times

...

Martha

7 months ago

Prometheus Operator with Thanos? Sounds like a lot of moving parts, but I guess it's the most flexible solution.

upvoted 0 times

Marti

7 months ago

A) Prometheus Operator with Thanos can be complex, but it offers flexibility.

upvoted 0 times

...

Loren

7 months ago

B) Use Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Configure remote-write to one central Prometheus. Query the central Prometheus instance.

upvoted 0 times

...

Louann

7 months ago

A) Use Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Ensure that a Thanos sidecar is enabled on every Prometheus instance. Configure Thanos in the central cluster. Query the central Thanos instance.

upvoted 0 times

...