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 is configuring a centralized Data Studio (Looker Studio) reporting dashboard connected to BigQuery. The dashboard will be shared with both internal business analysts who have report edit permissions and external stakeholders who have view-only access.
The solution must satisfy the following governance and operational requirements:
Which configuration should the data engineering team implement?
An embedded data source is created directly within the report editor rather than as a standalone asset. When configured with Owner's Credentials, the data source executes queries against BigQuery using the personal Google Cloud identity and IAM permissions of the user who originally authorized the data connection.
This approach would only be suitable for rapid, isolated prototyping by a single author where report editors are trusted with full administrative control over queries and external access is strictly prohibited.
While using Service Account Credentials solves the issue of author departure and avoids individual viewer IAM assignments, pairing them with embedded data sources and default sharing options compromises governance and security.
This pattern would be appropriate if report editors required full flexibility to alter underlying schemas and queries, and where viewer export and sharing restrictions were not mandated.
In Data Studio (Looker Studio), managing enterprise reporting at scale requires separating report layout editing from underlying data connection management, ensuring credential persistence, and restricting data dissemination. Creating a reusable data source that authenticates using a dedicated Google Cloud Service Account satisfies these requirements seamlessly.
Owner's Credentials). If the report creator departs the organization, scheduled refreshes and report queries continue uninterrupted.roles/bigquery.dataViewer and roles/bigquery.jobUser), eliminating the need to grant individual GCP IAM access to external viewers.This architecture establishes strict enterprise governance: reusable data sources lock down connection definitions, service accounts eliminate personal credential fragility, and advanced sharing settings prevent unauthorized data dissemination.
Viewer's Credentials require every individual accessing the Data Studio dashboard to authenticate directly against the underlying storage system (BigQuery) using their own personal Google identity and IAM privileges.
BigQuery Data Viewer role and BigQuery Job User permissions to every external stakeholder identity in Google Cloud IAM, directly violating the requirement to avoid granting direct IAM dataset permissions.This option would be ideal in strict multi-tenant internal environments where individual row-level security or table-level IAM policies in BigQuery must be enforced at query runtime for every specific internal user.
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