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
Backup and DR
Topic in 2 exam domains
Also called: Backup and DR API, Backup and DR Service, backupdr, Google Cloud Backup and DR, Google Cloud Backup and DR Service
Google Cloud's centralized backup and disaster recovery service for workloads, databases, and virtual machines.
Where this appears on the exam
2 objectives in 2 of 5 domains
~22% of exam
~18% of exam
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedCloud Key Management ServiceServiceVPC Service ControlsServiceIdentity and Access ManagementServiceApplication Default CredentialsFeatureCloud MonitoringServicecustomer-managed encryption keysFeatureBigQueryServiceCloud RunServiceCloud Run functionsServiceDataflowService
Backup and DRService
Cloud StorageServiceCloud LoggingServiceDatabase Migration ServiceServiceCommitted use discountsFeatureGKEServiceCloud SQLServiceAlloyDBServiceCompute EngineServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Backup and DR works with Compute Engine From the official documentation: “This page details how to use Backup and DR to back up the disks of a Compute Engine instance.”
- Backup and DR works with Cloud Key Management Service From the official documentation: “Backup and DR supports customer-managed encryption keys (CMEK) that are managed in Cloud Key Management Service.”
- Backup and DR works with Cloud SQL From the official documentation: “Enable the Backup and DR API where the Cloud SQL instances are located.”
- Backup and DR works with Cloud Storage From the official documentation: “A storage pool, which associates a Cloud Storage bucket with Backup and DR,<br>was removed from the Backup and DR management console.”
- Backup and DR secures Compute Engine From the official documentation: “Backup and DR ensures that the chosen Compute Engine instances get backed up per the frequency set in the backup policy.”
- VPC Service Controls secures Backup and DR From the official documentation: “Enclose backup operations within VPC Service Controls security perimeters to help secure your backup workflows.”
- Backup and DR secures AlloyDB From the official documentation: “Learn how to use Backup and DR to protect an AlloyDB cluster with immutable storage and restore it in the event of data loss.”
- Backup and DR works with BigQuery From the official documentation: “Backup and DR integrates with Cloud Monitoring, Cloud Logging, and BigQuery services and provides the following benefits:”
- Backup and DR works with Cloud Logging From the official documentation: “You can view Backup and DR event logs in **Cloud Logging** by using the Google Cloud console and the Google Cloud CLI.”
- Backup and DR works with Cloud Monitoring From the official documentation: “Backup and DR integrates with Cloud Monitoring, Cloud Logging, and BigQuery services and provides the following benefits:”
- Backup and DR secures Cloud SQL From the official documentation: “Cloud SQL is protected by Backup and DR Service”
- Backup and DR works with Committed use discounts From the official documentation: “This page describes how committed use discounts work with Backup and DR for Oracle databases.”
- Backup and DR works with customer-managed encryption keys From the official documentation: “This guide explains how to enhance backup security by using Customer-Managed Encryption Keys (CMEK) with Backup and DR.”
- Backup and DR depends on Identity and Access Management From the official documentation: “To access Backup and DR, each user needs a Google Account that has been added to a Google Cloud project, folder, or organization as a principal with an Identity and Access Management role that allows access to the Google Cloud console.”
- Backup and DR works with Identity and Access Management From the official documentation: “The Google Cloud-native Backup and DR Service integrates with the Google Cloud ecosystem, including simplified sign-on via SSO, seamless integration with Identity and Access Management (IAM), Cloud Logging, Cloud Monitoring, Key Management, and more.”
- Backup and DR works with VPC Service Controls From the official documentation: “This page gives an overview of [VPC Service Controls](/vpc-service-controls) and how you can integrate it with Backup and DR to secure your data and resources.”
- customer-managed encryption keys secures Backup and DR From the official documentation: “With CMEK, you can protect your Backup and DR data using a cryptographic key that you control through Cloud Key Management Service.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
- AlloyDB depends on Application Default Credentials From the official documentation: “To authenticate to AlloyDB, set up Application Default Credentials.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, 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.”
- Cloud SQL works with Database Migration Service From the official documentation: “Migrating from Cloud SQL to AlloyDB for PostgreSQL using Database Migration Service”
- 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”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- AlloyDB works with Application Default Credentials From the official documentation: “To authenticate to AlloyDB, set up Application Default Credentials.”
- 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.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, 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 Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
- 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.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Application Default Credentials works with Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
- Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Cloud Run functions works with Cloud Storage From the official documentation: “Set up functions in response to events in Cloud Storage:”
- Cloud Storage works with Database Migration Service From the official documentation: “Database Migration Service replicates data from SQL Server backup and transaction log files that you upload to a Cloud Storage bucket.”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- BigQuery works with Cloud Run functions From the official documentation: “BigQuery supports external function calls through Cloud Run functions.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
How learners score on this topic
Last updated