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
AlloyDB for PostgreSQL
Topic in 5 exam domains
Also called: AlloyDB for PostgreSQL service, fully-managed AlloyDB service on Google Cloud, Google Cloud AlloyDB, Google Cloud AlloyDB for PostgreSQL
A fully managed, PostgreSQL-compatible relational database service offered by Google Cloud.
Where this appears on the exam
3 objectives in 2 of 5 domains
Domain 3
Storing the data~20% of exam
~15% of exam
Related topics
FoundationsThis topicWorks alongsideAppliedPrivate Service ConnectFeaturecustomer-managed encryption keysFeatureCloud LoggingServiceIdentity and Access ManagementServiceVPC Service ControlsServiceDatabase Migration ServiceService
AlloyDB for PostgreSQLService
Cloud SQLServiceCloud StorageServiceBigQueryServiceGemini Cloud AssistServiceAlloyDBServiceCloud RunServiceKnowledge CatalogServiceDatastreamServiceCloud MonitoringServiceSpannerServiceQuery insightsFeaturehigh availabilityFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- AlloyDB for PostgreSQL works with Database Migration Service From the official documentation: “Database Migration Service helps you migrate your data to AlloyDB for PostgreSQL.”
- AlloyDB for PostgreSQL works with Datastream From the official documentation: “Datastream works with the following types of PostgreSQL databases: - AlloyDB for PostgreSQL”
- 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.”
- AlloyDB for PostgreSQL works with Private Service Connect From the official documentation: “This page describes how to use Private Service Connect to connect to an AlloyDB for PostgreSQL instance.”
- Query insights is part of AlloyDB for PostgreSQL From the official documentation: “To help you analyze and improve query performance of the databases,<br>AlloyDB for PostgreSQL provides a Query Insights tool.”
- AlloyDB for PostgreSQL works with Cloud Run From the official documentation: “The Cloud Run service can connect to the AlloyDB instance.”
- 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 Gemini Cloud Assist From the official documentation: “You can use Gemini Cloud Assist to help you monitor and troubleshoot your AlloyDB resources.”
- AlloyDB for PostgreSQL works with Knowledge Catalog From the official documentation: “Enable the Knowledge Catalog integration for your AlloyDB cluster”
- high availability is part of AlloyDB for PostgreSQL From the official documentation: “AlloyDB for PostgreSQL supports high availability on both primary and secondary instances.”
- AlloyDB for PostgreSQL works with Cloud Logging From the official documentation: “AlloyDB processes user-generated audit logs asynchronously before securely forwarding them to Cloud Logging.”
- AlloyDB for PostgreSQL works with customer-managed encryption keys From the official documentation: “This page describes how to create, configure, and apply customer-managed encryption keys (CMEK) for AlloyDB for PostgreSQL.”
- AlloyDB for PostgreSQL works with Identity and Access Management From the official documentation: “This page explains the process of logging into an AlloyDB for PostgreSQL instance using an account prepared with Identity and Access Management (IAM).”
- customer-managed encryption keys secures AlloyDB for PostgreSQL From the official documentation: “If you enable CMEK on a cluster, then AlloyDB uses your key to encrypt all of your cluster's data in storage.”
- 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”
- 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 Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- 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 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.”
- Cloud SQL works with Private Service Connect From the official documentation: “You can use Private Service Connect to connect to a Cloud SQL instance from multiple VPC networks.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- 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 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.”
- 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”
- Database Migration Service depends on Private Service Connect From the official documentation: “Database Migration Service uses [Private Service Connect](/vpc/docs/private-service-connect) to connect to your destination Cloud SQL instance using a private IP address.”
- 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.”
- 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).”
- Query insights is part of Cloud SQL From the official documentation: “To disable query insights for a Cloud SQL instance by using the Google Cloud console, follow these steps:”
- 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 Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
- 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.”
- Cloud SQL works with Gemini Cloud Assist From the official documentation: “To use Gemini Cloud Assist with Cloud SQL, do the following:”
- 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 works with Database Migration Service From the official documentation: “Database Migration Service supports continuous migrations from source databases to AlloyDB destination databases.”
- 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.”
How learners score on this topic
Last updated