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 feature
tags
Topic in 1 exam domain
- tags · Feature
- Tags · Feature
- tags · Concept
- Tags · Concept
Also called: alert-level tags, Build tags, case and alert tags, case tags, firewall tags, Google Cloud tags, IAM governed Tags, IAM Tags, IAM-governed tags, secure tags, standard Resource Manager tags, tags with IAM controls
Resource Manager metadata that provides fine-grained control over policies by conditionally allowing or denying them based on resource tags.
Where this appears on the exam
1 subdomain in 1 of 5 domains
~22% of exam
Related topics
FoundationsBuilding blocksThis topicWorks alongsideBuilds on theseBuilds on theseAppliedLookMLFeatureKnowledge CatalogServiceCloud LoggingServiceVPC Service ControlsServiceData CatalogServiceBigQueryService
tagsFeature
labelsConceptIdentity and Access ManagementServiceAlloyDB for PostgreSQLServicecustom constraintsFeatureDatastreamServiceOrganization policiesFeatureCloud Next Generation FirewallServicealerting policyConceptCloud SQLServiceCloud MonitoringServiceDataproc MetastoreServiceDatabase Migration ServiceServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- 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.”
- labels is an alternative to tags From the official documentation: “Google Cloud *tags* and *labels* are two ways to organize your Filestore resources.”
- Dataproc Metastore works with tags From the official documentation: “This page describes how to attach, detach, and list tags on Dataproc Metastore resources.”
- tags secures alerting policy From the official documentation: “To learn how to control access to your alerting policies with Tags, see [Use Tags to control access to resources](/monitoring/docs/access-control-with-tags).”
- AlloyDB for PostgreSQL works with tags From the official documentation: “Provide Google Cloud integrations for [Identity and Access Management (IAM)](/alloydb/docs/manage-iam-authn), [tags](/alloydb/docs/manage-tags), [Cloud Key Management Service](/alloydb/docs/cmek), and [Network Intelligence Center](/network-intelligence-center/docs).”
- Cloud Monitoring works with tags From the official documentation: “[Tags](/resource-manager/docs/tags/tags-overview) lets you restrict who can edit or delete specific Cloud Monitoring dashboards and alerting policies.”
- Cloud SQL works with tags From the official documentation: “This page describes Google Cloud tags and how to use them with Cloud SQL.”
- custom constraints works with tags From the official documentation: “Tags on organization, folder, or project resources are supported by custom constraints.”
- Organization policies works with tags From the official documentation: “This combines the tags with organization policies, custom organization policies, and IAM conditions to give more customization to instance creation policies.”
- tags configures Cloud Next Generation Firewall From the official documentation: “Create resource tags to govern Cloud Next Generation Firewall rules”
- tags is part of Data Catalog From the official documentation: “`tags` - `(BETA)` `(DEPRECATED)` Manage tags in Data Catalog.”
- tags is part of LookML From the official documentation: “For both custom actions and actions that are available from the Looker Action Hub, you must identify the relevant data fields by using the [`tags`](/looker/docs/reference/param-field-tags) parameter in your LookML model.”
- tags configures Organization policies From the official documentation: “Once you attach a tag to a Cloud Storage bucket, you can [use the tag](/iam/docs/conditions-attribute-reference#resource-tags) with [IAM Conditions](/storage/docs/access-control/using-iam-permissions#conditions-iam) to grant access to resources or with [organization…”
- AlloyDB for PostgreSQL works with Database Migration Service From the official documentation: “Migrating from Cloud SQL to AlloyDB for PostgreSQL using Database Migration Service”
- Cloud SQL works with Database Migration Service From the official documentation: “Migrating from Cloud SQL to AlloyDB for PostgreSQL using Database Migration Service”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Datastream From the official documentation: “Datastream supports three types of partitioning for BigQuery tables:”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- alerting policy is part of Cloud Monitoring From the official documentation: “The Google Cloud console lets you view, list, edit, copy, and delete your alerting policies in Cloud Monitoring.”
- 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 SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
- Data Catalog is an alternative to Knowledge Catalog From the official documentation: “**Caution:** Data Catalog is [deprecated](/data-catalog/docs/deprecations) in favor of [Knowledge Catalog](/dataplex/docs/introduction).”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “Datastream lets you stream from AlloyDB for PostgreSQL to BigQuery using the Free Tier, providing up to 100 GiB of change data capture data free every month.”
- 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.”
- AlloyDB for PostgreSQL works with Datastream From the official documentation: “- Learn how to configure an [AlloyDB for PostgreSQL](/datastream/docs/configure-alloydb-psql) database to work with Datastream.”
- AlloyDB for PostgreSQL works with Knowledge Catalog From the official documentation: “Enable the Knowledge Catalog integration for your AlloyDB cluster”
- 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 works with Database Migration Service From the official documentation: “Database Migration Service uses Cloud Logging.”
- Cloud Logging works with Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
- 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 Monitoring works with Database Migration Service From the official documentation: “To view more details about the error, navigate to Cloud Monitoring using the link on the migration job. The logs are filtered to the specific migration job.”
- Cloud SQL works with Datastream From the official documentation: “The change data capture pipeline uses VPC peering to establish a connection between Datastream and private IP Cloud SQL.”
- Data Catalog is part of Knowledge Catalog From the official documentation: “Knowledge Catalog features”
- Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
- Dataproc Metastore depends on Cloud SQL From the official documentation: “When you run a *start migration*, Dataproc Metastore connects to Cloud SQL and uses Cloud SQL as its backend database.”
- Dataproc Metastore works with VPC Service Controls From the official documentation: “For more information, see [VPC Service Controls with Dataproc Metastore](/dataproc-metastore/docs/vpc-sc).”
- Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
- labels is part of BigQuery From the official documentation: “BigQuery supports adding labels to resources.”
- Organization policies configures Cloud SQL From the official documentation: “This page describes how to add organization policies on Cloud SQL instances, to put restrictions on Cloud SQL at the project, folder, or organization level.”
- alerting policy works with Cloud Logging From the official documentation: “The alerting policy can monitor time-series data stored by Monitoring or logs stored by Cloud Logging.”
- alerting policy configures Cloud Monitoring From the official documentation: “Alerting policies are a way to configure Monitoring to notify you when something, like reaching 85% of your limit on a quota, happens.”
- alerting policy works with Datastream From the official documentation: “You can use Datastream to monitor the data and events that a stream processes and configure alerting policies to track replication health.”
- AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “The AlloyDB Auth Proxy and AlloyDB Language Connectors let you use [Identity and Access Management](/iam/docs/overview) (IAM) to control who has access to your data.”
- BigQuery works with Data Catalog From the official documentation: “Data Catalog integrates with BigQuery by automatically cataloging metadata about BigQuery resources like tables, datasets, views, and models.”
- BigQuery works with labels From the official documentation: “Labels are exported to BigQuery with the corresponding Google Cloud resources and their usage.”
- BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
- Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
- Cloud Logging works with Dataproc Metastore From the official documentation: “Dataproc Metastore exports request and system logs to Cloud Logging.”
- 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.”
- Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
- Cloud Monitoring works with Knowledge Catalog From the official documentation: “Cloud Logging and Cloud Monitoring let you track billable token consumption for Knowledge Catalog (formerly Dataplex Universal Catalog) data insights scans.”
- Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
- Cloud SQL is an alternative to Dataproc Metastore From the official documentation: “If you are using Cloud SQL as a Metastore using the `cloud-sql-proxy.sh` initialization action, refer to its specific troubleshooting in the [Cloud SQL Proxy initialization action…”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
How learners score on this topic
Last updated