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
Transfer Appliance
Topic in 6 exam domains
Also called: transferappliance
A hardware device used to migrate large volumes of data to Google Cloud.
Where this appears on the exam
3 objectives in 2 of 5 domains
Related topics
FoundationsThis topicWorks alongsideAppliedVPC Service ControlsServiceGoogle Cloud StorageServiceIdentity and Access ManagementServiceCloud LoggingService
Transfer ApplianceService
Managed Service for Apache AirflowServiceCloud StorageServiceBigQueryServicePub/SubServiceStorage Transfer ServiceServiceCloud MonitoringServiceCloud Audit LogsServiceGoogle SecOpsServiceCloud RunServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Google Cloud Storage works with Transfer Appliance From the official documentation: “You can use a Transfer Appliance to export your data from Cloud Storage.”
- Cloud Storage works with Transfer Appliance From the official documentation: “The appliance transfers the data you copy to it to Cloud Storage.”
- Storage Transfer Service is an alternative to Transfer Appliance From the official documentation: “For data copy options, see the following: 1. [Storage Transfer Service](/storage-transfer-service) or [Transfer Appliance](/transfer-appliance).”
- Transfer Appliance works with VPC Service Controls From the official documentation: “Transfer Appliance is fully supported for projects using VPC Service Controls.”
- Cloud Audit Logs works with Transfer Appliance From the official documentation: “This document describes audit logging for Transfer Appliance. Google Cloud services generate audit logs that record administrative and access activities within your Google Cloud resources.”
- Cloud Monitoring works with Transfer Appliance From the official documentation: “Transfer Appliance uses Cloud Monitoring to report on a wide range of appliance metrics.”
- Identity and Access Management secures Transfer Appliance From the official documentation: “Transfer Appliance uses [Identity and Access Management (IAM)](https://cloud.google.com/iam/) permissions and roles to control who can access Transfer Appliance resources.”
- 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”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
- 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.”
- 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 Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Cloud Logging works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
- Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow associates a Cloud Storage bucket with your environment.”
- BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
- BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
- Cloud Monitoring works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
- 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.”
- 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 Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
- 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 Logging works with Storage Transfer Service From the official documentation: “Enable Cloud Logging for agentless transfers, or transfers from S3-compatible sources, with `--log-actions` and `--log-action-states`.”
- 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.”
- VPC Service Controls secures Managed Service for Apache Airflow From the official documentation: “Managed Airflow can be selected as a secured service inside a VPC Service Controls perimeter.”
- 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 works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Audit Logs works with Cloud Storage From the official documentation: “Use Cloud Audit Logs to generate logs for API operations performed in Cloud Storage.”
- Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
- Cloud Run works with Google Cloud Storage From the official documentation: “The Cloud Run function will receive syslog messages from FortiEDR via HTTP and write them to GCS.”
- Google Cloud Storage works with Storage Transfer Service From the official documentation: “We use Storage Transfer Service to transfer data from the appliance to your Cloud Storage bucket.”
- Managed Service for Apache Airflow works with VPC Service Controls From the official documentation: “When used with Managed Airflow, VPC Service Controls have several [known limitations](/vpc-service-controls/docs/supported-products#composer).”
- Storage Transfer Service works with VPC Service Controls From the official documentation: “The Storage Transfer Service integration with VPC Service Controls has no known limitations.”
- BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
- Cloud Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
- Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
- Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- 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.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- Cloud Monitoring works with Google SecOps From the official documentation: “Google SecOps uses Cloud Monitoring to send the ingestion notifications.”
- Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
- 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.”
- Identity and Access Management secures Managed Service for Apache Airflow From the official documentation: “For access control, use Identity and Access Management and Managed Airflow [roles and permissions](/composer/docs/composer-2/access-control#user-account).”
- Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
How learners score on this topic
Last updated