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
Azure Blob Storage
Topic in 1 exam domain
Also called: Azure Storage, Blob Storage, Microsoft Azure Blob Storage V2, Microsoft Azure Storage Account
A Microsoft Azure object storage service used to store exported Intune log files for ingestion into Google SecOps.
Where this appears on the exam
1 objective in 1 of 5 domains
~15% of exam
Related topics
This topicWorks alongsideBuilds on theseApplied
Azure Blob StorageService
Cloud LoggingServicePub/SubServiceVPC Service ControlsServiceAmazon S3ServiceSensitive Data ProtectionServiceBigQuery OmniFeatureBigQuery Data Transfer ServiceServiceCloud StorageServiceGoogle Cloud StorageServiceCloud SQLServiceBigQueryServiceGoogle SecOpsServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Azure Blob Storage works with Google SecOps From the official documentation: “Google SecOps can use Azure Blob Storage to store Event Hub checkpoints, which track which events have been processed.”
- Azure Blob Storage works with BigQuery Omni From the official documentation: “BigQuery Omni writes to the specified Blob Storage location regardless of any existing content.”
- Amazon S3 is an alternative to Azure Blob Storage From the official documentation: “If your query result is larger than 20 GiB, consider exporting the results to [Amazon S3](/bigquery/docs/omni-aws-export-results-to-s3) or [Blob Storage](/bigquery/docs/omni-azure-export-results-to-azure-storage).”
- Azure Blob Storage works with BigQuery From the official documentation: “For information about how data flows between BigQuery and Azure Blob Storage, see [Data flow when exporting data](/bigquery/docs/omni-introduction#export-data).”
- Azure Blob Storage works with BigQuery Data Transfer Service From the official documentation: “You can use the BigQuery Data Transfer Service to transfer data from external sources, such as Amazon Simple Storage Service (Amazon S3), Azure Blob Storage, or Cloud Storage into Iceberg managed table.”
- Azure Blob Storage is an alternative to Cloud Storage From the official documentation: “**Storage bucket**: A bucket (Cloud Storage, Amazon S3, or Azure Blob Storage) in the cloud provider where your SAP systems are hosted.”
- BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
- 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 Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- 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 BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Amazon S3 works with Google SecOps From the official documentation: “Configure AWS S3 bucket and IAM for Google SecOps”
- 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.”
- Google Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
- BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
- 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.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
- 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.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- 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.”
- Amazon S3 is an alternative to Cloud Storage From the official documentation: “Data must be stored in either a Cloud Storage or Amazon S3 bucket.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
- 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 depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you are using the Google Cloud console, you can schedule recurring copies, and configure an email or Pub/Sub notifications with the BigQuery Data Transfer Service.”
- Cloud SQL works with Google Cloud Storage From the official documentation: “Imports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage.”
- VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
- Amazon S3 works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
- Amazon S3 works with BigQuery Omni From the official documentation: “To create an Amazon S3 connection with BigQuery Omni, see [Connect to Amazon S3](/bigquery/docs/omni-aws-create-connection).”
- BigQuery Data Transfer Service works with Cloud Storage From the official documentation: “Retrieving events from the provided Pub/Sub subscription for Cloud Storage event-driven transfer”
- Cloud Logging is an alternative to Google Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs in a Cloud Logging bucket, in a user-created Cloud Storage bucket, or in a Google Cloud-created and user-owned Cloud Storage bucket.”
- Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
- 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 depends on Google Cloud Storage From the official documentation: “This document explains how to ingest Desynova Contido logs to Google Security Operations using Google Cloud Storage V2.”
- 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 BigQuery Omni From the official documentation: “You can use VPC Service Controls perimeters to restrict access from BigQuery Omni to an external cloud service as an extra layer of defense.”
- VPC Service Controls secures Google Cloud Storage From the official documentation: “Storage Transfer Service supports on-premises transfers to Cloud Storage buckets protected by VPC Service Controls, under the following conditions:”
- Amazon S3 works with BigQuery From the official documentation: “Schedule recurring load jobs from Amazon S3 into BigQuery.”
- Amazon S3 works with Cloud Storage From the official documentation: “This section demonstrates how to synchronize data from Amazon S3 to a Cloud Storage bucket.”
- Amazon S3 is an alternative to Google Cloud Storage From the official documentation: “This document explains how to ingest Google Cloud Looker audit logs to Google Security Operations using Google Cloud Storage or Amazon S3.”
- Amazon S3 works with Sensitive Data Protection From the official documentation: “This page describes how to configure Sensitive Data Protection discovery for Amazon S3.”
- 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.”
- BigQuery Data Transfer Service works with Cloud Logging From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
- BigQuery Data Transfer Service works with Cloud SQL From the official documentation: “To transfer data from a private Cloud SQL instance in one project to BigQuery in another project, BigQuery Data Transfer Service requires a connector network to bridge private network connectivity.”
- BigQuery Data Transfer Service works with Google Cloud Storage From the official documentation: “As part of the data transfer, BigQuery Data Transfer Service writes data from Amazon Redshift to Cloud Storage as CSV files.”
- BigQuery Data Transfer Service depends on Pub/Sub From the official documentation: “The communication channel between the agent running on premises and BigQuery Data Transfer Service is by publishing Pub/Sub messages to a per transfer topic.”
- Cloud Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
- Cloud Logging works with Google Cloud Storage From the official documentation: “See [Routing and storage overview](/logging/docs/routing/overview) to route logs from Logging to Cloud Storage, BigQuery, or Pub/Sub.”
- Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
- 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.”
How learners score on this topic
Last updated