A security compliance team needs to aggregate and retain all admin activity audit logs from every Google Cloud project residing within a specific organizational Folder. The logs must be streamed into a central BigQuery dataset located in a dedicated security project for long-term analysis. You need to configure this aggregated log export while adhering to the principle of least privilege. Which TWO actions should you perform? (Select 2 answers.)
- Create an aggregated Log Router sink at the Folder level with the destination configured to point to the central BigQuery dataset.Answer
- Grant the BigQuery Data Editor role to the sink's writer identity service account on the destination BigQuery dataset.Answer
- CEnable the Cloud Logging API at the Folder container level using gcloud commands before creating the sink.
- DGrant the primitive Owner role to the sink writer identity across the entire destination security project.
Answer
The correct actions are to create an aggregated Log Router sink at the Folder level pointing to the destination BigQuery dataset, and to grant the BigQuery Data Editor role to the sink's writer identity service account specifically on the target dataset.
Aggregated Cloud Logging sinks created at a folder level automatically collect log entries from all child projects within that folder. Furthermore, granting the predefined role of BigQuery Data Editor to the sink's writer identity on the target BigQuery dataset enforces least privilege while providing the necessary write permissions for ingestion.
Step-by-Step Solution
Key Concept
Aggregated Log Router Sinks and Cross-Project IAM Permissions