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
data profiling
Topic in 2 exam domains
- data profiling · Feature
- Data profiling · Feature · BigQuery
- Data profiling · Concept
- data profiling · Task
Also called: profiling
A capability for analyzing and profiling data within Knowledge Catalog.
Where this appears on the exam
2 subdomains in 2 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksThis topicWorks alongsideApplication Default CredentialsConceptKnowledge CatalogServiceSensitive Data ProtectionServiceCloud StorageServiceCloud LoggingServiceCloud SQLServiceBigQueryService
data profilingFeature
DatastreamServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery works with data profiling From the official documentation: “This page describes how to estimate the cost of profiling BigQuery data in a project.”
- data profiling depends on BigQuery From the official documentation: “To create data profile or data quality scans on CMEK-encrypted BigQuery resources, grant the Cloud KMS CryptoKey Encrypter/Decrypter (`roles/cloudkms.cryptoKeyEncrypterDecrypter`) role on the Cloud KMS key that protects the BigQuery dataset to both the Knowledge Catalog and…”
- data profiling is part of Knowledge Catalog From the official documentation: “With [data profiling](/knowledge-catalog/docs/data-profiling-overview), Knowledge Catalog finds statistics for top-level columns, like null percentages, uniqueness, and value distributions in your data to help you understand it.”
- 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 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.”
- 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.”
- Cloud Storage works with Datastream From the official documentation: “Because Cloud Storage is in the same network as Datastream, no special connectivity is required.”
- 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 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 works with BigQuery From the official documentation: “Create a BigQuery client using 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.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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 Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
- Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- 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.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- 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 SQL works with Sensitive Data Protection From the official documentation: “Sensitive Data Protection starts identifying your Cloud SQL instances and creating a default connection for each instance.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, 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 configures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- 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 Logging works with Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
- 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.”
- 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.”
- Knowledge Catalog works with Sensitive Data Protection From the official documentation: “This page describes how to automatically add Knowledge Catalog aspects to your data after Sensitive Data Protection profiles your resources.”
- Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, 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.”
- 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.”
- 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.”
- Datastream works with Knowledge Catalog From the official documentation: “Datastream also integrates with Knowledge Catalog for centralized metadata and lineage management across Google Cloud.”
- Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
How learners score on this topic
Last updated