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 service
Cloud Data Loss Prevention API
Topic in 1 exam domain
- Cloud Data Loss Prevention API · Service · Google Cloud API
- Cloud Data Loss Prevention API · Feature
Also called: Cloud Data Loss Prevention (DLP) API, Cloud DLP API, DLP API, Sensitive Data Protection API
The API name maintained by Sensitive Data Protection for data loss prevention operations.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicApplication Default CredentialsFeatureVPC Service ControlsServicePub/SubServiceCloud StorageServiceSensitive Data ProtectionServiceBigQueryServiceDataflowServiceGoogle SecOpsServiceCloud SQLService
Cloud Data Loss Prevention APIService
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery works with Cloud Data Loss Prevention API From the official documentation: “Use the Data Loss Prevention API to compute risk metrics of a column of categorical data in a BigQuery table.”
- Cloud Data Loss Prevention API is part of Sensitive Data Protection From the official documentation: “Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection.”
- Cloud Data Loss Prevention API works with Cloud Storage From the official documentation: “Learn how to [de-identify sensitive data stored in Cloud Storage using the DLP API](/sensitive-data-protection/docs/deidentify-storage).”
- 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.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- 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.”
- 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 Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, 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.”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- 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.”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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 Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- 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 Dataflow From the official documentation: “To authenticate to Dataflow, 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.”
- 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.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
- Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
- Dataflow works with Sensitive Data Protection From the official documentation: “Use Dataflow and Sensitive Data Protection to securely tokenize and import data from a relational database to BigQuery.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- 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.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, 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).”
- 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 is an alternative to Dataflow From the official documentation: “To automate the EDA process, use BigQuery or a managed data processing service like Dataflow.”
- 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 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 works with Google SecOps From the official documentation: “This document describes how fields of Cloud SQL context logs map to Google Security Operations Unified Data Model (UDM) fields.”
- 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.”
- Dataflow works with VPC Service Controls From the official documentation: “To customize DNS resolution when using Dataflow with VPC Service Controls, use Cloud DNS [private zones](/dns/docs/overview#dns-private-zones) instead of using custom BIND servers.”
- Google SecOps works with Pub/Sub From the official documentation: “This document explains how to integrate Pub/Sub with Google Security Operations.”
- Google SecOps works with Sensitive Data Protection From the official documentation: “You can export your Sensitive Data Protection data to Google SecOps.”
- Google SecOps works with VPC Service Controls From the official documentation: “Configure Google Security Operations with VPC Service Controls so that Google SecOps can access resources and services outside its service perimeter.”
- 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 Dataflow From the official documentation: “Place your Dataflow pipelines inside a security perimeter using VPC Service Controls.”
- VPC Service Controls secures Google SecOps From the official documentation: “The APIs for Google Security Operations can be protected by VPC Service Controls and Google SecOps can be used normally inside service perimeters.”
- 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