Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company wants to establish automated daily exports of Google Cloud billing data to BigQuery to enable granular cost tracking, custom reporting, and financial auditing.
You are tasked with setting up the billing export to a dedicated BigQuery dataset in a centralized analytics project.
Which combination of Identity and Access Management (IAM) permissions and destination configurations is required to successfully enable this billing export?
Cloud Billing export to BigQuery is a native Google Cloud feature that enables continuous, automated streaming of detailed financial and resource usage data directly into a BigQuery dataset. This allows finance teams and cloud architects to run SQL-based cost analytics, aggregate spending by resource labels, and build automated visualization dashboards in tools like Looker Studio.
roles/billing.admin): Configuring billing exports at the billing account level requires administrative authority over the billing account itself. The administrator role grants the permissions necessary to link billing streams to external destination projects.roles/bigquery.dataEditor or roles/bigquery.admin): The administrator configuring the export must hold permissions in the target project to create tables, update metadata, and modify datasets (such as bigquery.tables.create and bigquery.tables.updateData).
This setup follows standard Google Cloud security principles by pairing administrative control on the billing entity with appropriate write permissions on a properly secured, dedicated destination repository.
The Billing Account Viewer (roles/billing.viewer) role grants read-only visibility into billing account balances, invoices, and transaction history. The Storage Admin (roles/storage.admin) role provides full administrative control over Cloud Storage buckets and objects, such as creating, listing, and deleting files.
A user needed read-only financial visibility while maintaining storage buckets for unstructured object backups.
The Project Viewer (roles/viewer) role provides read-only access to standard project resources across Google Cloud. The BigQuery Job User (roles/bigquery.jobUser) role grants permission to run queries and execute BigQuery processing jobs within a specific project.
roles/viewer lacks the necessary rights to modify cloud infrastructure or configure billing settings.An auditor required broad read-only visibility across projects to inspect configurations and execute analytical SQL queries in an existing BigQuery environment.
The Billing Account User (roles/billing.user) role allows users to link new or existing projects to a Cloud Billing account. The BigQuery Data Viewer (roles/bigquery.dataViewer) role grants read-only access to datasets, allowing principals to inspect dataset metadata and query existing tables.
roles/bigquery.dataViewer) does not permit creating tables, updating schemas, or writing incoming export streams into BigQuery.allAuthenticatedUsers makes confidential corporate financial data publicly readable by any authenticated Google Cloud identity.roles/billing.user is intended strictly for project association, not billing administration.roles/bigquery.dataViewer lacks essential write permissions such as bigquery.tables.create and bigquery.tables.updateData.This combination would be relevant if a developer only needed to attach a project to a billing account and read data from an existing public demonstration dataset.
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