Deal of The Day! 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 93 Discussion

Posted by Donette on Jul 07, 2025 at 08:39 AM

[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?

Suggested Answer: A

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
28 comments · newest first
TH
Theodora 10 months ago
Definitely need separate sinks for Dev and Prod, so D makes sense.
GL
Glory 10 months ago
I disagree, A seems simpler and covers everything.
TI
Tina 11 months ago
Wait, can we really filter by project ID like that? Sounds too good to be true.
LU
Luke 11 months ago
C is solid, but I wonder if it complicates things later on.
DU
Dudley 11 months ago
I think option C is the best choice. Two sinks for better organization.
JU
Junita 11 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.
GI
Giovanna 11 months ago
I practiced a similar question, and I think option D makes sense because it targets the specific folders directly.
MA
Marylou 12 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.
OR
Ora 12 months ago
I remember we discussed the importance of minimizing log sinks, so I think option A might be the best choice.
AN
Angelica 1 year 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.
TU
Tuyet 1 year 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.
HE
Herschel 1 year 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.
LI
Ling 1 year 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.
JO
Josphine 1 year ago
I don't know, man. All these options sound kind of serious. Where's the fun in logging? *chuckles*
CA
Cary 1 year ago
Ah, the classic 'create a log sink for each project' approach. Option B is so 2020, let's move with the times!
RA
Raylene 1 year ago
Hmm, Option C looks promising. Filtering by project ID could be a neat way to keep things organized.
EU
Eun 1 year ago
↳ replying to Raylene
I think Option C is the way to go.
YO
Youlanda 1 year 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.
DO
Douglass 1 year ago
↳ replying to Youlanda
I agree, having aggregated log sinks in the specific folders seems like the most efficient way to handle the log entries.
CA
Carin 1 year ago
↳ replying to Youlanda
Option D is a good choice. It keeps things organized by having separate log sinks for Dev and Prod folders.
LA
Lakeesha 1 year ago
Option A seems like the way to go. Minimizing the number of log sinks and ensuring future projects are covered? Sign me up!
CL
Clorinda 1 year ago
↳ replying to Lakeesha
C) Create two aggregated log sinks at the organization level, and filter by project ID
VE
Venita 1 year ago
↳ replying to Lakeesha
That's a good idea. It will cover all projects and minimize the number of log sinks.
CA
Catarina 1 year ago
↳ replying to Lakeesha
A) Create a single aggregated log sink at the organization level.
JE
Jettie 1 year ago
I think creating an aggregated log sink in the Dev and Prod folders would be the most practical solution.
MA
Marquetta 1 year ago
I believe creating two aggregated log sinks at the organization level and filtering by project ID is the best option.
CA
Carmelina 1 year ago
I disagree, creating a log sink in each project would be more efficient.
NI
Nidia 1 year ago
I think we should create a single aggregated log sink at the organization level.
0/2000 characters

Save Cancel