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
Concept
labels
Topic in 1 exam domain
- labels · Concept
- Labels · Feature
- labels · Feature
- LABELS · Feature · GQL function
- Labels · Concept
- --labels · Feature · Developer Device Platform session flag
Also called: BigQuery label, BigQuery labels, billing labels, Cloud Translation labels, custom labels, extracted labels, KEY=VALUE pairs, Kubernetes resource labels, label field, labels of a parameter template, labels UDM fields, user-defined labels, VM labels, Workflow labels
Key-value pairs assigned to Google Cloud resources to organize resources and track customer usage.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksThis topicWorks alongsideBuilds on theseAppliedUDMConceptCloud SQLServiceApplication Default CredentialsFeatureIdentity and Access ManagementServiceCloud LoggingServiceCloud MonitoringServiceCloud StorageServiceCloud RunServiceCloud TranslationServiceBigQueryService
labelsConcept
tagsFeatureCloud BillingServicereservationConceptCompute EngineServicecustom dashboardsConceptGoogle Kubernetes Engine (GKE)ServiceGKEServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- labels is an alternative to tags From the official documentation: “Google Cloud *tags* and *labels* are two ways to organize your Filestore resources.”
- Cloud Billing works with labels From the official documentation: “Labels allow you to filter the results of resource lists and Cloud Billing reports.”
- labels is part of BigQuery From the official documentation: “BigQuery supports adding labels to resources.”
- labels configures reservation From the official documentation: “When you add a label to a reservation, it is included in your billing data.”
- BigQuery works with labels From the official documentation: “Labels are exported to BigQuery with the corresponding Google Cloud resources and their usage.”
- Cloud Logging works with labels From the official documentation: “[Labels](/resource-manager/docs/creating-managing-labels) can track your resource spend in Cloud Billing, and provide extra insights in Cloud Logging.”
- labels is part of Cloud SQL From the official documentation: “Modifying labels has no impact on Cloud SQL instance performance.”
- labels is part of Cloud Translation From the official documentation: “The Cloud Translation API supports adding user-defined labels (key-value pairs) to `TranslateText`, `BatchTranslateText` and `DetectLanguage` requests.”
- labels configures Compute Engine From the official documentation: “Labels that are applied to the workstation and propagated to the underlying Compute Engine resources.”
- labels configures custom dashboards From the official documentation: “You can add labels only to custom dashboards, which include dashboards that you import.”
- labels configures Google Kubernetes Engine (GKE) From the official documentation: “To register agents deployed on [Google Kubernetes Engine (GKE)](/kubernetes-engine/docs/tutorials/agentic-adk-vertex), add the required Kubernetes [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) and…”
- labels is part of UDM From the official documentation: “The following `labels` fields for UDM nouns are deprecated: `about.labels`, `intermediary.labels`, `observer.labels`, `principal.labels`, `src.labels`, `security_result.about.labels`, and `target.labels`.”
- 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: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
- Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- BigQuery works with Cloud Billing From the official documentation: “The Cloud Billing data exported to BigQuery is the same data that your Cloud Billing reports use.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
- Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
- Cloud Translation depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Translation, set up Application Default Credentials.”
- Identity and Access Management works with tags From the official documentation: “You can use tags and IAM conditions to conditionally grant role bindings to users in your hierarchy.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
- Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
- Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
- Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
- Application Default Credentials secures Cloud Translation From the official documentation: “To authenticate to Cloud Translation, 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.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
How learners score on this topic
Last updated