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.
Your enterprise stores sensitive sales and customer data in BigQuery. The dataset implements row-level security (RLS) to restrict sales data access based on each manager's region (SESSION_USER()), along with column-level security policy tags to mask personally identifiable information (PII).
You need to configure access for business intelligence (BI) visualization dashboards in Looker Studio so that multiple regional sales managers can view their respective metrics securely while strictly adhering to the principle of least privilege.
Which configuration should you implement?
This approach uses a single user-managed service account with the administrative role roles/bigquery.admin to authenticate the data source connection, executing all queries on behalf of the service account rather than the logged-in viewer.
SESSION_USER() as the service account rather than the individual sales manager. All viewers see identical data matching the service account's permissions.You needed to publish a public or organization-wide executive summary dashboard where all viewers are intended to see the exact same aggregated dataset without individual identity tracking.
The Project Viewer (roles/viewer) role is a legacy primitive/basic IAM role that provides broad read-only access to almost all Google Cloud services and resources residing within a project.
roles/viewer at the project level exposes metadata and configurations for all other project resources (e.g., Cloud Storage buckets, Compute Engine VMs, Cloud SQL instances) rather than restricting access to the specific BigQuery dataset.A user were an overall infrastructure auditor requiring read-only visibility into the inventory and configuration of all services across an entire Google Cloud project.
Viewer's Credentials (OAuth) require individual dashboard viewers to authenticate against Google Cloud BigQuery using their own identity rather than a shared service account. Combining this credential model with predefined IAM roles at specific resource hierarchy levels enforces least-privilege access and activates fine-grained security policies.
SESSION_USER(). This ensures that regional sales managers see only the rows authorized by the row-level security (RLS) policy.roles/bigquery.jobUser on the project provides only the ability to run query jobs without exposing data, while roles/bigquery.dataViewer is restricted specifically to the target dataset rather than the entire project or organization.bigquery.jobs.create) from dataset-level storage read permissions (bigquery.tables.getData).Using Owner's Credentials or a single service account bypasses user-specific row-level security and column-level policy tags because BigQuery sees only the service identity. Delegating the query context via Viewer's (OAuth) credentials with narrow dataset-scoped roles guarantees that security controls and least privilege are enforced natively at query execution time.
This configuration involves creating a downloadable private JSON service account key, embedding it into the external connection settings of the BI tool, and granting project-level job execution roles to end users.
roles/bigquery.user role at the project level gives them unnecessary permissions to create their own jobs and datasets directly in the project.An external automated batch service residing outside Google Cloud required non-interactive machine-to-machine data ingestion where OAuth federated access was unavailable.
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