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

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

Question #: 93
Topic #: 5

[All Professional Cloud DevOps Engineer Questions]

[Building and implementing service monitoring strategies]

You are creating Cloud Logging sinks to export log entries from Cloud Logging to BigQuery for future analysis Your organization has a Google Cloud folder named Dev that contains development projects and a folder named Prod that contains production projects Log entries for development projects must be exported to dev_dataset. and log entries for production projects must be exported to prod_datasetYou need to minimize the number of log sinks created and you want to ensure that the log sinks apply to future projects What should you do?

ACreate a single aggregated log sink at the organization level.

BCreate a log sink in each project

CCreate two aggregated log sinks at the organization level, and filter by project ID

DCreate an aggregated Iog sink in the Dev and Prod folders

Show Suggested Answer

Suggested Answer: A

by Donette at Jul 07, 2025, 08:39 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

Theodora

5 months ago

Definitely need separate sinks for Dev and Prod, so D makes sense.

upvoted 0 times

...

Glory

5 months ago

I disagree, A seems simpler and covers everything.

upvoted 0 times

...

Tina

6 months ago

Wait, can we really filter by project ID like that? Sounds too good to be true.

upvoted 0 times

...

Luke

6 months ago

C is solid, but I wonder if it complicates things later on.

upvoted 0 times

...

Dudley

6 months ago

I think option C is the best choice. Two sinks for better organization.

upvoted 0 times

...

Junita

6 months ago

I’m a bit confused about the differences between A and C. I thought both could potentially minimize the number of sinks, but I can't recall the details.

upvoted 0 times

...

Giovanna

7 months ago

I practiced a similar question, and I think option D makes sense because it targets the specific folders directly.

upvoted 0 times

...

Marylou

7 months ago

I'm not entirely sure, but I feel like creating two aggregated log sinks in option C could also work since it filters by project ID.

upvoted 0 times

...

Ora

7 months ago

I remember we discussed the importance of minimizing log sinks, so I think option A might be the best choice.

upvoted 0 times

...

Angelica

7 months ago

I'm leaning towards option D - creating an aggregated sink in the Dev and Prod folders. That way the sinks will automatically apply to any new projects added to those folders. Seems like the most scalable and maintainable approach.

upvoted 0 times

...

Tuyet

7 months ago

Okay, I've got a strategy. I'll create two aggregated sinks at the organization level and use filters to route the logs to the appropriate datasets. That way I only have to manage two sinks but can still segregate the data.

upvoted 0 times

...

Herschel

8 months ago

Hmm, I'm a bit unsure about this one. I'm trying to weigh the tradeoffs between creating a single aggregated sink versus multiple sinks. Need to think through the requirements carefully.

upvoted 0 times

...

Ling

8 months ago

This looks like a classic cloud logging and data export question. I think the key is to minimize the number of log sinks while ensuring the logs are properly segregated by environment.

upvoted 0 times

...

Josphine

9 months ago

I don't know, man. All these options sound kind of serious. Where's the fun in logging? *chuckles*

upvoted 0 times

...

Cary

9 months ago

Ah, the classic 'create a log sink for each project' approach. Option B is so 2020, let's move with the times!

upvoted 0 times

...

Raylene

10 months ago

Hmm, Option C looks promising. Filtering by project ID could be a neat way to keep things organized.

upvoted 0 times

Eun

8 months ago

I think Option C is the way to go.

upvoted 0 times

...

Youlanda

10 months ago

I think Option D is the best choice. Creating aggregated log sinks in the Dev and Prod folders makes the most sense to me.

upvoted 0 times

Douglass

8 months ago

I agree, having aggregated log sinks in the specific folders seems like the most efficient way to handle the log entries.

upvoted 0 times

...

Carin

8 months ago

Option D is a good choice. It keeps things organized by having separate log sinks for Dev and Prod folders.

upvoted 0 times

...

Lakeesha

10 months ago

Option A seems like the way to go. Minimizing the number of log sinks and ensuring future projects are covered? Sign me up!

upvoted 0 times

Clorinda

9 months ago

C) Create two aggregated log sinks at the organization level, and filter by project ID

upvoted 0 times

...

Venita

9 months ago

That's a good idea. It will cover all projects and minimize the number of log sinks.

upvoted 0 times

...

Catarina

10 months ago

A) Create a single aggregated log sink at the organization level.

upvoted 0 times

...

Jettie

10 months ago

I think creating an aggregated log sink in the Dev and Prod folders would be the most practical solution.

upvoted 0 times

...

Marquetta

10 months ago

I believe creating two aggregated log sinks at the organization level and filtering by project ID is the best option.

upvoted 0 times

...

Carmelina

11 months ago

I disagree, creating a log sink in each project would be more efficient.

upvoted 0 times

...

Nidia

11 months ago

I think we should create a single aggregated log sink at the organization level.

upvoted 0 times

...