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
data quality rules
Topic in 2 exam domains
- data quality rules · Concept
- Data quality rules · Concept · business glossary term property
Also called: data quality expectations, DQ rules, quality rules
Rules specified for a data quality scan, including rule details such as filters and sampling percent.
Where this appears on the exam
2 subdomains in 2 of 5 domains
~22% of exam
~25% of exam
Related topics
FoundationsBuilding blocksThis topicAppliedTerraformConceptApplication Default CredentialsFeatureCompute EngineServiceSecret ManagerServiceCloud StorageServiceKnowledge CatalogServiceGKEServiceCloud SQLService
data quality rulesConcept
Cloud BuildServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Cloud Build works with data quality rules From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
- data quality rules is part of Knowledge Catalog From the official documentation: “You can declare data quality rules as aspects in Knowledge Catalog to make them searchable and reusable across scans.”
- data quality rules works with Terraform From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
- 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.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
- 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 Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- 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.”
- Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- 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.”
- Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- Terraform configures Compute Engine From the official documentation: “Provisioning Compute Engine virtual machines (VMs) with Terraform lets you evaluate Google Distributed Cloud in high availability (HA) mode without physical hardware.”
- Cloud Build works with Cloud SQL From the official documentation: “This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Build.”
- Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
- 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.”
- 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.”
- GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- 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 configures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
- Cloud Build depends on Secret Manager From the official documentation: “Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only.”
- Cloud SQL works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
- Cloud Storage works with Knowledge Catalog From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
- Application Default Credentials works with Cloud Build From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
- Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, 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.”
- Application Default Credentials secures Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud Build depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
- Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
- Cloud Build works with Compute Engine From the official documentation: “Automating builds on repository events ensures that Cloud Build immediately validates, builds, and publishes your custom OS images to Compute Engine and Artifact Registry upon code review or merge.”
- Cloud Build is an alternative to Compute Engine From the official documentation: “If Cloud Build is not available, use a small Compute Engine VM with a cron job to pull IOC data and write to GCS.”
- Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
- Cloud Build works with Terraform From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
- Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Cloud SQL works with Terraform From the official documentation: “For more information about using Cloud SQL with Terraform, see [Cloud SQL Database Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) in the Terraform documentation.”
- GKE works with Terraform From the official documentation: “Terraform is a popular open source IaC tool created by HashiCorp that supports a wide range of Cloud services, including GKE.”
- Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Secret Manager works with Terraform From the official documentation: “- Secret Manager: You can store and retrieve the secret using Secret Manager. To learn how to use Secret Manager with Terraform, see [google_secret_manager_secret](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/secret_manager_secret.html).”
- Terraform configures Knowledge Catalog From the official documentation: “Automate your infrastructure by [provisioning Knowledge Catalog resources with Terraform](/knowledge-catalog/docs/terraform) to manage your data quality specifications and metadata enrichment at scale.”
How learners score on this topic
Last updated