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
Concept
primary instance
Topic in 1 exam domain
- primary instance · Concept
- Primary instance · Concept · cross-region replication
- primary instance · Feature · AlloyDB
Also called: AlloyDB primary instance, cluster's primary instance, primary instances, regional AlloyDB primary instance, source server
The main database instance in AlloyDB that processes transactions and writes.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksThis topicWorks alongsideAdvanced disaster recoveryFeatureTerraformConceptPrivate Service ConnectFeatureAlloyDB for PostgreSQLServiceCloud Data FusionServiceVPC Service ControlsServiceDR replicaFeatureclusterConcepthigh availabilityFeatureBigQueryServiceswitchoverConceptfailoverConceptCloud SQLService
primary instanceConcept
write endpointFeatureReplicationConceptcross-region read replicaFeatureKnowledge CatalogServiceGKEServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- primary instance is part of cluster From the official documentation: “Clusters are regional resources that contain your primary instance and its associated data.”
- high availability works with primary instance From the official documentation: “HA in Cloud SQL works by having two synchronized instances: a primary instance and a standby instance.”
- primary instance is part of AlloyDB for PostgreSQL From the official documentation: “To deploy a database environment for your applications in AlloyDB for PostgreSQL, you create a cluster and its primary instance.”
- primary instance works with Replication From the official documentation: “Replication copies transactions from a primary instance to one or more read replicas.”
- cluster works with primary instance From the official documentation: “The cluster manages your regional storage and configuration settings, while the primary instance provides the compute resources for read and write operations.”
- cross-region read replica works with primary instance From the official documentation: “In addition to the regular cost associated with the instance, a cross-region replica incurs cross-region data transfer charges for replication logs sent from the primary instance to the replica instance, as described in [Network Egress…”
- DR replica works with primary instance From the official documentation: “A primary instance can failover to a replica only if the replica is a DR replica.”
- failover works with primary instance From the official documentation: “A failover is when Cloud SQL switches serving from the original primary instance to the standby instance.”
- Knowledge Catalog works with primary instance From the official documentation: “Knowledge Catalog retrieves metadata only from Cloud SQL primary instances and not from read replicas or external server replicas.”
- primary instance works with write endpoint From the official documentation: “A write endpoint is a global domain name service (DNS) name that resolves to the IP address of the current primary instance automatically.”
- Private Service Connect configures primary instance From the official documentation: “For information about creating a primary instance for a Private Service Connect-enabled cluster, see [Create an AlloyDB instance](/alloydb/docs/configure-private-service-connect#create-cluster).”
- switchover configures primary instance From the official documentation: “Once all standbys are successfully upgraded, the operator performs a switchover, promoting one of the upgraded standby instances to be your new primary instance.”
- Terraform configures primary instance From the official documentation: “To support read and write workloads in an AlloyDB for PostgreSQL cluster, you can create a primary instance by using the Google Cloud console, the Google Cloud CLI, Terraform, or the AlloyDB API.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Cloud SQL works with Private Service Connect From the official documentation: “`--psc` Connect to the Cloud SQL instance using Private Service Connect.”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- AlloyDB for PostgreSQL works with Private Service Connect From the official documentation: “Private Service Connect](/vpc/docs/private-service-connect) lets you create private and secure connections between your VPC networks and a Google Cloud service, such as AlloyDB for PostgreSQL.”
- Cloud Data Fusion works with Knowledge Catalog From the official documentation: “Cloud Data Fusion provides an integration with Knowledge Catalog for lineage.”
- 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.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “Datastream lets you stream from AlloyDB for PostgreSQL to BigQuery using the Free Tier, providing up to 100 GiB of change data capture data free every month.”
- 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.”
- AlloyDB for PostgreSQL works with Knowledge Catalog From the official documentation: “Enable the Knowledge Catalog integration for your AlloyDB cluster”
- 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 works with Private Service Connect From the official documentation: “Click the private zone that contains the DNS records for the Private Service Connect endpoints, which you created to allow BigQuery Toolkit for SAP to privately connect to the BigQuery and IAM APIs.”
- 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.”
- cross-region read replica is part of Cloud SQL From the official documentation: “Use the cross-region read replica feature for Cloud SQL to help you meet data residency standards for a designated region.”
- DR replica is part of Advanced disaster recovery From the official documentation: “As a required component of advanced DR, the DR replica has the following characteristics:”
- failover depends on high availability From the official documentation: “If high availability (HA) is available, trigger a failover.”
- 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.”
- Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
- Replication is part of Cloud Data Fusion From the official documentation: “In the Cloud Data Fusion web interface, click **Replication**.”
- switchover works with write endpoint From the official documentation: “This endpoint redirects incoming connections to the new primary instance automatically in case of a replica [failover or switchover](/sql/docs/sqlserver/replication/cross-region-replicas) operation.”
- write endpoint is part of Cloud SQL From the official documentation: “A write endpoint is available only for Cloud SQL Enterprise Plus edition instances that have private IP addresses and associated networks.”
- Advanced disaster recovery configures write endpoint From the official documentation: “If you already have a Cloud SQL Enterprise Plus edition instance without the write endpoint and you want Cloud SQL to generate a write endpoint automatically, then create a replica that's enabled for [advanced disaster…”
- AlloyDB for PostgreSQL works with GKE From the official documentation: “Connect from Google Kubernetes Engine (GKE) to AlloyDB”
- BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
- 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.”
- 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 works with Private Service Connect From the official documentation: “The option to select the connectivity type appears only if you selected a Cloud Data Fusion version that supports Private Service Connect.”
- Cloud Data Fusion works with VPC Service Controls From the official documentation: “Using VPC Service Controls with Cloud Data Fusion”
- 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 SQL works with Replication From the official documentation: “Cloud SQL supports various replication modes to migrate data into your instance.”
- Cloud SQL works with Terraform From the official documentation: “For more information about using Cloud SQL with Terraform, see [Cloud SQL Database Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) in the Terraform documentation.”
- Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
- cluster is part of AlloyDB for PostgreSQL From the official documentation: “To deploy a database environment for your applications in AlloyDB for PostgreSQL, you create a cluster and its primary instance.”
- cluster works with GKE From the official documentation: “GKE is a container orchestration platform that works by connecting VMs into a *cluster*.”
- failover works with write endpoint From the official documentation: “This endpoint redirects incoming connections to the new primary instance automatically in case of a replica [failover or switchover](/sql/docs/sqlserver/replication/cross-region-replicas) operation.”
- GKE works with Private Service Connect From the official documentation: “This page provides an overview of Private Service Connect in Google Kubernetes Engine (GKE) clusters.”
- GKE works with Terraform From the official documentation: “Terraform is a popular open source IaC tool created by HashiCorp that supports a wide range of Cloud services, including GKE.”
- high availability is part of AlloyDB for PostgreSQL From the official documentation: “High availability (HA) in AlloyDB for PostgreSQL keeps your database operational and your data accessible to client applications during zonal or instance failures.”
- 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).”
- Knowledge Catalog works with VPC Service Controls From the official documentation: “The integration between Looker (Google Cloud core) and Knowledge Catalog supports VPC Service Controls.”
- Private Service Connect configures Cloud SQL From the official documentation: “To create an instance with a private IP address, you can create an instance enabled with either [private services access](/sql/docs/postgres/configure-private-services-access) or [Private Service Connect](/sql/docs/postgres/about-private-service-connect).”
- Private Service Connect configures cluster From the official documentation: “To restore a cluster with Private Service Connect enabled, make sure that you add the `--enable-private-service-connect` flag.”
- Replication is part of Cloud SQL From the official documentation: “Cloud SQL supports various replication modes to migrate data into your instance.”
- switchover is part of Advanced disaster recovery From the official documentation: “You can also use the switchover operation of advanced DR to perform routine DR drills to test and prepare your Cloud SQL topology for cross-regional failover *before* a disaster occurs.”
- switchover depends on DR replica From the official documentation: “However, if no DR replica is assigned to a primary instance, then you can't perform switchover or replica failover.”
- Terraform configures cluster From the official documentation: “The gcloud CLI and Terraform only support updating admin and user clusters.”
How learners score on this topic
Last updated