PROFESSIONAL-SECURITY-OPERATIONS-ENGINEER · Question #72
You scheduled a Google Security Operations (SecOps) report to export results to a BigQuery dataset in your Google Cloud project. The report executes successfully in Google SecOps, but no data…
The correct answer is D. Grant the Google SecOps service account the roles/bigquery.dataEditor IAM role on the dataset. The export from Google SecOps to BigQuery requires that the SecOps service account has permission to write to the dataset. Granting the service account the roles/bigquery.dataEditor IAM role on the target dataset provides the necessary access to insert data, resolving the export
Question
You scheduled a Google Security Operations (SecOps) report to export results to a BigQuery dataset in your Google Cloud project. The report executes successfully in Google SecOps, but no data appears in the dataset. You confirmed that the dataset exists. How should you address this export failure?
Options
- AGrant the Google SecOps service account the roles/iam.serviceAccountUser IAM role to itself.
- BSet a retention period for the BigQuery export.
- CGrant the user account that scheduled the report the roles/bigquery.dataEditor IAM role on the
- DGrant the Google SecOps service account the roles/bigquery.dataEditor IAM role on the dataset.
How the community answered
(48 responses)- A13% (6)
- B4% (2)
- C6% (3)
- D77% (37)
Explanation
The export from Google SecOps to BigQuery requires that the SecOps service account has permission to write to the dataset. Granting the service account the roles/bigquery.dataEditor IAM role on the target dataset provides the necessary access to insert data, resolving the export
Topics
Community Discussion
No community discussion yet for this question.