Answer-first summary for fast verification
Answer: Create a central Cloud Monitoring workspace and attach all related projects.
The requirement is to centralize logs from all projects (across production, test, and development folders) into the production folder for alerting and near-real-time analysis. Option B is correct because creating a central Cloud Monitoring workspace in a project within the production folder and attaching all projects (regardless of their folder) ensures logs are aggregated into that workspace. This enables unified alerting, dashboards, and analysis using Cloud Monitoring's capabilities, while keeping the log data stored in the production folder. Options C and D are incorrect because an aggregated log sink associated only with the production folder cannot capture logs from projects in other folders (e.g., test or development). Option A is irrelevant, as the Workflows API is unrelated to log routing or centralization.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To centralize logs from all projects within your production folder for security review, alerting, and near-real-time analysis, what is the recommended approach in your Google Cloud resource hierarchy?
(Assume the production, test, and development folders are already structured under the organization.)
A
Enable the Workflows API and route all the logs to Cloud Logging.
B
Create a central Cloud Monitoring workspace and attach all related projects.
C
Create an aggregated log sink associated with the production folder that uses a Pub/Sub topic as the destination.
D
Create an aggregated log sink associated with the production folder that uses a Cloud Logging bucket as the destination.