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_dataset. You 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?
Select an option, then click Submit answer.
Reference / correct answer:
Create an aggregated log sink in the Dev and Prod folders.
Most accepted answer: D. Create an aggregated log sink in the Dev and Prod folders.
Community votes: D=2
I vote for D upvoted 6 times
Selected Answer: D To minimize the number of log sinks and ensure that the log sink configurations are applied to future projects, the optimal choice is Option D. By creating an aggregated log sink at the folder level for both the Dev and Prod folders, you can enforce consistent export configurations for all existing and forthcoming projects within each folder. This approach facilitates centralized management, eliminating the need for creating individual sinks for each project. It reduces complexity and ensures that any new projects added to the Dev or Prod folders will automatically adopt the log sink configuration, streamlining the process and fostering uniformity throughout the organization. upvoted 2 times
Selected Answer: D need to create two sinks at folder level. if there is new projects inside each folder, the rule will be applied to them too upvoted 1 times
D for sure. upvoted 3 times
C. Create two aggregated log sinks at the organization level, and filter by project ID. By creating two aggregated log sinks at the organization level and applying filters based on project ID, you can achieve the desired log entry routing for both development and production projects. This approach allows for scalability and ensures that future projects in the respective folders will inherit the log sink configurations. upvoted 2 times elskander 1 year, 8 months ago but doesn't apply for future projects hence D is a better option upvoted 3 times ... syslog 1 year, 10 months ago I vote for D. If you use project ID, you can't scale. Your explanation also suggests D, because if you configure the sink at folder level, all projects into folder (present and future) inherit the sink. upvoted 2 times ...