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
discovery service
Topic in 2 exam domains
Also called: discovery, secrets discovery
A feature within Sensitive Data Protection responsible for automatically scanning and generating data profiles across organizational resources.
Where this appears on the exam
2 objectives in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedApplication Default CredentialsFeatureSecurity Command CenterServiceSensitive Data ProtectionServiceIdentity and Access ManagementService
discovery serviceFeature
BigQueryServiceKnowledge CatalogServiceCloud StorageServiceVertex AIServicePub/SubServiceCloud SQLServiceGoogle SecOpsServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- discovery service works with Google SecOps From the official documentation: “Additionally, discovery can connect to other Google Cloud services like Security Command Center, Google Security Operations, and Knowledge Catalog to enrich security operations and data management.”
- discovery service works with Knowledge Catalog From the official documentation: “Additionally, discovery can connect to other Google Cloud services like Security Command Center, Google Security Operations, and Knowledge Catalog to enrich security operations and data management.”
- discovery service works with Security Command Center From the official documentation: “Additionally, discovery can connect to other Google Cloud services like Security Command Center, Google Security Operations, and Knowledge Catalog to enrich security operations and data management.”
- discovery service is part of Sensitive Data Protection From the official documentation: “This page shows you how to resolve issues with the discovery service of Sensitive Data Protection.”
- discovery service works with Vertex AI From the official documentation: “This page describes Sensitive Data Protection discovery for use with Vertex AI.”
- 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.”
- Vertex AI depends on Application Default Credentials From the official documentation: “To authenticate to Vertex AI, 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.”
- Security Command Center depends on Application Default Credentials From the official documentation: “To authenticate to Security Command Center, 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.”
- Application Default Credentials secures Vertex AI From the official documentation: “To authenticate to Vertex AI, set up Application Default Credentials.”
- Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- 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.”
- Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Cloud SQL works with Vertex AI From the official documentation: “This page describes how to integrate Cloud SQL with [Vertex AI](/vertex-ai/docs).”
- 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 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 Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
- 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.”
- Application Default Credentials works with Security Command Center From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
- Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
- 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.”
- Security Command Center works with Sensitive Data Protection From the official documentation: “Sending Sensitive Data Protection scan results to Security Command Center”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, 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.”
- 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.”
- Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials works with Vertex AI From the official documentation: “To authenticate to Vertex AI, set up Application Default Credentials.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Identity and Access Management secures Vertex AI From the official documentation: “A Vertex AI model with an active endpoint that you have Identity and Access Management (IAM) permission to access.”
- 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 Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
- BigQuery works with Vertex AI From the official documentation: “The page provides guidance for getting predictions from Vertex AI, based on retail [data exported into BigQuery](/retail/docs/export-data-into-bq).”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Google SecOps works with Security Command Center From the official documentation: “This document explains how to integrate Security Command Center with Google Security Operations.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Identity and Access Management secures Knowledge Catalog From the official documentation: “IAM controls access to your Knowledge Catalog resources at the Google Cloud resource level.”
- Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
- 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.”
- Pub/Sub works with Security Command Center From the official documentation: “This page explains how to use the Security Command Center API to enable finding notifications for Pub/Sub.”
How learners score on this topic
Last updated