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
dynamic data masking
Topic in 1 exam domain
A BigQuery capability that automatically masks column data at query runtime based on masking rules and user roles.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicApplication Default CredentialsFeatureVPC Service ControlsServicePub/SubServiceSensitive Data ProtectionServiceCloud StorageServiceBigQueryServiceKnowledge CatalogServicepolicy tagsFeatureData CatalogService
dynamic data maskingFeature
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- dynamic data masking is part of BigQuery From the official documentation: “BigQuery supports [dynamic data masking](/bigquery/docs/column-data-masking-intro) at the column level.”
- dynamic data masking depends on Data Catalog From the official documentation: “The Data Catalog API (`datacatalog.googleapis.com`) must remain enabled in projects that use BigQuery column-level access control or dynamic data masking.”
- policy tags configures dynamic data masking From the official documentation: “Policy tags in BigQuery let you enforce [column-level access control](/bigquery/docs/column-level-security-intro) and [dynamic data masking](/bigquery/docs/column-data-masking-intro) on sensitive table data.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Sensitive Data Protection depends on Application Default Credentials From the official documentation: “To authenticate to Sensitive Data Protection, 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.”
- BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, 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.”
- Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- Application Default Credentials secures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, 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.”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Data Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Data Catalog, set up Application Default Credentials.”
- Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
- Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
- Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
- Application Default Credentials works with Data Catalog From the official documentation: “To authenticate to Data Catalog, set up Application Default Credentials.”
- Application Default Credentials works with Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Data Catalog is an alternative to Knowledge Catalog From the official documentation: “Use Knowledge Catalog for all new projects to take advantage of AI-powered features and enhanced governance.”
- Data Catalog is part of Knowledge Catalog From the official documentation: “Knowledge Catalog features”
- Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- BigQuery works with Data Catalog From the official documentation: “The instructions in this page use both BigQuery and Data Catalog.”
- Data Catalog works with Sensitive Data Protection From the official documentation: “Send job results to Data Catalog. This feature is [deprecated](/sensitive-data-protection/docs/deprecations).”
- Knowledge Catalog works with Sensitive Data Protection From the official documentation: “Send the results of a [BigQuery inspection job](/sensitive-data-protection/docs/inspecting-storage#inspect_a_table) to Knowledge Catalog.”
- Sensitive Data Protection works with VPC Service Controls From the official documentation: “For information about VPC Service Controls support for Sensitive Data Protection, see the [Supported products](/vpc-service-controls/docs/supported-products#table_dlp) table in the VPC Service Controls documentation.”
- VPC Service Controls secures Knowledge Catalog From the official documentation: “The API for Knowledge Catalog can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- 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 configures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
- 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 Storage works with Data Catalog From the official documentation: “Data Catalog supports the definition of Cloud Storage file entries and their schema.”
- Cloud Storage works with Knowledge Catalog From the official documentation: “To automatically discover and build inventories of the data assets, integrate Knowledge Catalog with your storage systems, such as [BigQuery](/bigquery/docs/introduction), [Cloud Storage](/storage/docs/introduction), and [Pub/Sub](/pubsub/docs/overview).”
- Data Catalog works with policy tags From the official documentation: “You can move a policy tag only through the Data Catalog `PolicyTagManager.UpdatePolicyTag` method.”
- Data Catalog works with Pub/Sub From the official documentation: “Pub/Sub topics are automatically registered with the Data Catalog.”
- Data Catalog works with VPC Service Controls From the official documentation: “The Data Catalog integration with VPC Service Controls has no known limitations.”
- Knowledge Catalog depends on Cloud Storage From the official documentation: “Looker (Google Cloud core) publishes LookML metadata to regional Cloud Storage repositories for Knowledge Catalog to consume through a batch sync process.”
- Knowledge Catalog works with Pub/Sub From the official documentation: “To automatically discover and build inventories of the data assets, integrate Knowledge Catalog with your storage systems, such as [BigQuery](/bigquery/docs/introduction), [Cloud Storage](/storage/docs/introduction), and [Pub/Sub](/pubsub/docs/overview).”
- Knowledge Catalog works with VPC Service Controls From the official documentation: “The integration between Looker (Google Cloud core) and Knowledge Catalog supports VPC Service Controls.”
- policy tags is part of BigQuery From the official documentation: “Policy tags in BigQuery let you enforce [column-level access control](/bigquery/docs/column-level-security-intro) and [dynamic data masking](/bigquery/docs/column-data-masking-intro) on sensitive table data.”
- policy tags works with Sensitive Data Protection From the official documentation: “To determine the types of sensitive data that you have and which columns need policy tags, consider generating profiles about your data across an organization, folder, or project by using Sensitive Data Protection.”
- Sensitive Data Protection secures BigQuery From the official documentation: “To help meet compliance requirements, use Sensitive Data Protection to inspect your BigQuery tables and to help protect your sensitive data.”
- VPC Service Controls secures Sensitive Data Protection From the official documentation: “VPC Service Controls enables you to define a security perimeter around your projects and resources, including Sensitive Data Protection resources.”
How learners score on this topic
Last updated