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
replication
Topic in 1 exam domain
- replication · Feature
- Replication · Feature · Cloud Data Fusion feature
- replication · Concept
- Replication · Concept
Also called: Bigtable replication, kind: Replication, replication object, replication process, Replication resource
A database feature in Cloud SQL that synchronizes data from a primary instance to read replicas.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicDatastreamServiceVPC Service ControlsServiceIdentity and Access ManagementServiceCloud LoggingServiceCloud SQLServiceCloud Data FusionServiceBigtableServiceKnowledge CatalogServiceCloud StorageServiceCloud MonitoringService
replicationConcept
BigQueryServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery works with replication From the official documentation: “After the initial snapshot, incremental changes at the source are captured and applied to the BigQuery target as part of the ongoing replication process.”
- replication is part of Cloud Data Fusion From the official documentation: “In the Cloud Data Fusion web interface, click **Replication**.”
- Cloud SQL works with replication From the official documentation: “Cloud SQL supports various replication modes to migrate data into your instance.”
- replication is part of Bigtable From the official documentation: “**Bigtable** provides [Bigtable replication](/bigtable/docs/replication-overview).”
- replication is part of Cloud SQL From the official documentation: “Cloud SQL supports various replication modes to migrate data into your instance.”
- replication depends on Datastream From the official documentation: “Replication from Oracle sources in Cloud Data Fusion is powered by Datastream.”
- 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”
- BigQuery works with Datastream From the official documentation: “Permissions needed for datastream to write to BigQuery.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Storage works with Datastream From the official documentation: “When you stream to Cloud Storage, Datastream organizes data by object name and timestamp.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- 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 Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- 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 SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- 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).”
- 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 Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud SQL works with Datastream From the official documentation: “This page describes an example NAT VM configuration that lets Datastream privately connect to a Cloud SQL instance.”
- 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.”
- BigQuery works with Cloud Data Fusion From the official documentation: “Cloud Data Fusion pulls data from the storage bucket and writes it to BigQuery.”
- 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.”
- Cloud Data Fusion works with Cloud Logging From the official documentation: “Starting with Cloud Data Fusion version 6.11, pipeline logs and service logs are available in Cloud Logging.”
- Cloud Data Fusion works with Knowledge Catalog From the official documentation: “Cloud Data Fusion provides an integration with Knowledge Catalog for lineage.”
- Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
- VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
- Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
- Bigtable works with Identity and Access Management From the official documentation: “Bigtable uses [Identity and Access Management (IAM)](/iam) for access control.”
- 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.”
- Datastream works with Knowledge Catalog From the official documentation: “You can search for and manage your Datastream resources using Knowledge Catalog, which is a platform for storing, managing, and accessing your metadata.”
- Identity and Access Management secures Knowledge Catalog From the official documentation: “IAM controls access to your Knowledge Catalog resources at the Google Cloud resource level.”
- Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
- VPC Service Controls secures Knowledge Catalog From the official documentation: “The API for Knowledge Catalog can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
- 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.”
- Bigtable works with Cloud Logging From the official documentation: “You can audit the requests that Bigtable sends to Cloud KMS on your behalf in [Cloud Logging](/kms/docs/audit-logging), if you have [enabled Cloud KMS audit logs](/logging/docs/audit/configure-data-access#config-console-enable) for the Cloud KMS API in your project.”
- Bigtable works with Cloud Monitoring From the official documentation: “The following Bigtable metrics are provided to Cloud Monitoring.”
- Bigtable is an alternative to Cloud SQL 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.”
- Bigtable works with Cloud Storage From the official documentation: “Another way you can back up Bigtable is to use a managed data export to Cloud Storage.”
- Bigtable works with Knowledge Catalog From the official documentation: “Knowledge Catalog is also integrated with Bigtable, offering similar capabilities.”
- Cloud Data Fusion works with Cloud Monitoring From the official documentation: “Filter and aggregate Cloud Data Fusion pipeline and instance metrics in Monitoring using [*metric* and *monitored-resource* labels](/monitoring/api/v3/metric-model#generic-label-info).”
- Cloud Data Fusion works with Cloud SQL From the official documentation: “This page describes how to connect a private Cloud Data Fusion instance to a private Cloud SQL instance that hosts a MySQL database.”
- Cloud Data Fusion depends on Datastream From the official documentation: “When you run a replication job with an Oracle Database, Cloud Data Fusion uses the Datastream service in the backend.”
- Cloud Data Fusion is an alternative to Datastream From the official documentation: “Alternatively, to replicate data into BigQuery, you can also use Cloud Data Fusion or [Datastream](/datastream/docs/overview).”
- Cloud Data Fusion works with VPC Service Controls From the official documentation: “Using VPC Service Controls with Cloud Data Fusion”
- Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
- 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 Knowledge Catalog From the official documentation: “Knowledge Catalog sends logs for service operations and job executions to Cloud Logging.”
- 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 Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
- Cloud Monitoring works with Knowledge Catalog From the official documentation: “Knowledge Catalog is integrated with Cloud Monitoring, which collects metrics, events, and metadata from Knowledge Catalog services.”
- Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
How learners score on this topic
Last updated