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
Bigtable
Topic in 19 exam domains
Also called: Cloud Bigtable, Google Bigtable, Google Cloud Bigtable
Google Cloud's low-latency, high-throughput NoSQL database service.
Where this appears on the exam
13 objectives in 4 of 5 domains
~22% of exam
~25% of exam
Domain 3
Storing the data~20% of exam
~18% of exam
Related topics
FoundationsThis topicWorks alongsideAppliedIdentity and Access ManagementServiceApplication Default CredentialsFeaturecustomer-managed encryption keysFeatureCompute EngineServiceBigQueryServiceDataflowService
BigtableService
Pub/SubServiceSpannerServiceSecret ManagerServiceSecurity Command CenterServiceCloud StorageServiceGKEServiceCloud Asset InventoryServiceCloud LoggingServiceApache BeamConceptCloud KMS AutokeyFeatureBigtable backupsFeatureCloud RunServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Application Default Credentials works with Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Application Default Credentials secures Bigtable From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- Bigtable depends on Application Default Credentials From the official documentation: “To authenticate to Bigtable, set up Application Default Credentials.”
- BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
- customer-managed encryption keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
- Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
- Apache Beam works with Bigtable From the official documentation: “Write data to Cloud Bigtable with Apache Beam.”
- 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 Compute Engine From the official documentation: “The Compute Engine instances can connect to and manage the Bigtable instance.”
- Bigtable works with Dataflow From the official documentation: “The Dataflow job then writes the transformed data to your Bigtable table.”
- Bigtable works with Identity and Access Management From the official documentation: “Bigtable uses [Identity and Access Management (IAM)](/iam) for access control.”
- Bigtable works with Pub/Sub From the official documentation: “Bigtable supports ingestion from Pub/Sub subscriptions. You can configure a Pub/Sub subscription to send messages to a Bigtable table.”
- Bigtable works with Cloud Asset Inventory From the official documentation: “Cloud Asset Inventory, which provides inventory services based on a time series database, supports and returns Bigtable resources types.”
- Bigtable works with Cloud KMS Autokey From the official documentation: “Autokey creates a default key when you create Bigtable clusters.”
- 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 Run From the official documentation: “The Cloud Run service can perform administrative functions on the Bigtable instance.”
- 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 customer-managed encryption keys From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Bigtable.”
- Bigtable backups is part of Bigtable From the official documentation: “Bigtable provides two methods to cover common backup needs: [Bigtable backups](/bigtable/docs/backups) and managed data exports.”
- 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.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Security Command Center depends on Application Default Credentials From the official documentation: “To authenticate to Security Command Center, 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 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 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”
- 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.”
- Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, 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 Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- Application Default Credentials works with Dataflow From the official documentation: “To authenticate to Dataflow, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, 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.”
- Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, 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 Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- 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.”
- Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
- Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
- BigQuery works with Cloud Asset Inventory From the official documentation: “You can also use Cloud Asset Inventory to transfer this data into BigQuery.”
- Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
- 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.”
- Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- 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 Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
- Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
- BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
- Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- 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.”
- Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
How learners score on this topic
Last updated