Answer-first summary for fast verification
Answer: Create an aggregate org sink at the parent folder of the production projects, and set the destination to a logs bucket.
The question requires centralizing logs from production projects while maintaining the ability to search and analyze them using Logs Explorer. Option D is correct because creating an aggregate org sink at the parent folder level routes logs to a centralized logs bucket, which preserves compatibility with Logs Explorer. This approach allows teams to access and query logs directly within Cloud Logging. Option C is incorrect because routing logs to a Cloud Storage bucket makes them inaccessible to Logs Explorer, as Cloud Storage requires manual export/import for analysis. Option A (Cloud Monitoring) focuses on metrics and resource monitoring, not log centralization and analysis. Option B (organization-level Logs Explorer filtering) does not centralize logs but relies on distributed access, which may not meet the centralization requirement. The community discussion strongly supports D (88% consensus), with key insights highlighting that logs buckets maintain Logs Explorer functionality, unlike Cloud Storage destinations.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You need to centralize your team's logs for production projects and enable log searching and analysis using Logs Explorer. What should you do?
A
Enable Cloud Monitoring workspace, and add the production projects to be monitored.
B
Use Logs Explorer at the organization level and filter for production project logs.
C
Create an aggregate org sink at the parent folder of the production projects, and set the destination to a Cloud Storage bucket.
D
Create an aggregate org sink at the parent folder of the production projects, and set the destination to a logs bucket.
No comments yet.