Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise data engineering team processes streaming events using Cloud Dataflow and manages batch pipelines using Cloud Dataproc. To satisfy security audit requirements and analyze system health, the team creates a custom Log Router sink configured to route Dataflow and Dataproc execution and audit logs into a BigQuery dataset residing in a centralized observability project.
After creating the log sink, the team notices that log entries are not appearing in the destination BigQuery dataset.
Which action should the data engineer take to enable the log sink to export logs successfully?
The Logs Configuration Writer (roles/logging.configWriter) role is an administrative role granting permissions to create, update, and delete log sinks, log scopes, exclusion filters, and log metrics within a project.
roles/logging.configWriter allows users or automated tools to configure sinks, but it does not provide data ingestion rights at the destination dataset.bigquery.tables.create or bigquery.tables.updateData permissions.A continuous integration (CI/CD) pipeline service account needed permissions to programmatically provision and update Log Router sinks across data projects.
The Logs Bucket Writer (roles/logging.bucketWriter) role provides permissions (logging.logEntries.route) allowing principals or sinks to route and save log entries specifically into native Cloud Logging buckets (_Default or custom log buckets).
roles/bigquery.dataEditor), not logging bucket permissions.writerIdentity.LogBucket resources inside Cloud Logging storage.You were routing logs to a centralized custom Cloud Logging bucket in another project rather than exporting structured logs to BigQuery for SQL analytics.
When you create a log sink in Cloud Logging that routes log entries to another destination (such as a BigQuery dataset, Cloud Storage bucket, or Pub/Sub topic), Cloud Logging creates or assigns a dedicated service account represented in the writerIdentity field of the sink configuration. This identity acts on behalf of the Log Router to deliver logs to external or cross-project resources.
writerIdentity principal requires permissions to insert records into tables and create underlying log tables, which is provided by the BigQuery Data Editor (roles/bigquery.dataEditor) role.gcloud logging sinks describe SINK_NAME reveals the assigned service account (e.g., serviceAccount:service-123456789012@gcp-sa-logging.iam.gserviceaccount.com), which can then be granted the necessary role via IAM policy bindings on the target dataset or project.Granting the specific destination role (roles/bigquery.dataEditor) directly to the sink's writerIdentity satisfies the exact IAM requirement needed for the Log Router to push data into BigQuery without granting unnecessary project-level owner permissions.
The Cloud Dataflow Service Agent (roles/dataflow.serviceAgent) is an internal Google-managed service account used by Dataflow to manage Compute Engine instances, monitor worker status, and coordinate pipeline steps during job execution.
roles/dataflow.serviceAgent does not authorize the Log Router sink to publish log data into the destination BigQuery dataset.This role binding would be correct if Dataflow workers were executing pipeline transforms designed to write business data directly into BigQuery using the BigQuery I/O connector via the service agent rather than relying on log exports.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated