Build and operate the data processing systems behind analytics and ML on Google Cloud, including BigQuery, Dataflow, and Pub/Sub, and track your readiness for the Professional Data Engineer exam.
Advanced
Prepare and test your skills
Advanced
Prepare and test your skills
Google Cloud service
Cloud Billing
Topic in 3 exam domains
Also called: billing system, Cloud Billing system, Google Cloud billing
Google Cloud's billing service used to manage accounts and authorize package downloads.
Where this appears on the exam
3 objectives in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedApplication Default CredentialsFeatureIdentity and Access ManagementServiceCloud RunService
Cloud BillingService
Compute EngineServiceBigQueryServiceCloud StorageServiceAlloyDB for PostgreSQLServiceCloud Billing reportsFeatureCommitted use discountsFeatureGKEServiceCloud SQLServiceData Studio ProServiceDataflowServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery works with Cloud Billing From the official documentation: “To export Cloud Billing data to BigQuery, take the following steps:”
- Identity and Access Management secures Cloud Billing From the official documentation: “Cloud Billing uses Identity and Access Management (IAM) for authorization.”
- Cloud Billing works with Compute Engine From the official documentation: “To report usage to Cloud Billing, you can use any of the following services: - A Google Cloud service, such as Compute Engine that measures the life of a virtual machine (VM).”
- Cloud Billing works with GKE From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
- Cloud Billing reports is part of Cloud Billing From the official documentation: “Labels are forwarded to Cloud Billing [cost management](/cost-management) tools, including [cost reports](/billing/docs/how-to/reports) and [billing exports](/billing/docs/how-to/export-data-bigquery).”
- Committed use discounts depends on Cloud Billing From the official documentation: “You can purchase CUDs from any Cloud Billing account, and the discount applies to any eligible usage in projects that the Cloud Billing account pays for.”
- Data Studio Pro depends on Cloud Billing From the official documentation: “A Data Studio Pro subscription must be linked to a Google Cloud project that has an active Cloud Billing account.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Application Default Credentials secures Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Cloud SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “BigQuery AlloyDB federation lets BigQuery query data residing in AlloyDB in real time without copying or moving the data.”
- AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB supports importing and exporting compressed `.gz` files from Cloud Storage.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- AlloyDB for PostgreSQL works with Cloud Run From the official documentation: “The Cloud Run service can connect to the AlloyDB instance.”
- AlloyDB for PostgreSQL is an alternative to Cloud SQL From the official documentation: “The sample code uses Cloud SQL as the vector database, whereas this reference architecture uses AlloyDB for PostgreSQL.”
- Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, set up Application Default Credentials.”
- BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
- Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
- Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
- Data Studio Pro works with Identity and Access Management From the official documentation: “You can use IAM to assign project-level permissions that apply to all Data Studio Pro assets in your organization.”
- Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
- Dataflow depends on Compute Engine From the official documentation: “When you run your pipeline on the Dataflow service, Dataflow creates Compute Engine instances to run your pipeline code.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- AlloyDB for PostgreSQL works with Committed use discounts From the official documentation: “This page describes how committed use discounts (CUDs) work with AlloyDB for PostgreSQL.”
- AlloyDB for PostgreSQL works with Compute Engine From the official documentation: “In this tutorial, you integrate an AlloyDB instance and a [Compute Engine](https://cloud.google.com/compute) VM instance on a [Virtual Private Cloud (VPC)](https://cloud.google.com/vpc) network.”
- AlloyDB for PostgreSQL works with GKE From the official documentation: “Route AlloyDB for PostgreSQL events to GKE”
- AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “This page explains the process of logging into an AlloyDB for PostgreSQL instance using an account prepared with Identity and Access Management (IAM).”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
How learners score on this topic
Last updated