automated backups on Associate Data Practitioner

What you can expect on the exam

Scheduled backup cadences and backup windows. Be ready to understand how automated backups in Cloud SQL run during a designated backup window on regular cadences such as hourly, daily, weekly, or monthly.
Backup retention and incremental chains. Expect to evaluate retention policies ranging from 1 day to 10 years for automated backups in Cloud SQL, including how the deletion of the oldest backup promotes the next oldest into a full backup.
Prerequisites for replication and recovery features. You may need to know that features such as read replica instances, high availability configurations, and point-in-time recovery depend on having automated backups configured.
Retained backups after instance deletion. Know the difference between automated backups deleted on a rolling basis as retained backups at the project level and standard on-demand backups that persist until manually deleted.
Automated versus on-demand backup strategies. Be ready to compare automated backups against on-demand backups to determine suitable use cases, such as taking manual snapshots before risky operations or automating routine protection.

Where this appears on the exam

1 subdomain in 1 of 4 domains

Section 4
Data Management
1. 4.3Identify high availability and disaster recovery strategies for data in Cloud Storage and Cloud SQL
  - Compare backup and recovery solutions offered as Google-managed services

automated backupsFeature

Cloud StorageService SpannerService FirestoreService high availabilityFeature Cloud SQLService on-demand backupsFeature point-in-time recoveryFeature read replicaFeature

Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two

automated backups is part of Cloud SQL From the official documentation: “You can take on-demand, automated, or final backups for your Cloud SQL instances.”
automated backups is an alternative to on-demand backups From the official documentation: “There are two database backup methods for Cloud SQL for PostgreSQL: on-demand and automated.”
high availability depends on automated backups From the official documentation: “Check the instance to see if automatic backups and binary logs are enabled. These are required for high availability instances.”
point-in-time recovery depends on automated backups From the official documentation: “In addition, Cloud SQL for PostgreSQL lets you restore a PostgreSQL database to a specific [point in time](/sql/docs/postgres/backup-recovery/pitr) as long as point-in-time recovery is turned on and the automated backup option is enabled.”
Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
point-in-time recovery is part of Spanner From the official documentation: “Spanner point-in-time recovery (PITR) provides protection against accidental deletion or writes.”
Cloud SQL is an alternative to Spanner From the official documentation: “If a workload requires transaction processing with strong relational consistencies, [Spanner](/spanner/docs/overview) or [Cloud SQL](/sql/docs) can be better alternatives.”
Cloud Storage works with point-in-time recovery From the official documentation: “For data retention needs beyond 14 weeks, you can use PITR to create an export of your entire database and save this data in Cloud Storage indefinitely.”
high availability is part of Cloud SQL From the official documentation: “You can configure a Cloud SQL instance for high availability by using the Google Cloud console, [gcloud CLI](/sdk/gcloud), or the API.”
point-in-time recovery is an alternative to read replica From the official documentation: “You can recover a standalone instance from a zonal outage manually by performing either point-in-time-recovery or by promoting a read replica to become the standalone instance.”
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 is an alternative to Firestore From the official documentation: “If you're interested in evaluating how the performance of your on-premises databases compares to [Cloud SQL](/sql), [Spanner](/spanner), [Firestore](/firestore), or [Bigtable](/bigtable), you could implement a PoC where the same business logic uses different databases.”
Cloud SQL configures high availability From the official documentation: “If you want your instance to be replicated between zones synchronously, then [configure it for high availability](/sql/docs/mysql/high-availability).”
Cloud Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
high availability configures Cloud SQL From the official documentation: “If you want your instance to be replicated between zones synchronously, then [configure it for high availability](/sql/docs/postgres/high-availability).”
high availability depends on point-in-time recovery From the official documentation: “Check the instance to see if automatic backups and point-in-time recovery are enabled. These are required for high availability instances.”
on-demand backups is part of Cloud SQL From the official documentation: “You can take on-demand, automated, or final backups for your Cloud SQL instances.”
point-in-time recovery is part of Cloud SQL From the official documentation: “Cloud SQL provides the following options to restore your instance using PITR:”
point-in-time recovery depends on Cloud Storage From the official documentation: “Must store the transaction logs used for PITR in Cloud Storage”
point-in-time recovery is part of Firestore From the official documentation: “After you enable PITR, Firestore starts retaining PITR data.”
read replica is part of Cloud SQL From the official documentation: “This page applies to replicas of a Cloud SQL instance.”
read replica depends on point-in-time recovery From the official documentation: “Additionally, the point-in-time recovery option, which uses write-ahead logs, is also required for creating a read replica.”

automated backups

What you can expect on the exam

Where this appears on the exam

How learners score on this topic

automated backups

What you can expect on the exam

Where this appears on the exam

How learners score on this topic

What you can expect on the exam

Where this appears on the exam

Related topics

How learners score on this topic

What you can expect on the exam

Where this appears on the exam

Related topics

How learners score on this topic