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
Topic in 2 exam domains
Also called: Google AlloyDB
A fully managed relational database service offered by Google Cloud that is compatible with PostgreSQL.
Where this appears on the exam
1 objective in 1 of 5 domains
Related topics
FoundationsBuilding blocksThis topicWorks alongsideAppliedApplication Default CredentialsFeatureVPC Service ControlsServiceAccess ApprovalServiceCMEKFeaturecustomer-managed encryption keysFeatureIdentity and Access ManagementServiceCompute EngineServiceVertex AIServiceCloud RunServiceBigQueryServiceCloud StorageServiceDatabase Migration ServiceServiceSecret ManagerServiceCloud SQLService
AlloyDBService
Gemini Cloud AssistServiceAlloyDB for PostgreSQLServiceWorkflowsServicepgvectorFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- AlloyDB depends on Application Default Credentials From the official documentation: “To authenticate to AlloyDB, set up Application Default Credentials.”
- AlloyDB works with Application Default Credentials From the official documentation: “To authenticate to AlloyDB, set up Application Default Credentials.”
- CMEK secures AlloyDB From the official documentation: “Enable CMEK for AlloyDB Clusters”
- AlloyDB works with Database Migration Service From the official documentation: “Database Migration Service supports continuous migrations from source databases to AlloyDB destination databases.”
- AlloyDB works with Vertex AI From the official documentation: “Reference architecture for a RAG-capable generative AI application using Vertex AI and AlloyDB for PostgreSQL.”
- AlloyDB works with BigQuery From the official documentation: “By integrating AlloyDB and BigQuery, you can achieve a seamless flow of data between your transactional database and your data warehouse, which supports real-time analytics and helps you build powerful interactive applications.”
- AlloyDB works with Compute Engine From the official documentation: “This page describes how to connect the `psql` client tool from Compute Engine to an AlloyDB instance.”
- AlloyDB works with Gemini Cloud Assist From the official documentation: “You can use Gemini Cloud Assist to help you monitor and troubleshoot your AlloyDB resources.”
- customer-managed encryption keys secures AlloyDB From the official documentation: “Enable customer-managed encryption keys (CMEK) in the AlloyDB cluster to gain more control over data encryption and key management.”
- pgvector is part of AlloyDB From the official documentation: “This example requires: 1. An AlloyDB instance with pgvector extension and PUBLIC IP enabled”
- Access Approval secures AlloyDB From the official documentation: “You can use Access Approval and Access Transparency to control access to AlloyDB instances by Google personnel who support the service.”
- AlloyDB works with Cloud Run From the official documentation: “The A2A Agent's core is a serving and orchestration layer, such as Cloud Run. This layer manages interactions with AI models like Gemini and Vertex AI, memory storages like AlloyDB and A2A TaskStore, and external tools through APIs.”
- AlloyDB works with Cloud Storage From the official documentation: “For example, if you frequently write data to AlloyDB from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your AlloyDB cluster in the `us-central1` region.”
- AlloyDB depends on Secret Manager From the official documentation: “AlloyDB stores and reads your Elasticsearch API key from Secret Manager.”
- AlloyDB works with Secret Manager From the official documentation: “AlloyDB stores and reads your OpenSearch credentials from Secret Manager.”
- AlloyDB works with VPC Service Controls From the official documentation: “This page provides an overview of VPC Service Controls, a Google Cloud feature that integrates with AlloyDB to secure data and resources.”
- VPC Service Controls secures AlloyDB From the official documentation: “VPC Service Controls helps mitigate the risk of data exfiltration from AlloyDB instances.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Vertex AI depends on Application Default Credentials From the official documentation: “To authenticate to Vertex AI, 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.”
- 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 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.”
- Application Default Credentials secures Vertex AI From the official documentation: “To authenticate to Vertex AI, set up Application Default Credentials.”
- Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- 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”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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.”
- 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 Vertex AI From the official documentation: “This page describes how to integrate Cloud SQL with [Vertex AI](/vertex-ai/docs).”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, 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.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
- 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.”
- Application Default Credentials works with Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- Cloud Run works with Workflows From the official documentation: “Route Workflows events to Cloud Run”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
- 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”
- 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 SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
- 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).”
- CMEK secures Cloud Storage From the official documentation: “Enable CMEK for Cloud Storage Buckets”
- customer-managed encryption keys secures Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
- Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
How learners score on this topic
Last updated