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
Spanner
Topic in 15 exam domains
Also called: managed Spanner, managed version of Spanner, Spanner production service
Google Cloud's fully managed relational database service.
Where this appears on the exam
11 objectives in 5 of 5 domains
~22% of exam
~25% of exam
Domain 3
Storing the data~20% of exam
~15% of exam
~18% of exam
Related topics
FoundationsThis topicWorks alongsideBuilds on theseBuilds on theseAppliedApplication Default CredentialsFeatureIdentity and Access ManagementServiceCloud SQLServiceDataflowServiceCloud Run functionsServiceFirestoreServiceBigQueryService
SpannerService
Pub/SubServiceCloud MonitoringServiceWorkflowsServiceEventarcServiceGoogle Cloud StorageServiceDatastreamServiceCloud Key Management ServiceServiceGoogleSQLFeaturepoint-in-time recoveryFeaturecustomer-managed encryption keysFeatureCloud StorageServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
- Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
- Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
- Cloud Run functions works with Spanner From the official documentation: “Using Spanner with Cloud Run functions (1st gen)”
- 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.”
- Datastream works with Spanner From the official documentation: “Learn how Datastream ingests data from [Spanner](/datastream/docs/sources-spanner).”
- Google Cloud Storage works with Spanner From the official documentation: “- Export any Spanner database into a Cloud Storage bucket using either Avro or CSV file formats.”
- Identity and Access Management secures Spanner From the official documentation: “Spanner uses Identity and Access Management (IAM) for authorization.”
- GoogleSQL is part of Spanner From the official documentation: “When creating a Spanner database, you can choose between two SQL dialects: GoogleSQL and PostgreSQL.”
- 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.”
- Cloud Key Management Service depends on Spanner From the official documentation: “Cloud KMS stores all of its data and metadata in Spanner databases which provide high data durability and availability with synchronous replication.”
- Cloud Key Management Service works with Spanner From the official documentation: “After the database is created, Spanner calls Cloud KMS about every five minutes to make sure that the key is still valid.”
- Cloud Key Management Service secures Spanner From the official documentation: “For Spanner databases in [custom, dual-region, or multi-region instance configurations](/spanner/docs/instance-configurations#configuration), you can use multiple regional (single-region) Cloud KMS keys to protect your database.”
- Cloud SQL is an alternative to Spanner 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.”
- Cloud Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
- customer-managed encryption keys secures Spanner From the official documentation: “To learn how to use manually-created CMEKs to protect your Spanner resources, see [Secure a database with CMEK](/spanner/docs/use-cmek).”
- GoogleSQL works with Spanner From the official documentation: “GoogleSQL is a query language used by multiple Google Cloud services, including Spanner and BigQuery.”
- Spanner depends on Identity and Access Management From the official documentation: “Spanner relies on IAM for identity management rather than managing user credentials within the database.”
- 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.”
- customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Dataflow depends on Application Default Credentials From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Firestore From the official documentation: “To authenticate to Firestore, set up Application Default Credentials.”
- Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, 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.”
- 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- BigQuery works with Datastream From the official documentation: “Permissions needed for datastream to write to BigQuery.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- 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.”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- 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.”
- Application Default Credentials works with Google Cloud Storage 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.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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:”
- Application Default Credentials works with Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- Cloud Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
- Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
- BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
- BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
- Cloud Run functions works with Cloud Storage From the official documentation: “Set up functions in response to events in Cloud Storage:”
- BigQuery works with Cloud Run functions From the official documentation: “BigQuery supports external function calls through Cloud Run functions.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- 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 Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- 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.”
How learners score on this topic
Last updated