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 feature
point-in-time recovery
Topic in 1 exam domain
- point-in-time recovery · Feature
- point-in-time recovery · Concept
- point-in-time recovery · Task
- point-in-time-recovery · Feature
- Point In Time Recovery · Feature · DynamoDB feature
- Point-in-Time Recovery · Feature
- Point-in-time recovery · Feature
- Point-in-Time Recovery · Task · pgBackRest
Also called: Enable PITR, PIT, PiTR, PITR feature, PITR restore, Point In Time, Point In Time (PIT), pointInTimeRecoveryEnabled, Recover to a specific point in time, recovery to a specific point in time
A recovery mechanism whose transaction logs are overwritten during an instance restore.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicAppliedIdentity and Access ManagementServiceApplication Default CredentialsFeatureAlloyDB for PostgreSQLServiceSpannerServiceCloud StorageServiceFirestoreServicecustomer-managed encryption keysFeatureCloud SQLServiceCloud LoggingService
point-in-time recoveryFeature
BigQueryServiceDatabase Migration ServiceServicehigh availabilityFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- 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:”
- Cloud Storage works with point-in-time recovery From the official documentation: “You can export your database to Cloud Storage from PITR data using the [`gcloud firestore export`][sdk] command.”
- 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.”
- Database Migration Service depends on point-in-time recovery From the official documentation: “Your source Cloud SQL for SQL Server must have point-in-time recovery (PITR) enabled so that Database Migration Service can create transaction log backup files.”
- 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.”
- point-in-time recovery is part of Firestore From the official documentation: “After you enable PITR, Firestore starts retaining PITR data.”
- Firestore depends on Application Default Credentials From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- 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.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- AlloyDB for PostgreSQL works with Database Migration Service From the official documentation: “Database Migration Service helps you migrate your data to AlloyDB for PostgreSQL.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, 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.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, 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.”
- Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, 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.”
- Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- 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.”
- BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- 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.”
- customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
- customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- high availability is part of Cloud SQL From the official documentation: “HA in Cloud SQL works by having two synchronized instances: a primary instance and a standby instance.”
- Identity and Access Management secures Database Migration Service From the official documentation: “You can get and set permissions for Database Migration Service using the Google Cloud console, the IAM methods of the API, or the Google Cloud CLI.”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- Cloud Logging works with Database Migration Service From the official documentation: “Database Migration Service uses Cloud Logging.”
- Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- 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).”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- customer-managed encryption keys works with Database Migration Service From the official documentation: “Database Migration Service supports CMEK in the migration job to secure the data at rest.”
- Database Migration Service depends on Cloud Logging From the official documentation: “Database Migration Service uses Cloud Logging.”
- 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.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “BigQuery AlloyDB federation lets BigQuery query data residing in AlloyDB in real time without copying or moving the data.”
- AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB supports importing and exporting compressed `.gz` files from Cloud Storage.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- customer-managed encryption keys secures Database Migration Service From the official documentation: “When you protect data in Database Migration Service with CMEK, the CMEK is within your control.”
- customer-managed encryption keys works with Spanner From the official documentation: “This page describes how to use manually-created customer-managed encryption keys (CMEK) for Spanner.”
- Identity and Access Management secures Spanner From the official documentation: “Spanner uses Identity and Access Management (IAM) for authorization.”
- AlloyDB for PostgreSQL is an alternative to Cloud SQL From the official documentation: “The sample code uses Cloud SQL as the vector database, whereas this reference architecture uses AlloyDB for PostgreSQL.”
- Application Default Credentials secures Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- BigQuery works with Firestore From the official documentation: “You can load data from a Firestore with MongoDB compatibility export into BigQuery, but only if you specified a `collection-ids` filter.”
- Cloud SQL is an alternative to Firestore From the official documentation: “Check your application code for reliance on local filesystems, and replace it with file storage on [Cloud Storage](/storage) or data storage such as [Firestore](/firestore) or [Cloud SQL](/sql).”
- customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
- customer-managed encryption keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
- Database Migration Service depends on Cloud SQL From the official documentation: “For heterogeneous Oracle migrations to Cloud SQL, Database Migration Service requires that you first create and configure your Cloud SQL destination instance.”
- high availability is part of AlloyDB for PostgreSQL From the official documentation: “AlloyDB for PostgreSQL supports high availability on both primary and secondary instances.”
How learners score on this topic
Last updated