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
Table
Topic in 2 exam domains
- Table · Concept
- table · Concept
- Table · Feature · Data Studio chart type
- table · Feature · gcloud output format
- TABLE · Concept
Also called: Bigtable tables, entity, org.apache.hadoop.hbase.client.Table, table (BigQuery resource), table-level, table-level resource
A structured data storage resource within BigQuery that can be configured with CMEK encryption.
Where this appears on the exam
2 subdomains in 2 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicWorks alongsideAppliedIAMServiceCloud KMSServicepartitioningFeatureCustomer-Managed Encryption KeysFeatureBigtableServiceCloud StorageServicePub/SubServiceCloud SQLServicedatasetConceptBigQueryServiceCloud RunServiceregionConceptclustered tablesFeatureBigQuery datasetConcept
TableConcept
Cloud Audit LogsFeatureML.GENERATE_TEXT functionFeatureKnowledge CatalogServiceschemaConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Customer-Managed Encryption Keys secures Table From the official documentation: “// createTableWithCMEK demonstrates creating a table protected with a customer managed encryption key.”
- Cloud Audit Logs works with Table From the official documentation: “Check Cloud Audit Logs for a `google.cloud.bigquery.v2.TableService.DeleteTable` event.”
- clustered tables configures Table From the official documentation: “If you often update rows where one or more columns fall within a narrow range of values, consider using [clustered tables](/bigquery/docs/clustered-tables).”
- IAM secures Table From the official documentation: “To control access to tables in BigQuery, see [Control access to resources with IAM](/bigquery/docs/control-access-to-resources-iam).”
- ML.GENERATE_TEXT function works with Table From the official documentation: “To minimize Agent Platform charges, write query results to a table and then reference that table in the `ML.GENERATE_TEXT` function.”
- partitioning configures Table From the official documentation: “If updates or deletions generally happen on older data, or within a particular range of dates, consider [partitioning](/bigquery/docs/partitioned-tables) your tables.”
- schema is part of Table From the official documentation: “- To specify a schema when you create a table, call the [`tables.insert`](/bigquery/docs/reference/rest/v2/tables/insert) method and configure the [`schema`](/bigquery/docs/reference/rest/v2/tables#Table.FIELDS.schema) property in the…”
- Table is part of BigQuery From the official documentation: “This document describes the table layout, columns, event types, user identity fields, and JSON payload structure for conversational analytics conversation logging in BigQuery.”
- Table is part of BigQuery dataset From the official documentation: “Delete a table from a dataset.”
- Table is part of Bigtable From the official documentation: “Bigtable stores data in *tables*, which contain *rows*.”
- Table is part of dataset From the official documentation: “The table or view also inherits access controls specified at the dataset level and higher.”
- Table depends on region From the official documentation: “The model and input table must be in the same region.”
- 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: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
- Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
- 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.”
- Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
- BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
- Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
- Customer-Managed Encryption Keys depends on Cloud KMS From the official documentation: “You must have a symmetric encryption key in Cloud KMS to use for CMEK.”
- BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
- BigQuery dataset is part of BigQuery From the official documentation: “Sample demonstrating how to create a dataset in BigQuery.”
- Cloud KMS works with Customer-Managed Encryption Keys From the official documentation: “With customer-managed encryption keys (CMEK), volume keys are wrapped using your keys stored in Cloud KMS.”
- Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- Cloud Storage 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 Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
- Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
- 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 Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
- BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
- 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 works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
- 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.”
- Cloud SQL configures region From the official documentation: “When you create a Cloud SQL instance, you choose a [region](/docs/geography-and-regions) where the instance and its data are stored.”
- 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.”
- IAM secures BigQuery From the official documentation: “BigQuery uses IAM to manage access to resources.”
- BigQuery works with Cloud KMS From the official documentation: “BigQuery stores the name of the key used to encrypt the table content and uses that key when a table protected by Cloud KMS is queried.”
- 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.”
- Cloud Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
- Cloud KMS secures BigQuery From the official documentation: “If reading from BigQuery using query source, use this Cloud KMS key to encrypt any temporary tables created.”
- Cloud KMS works with Pub/Sub From the official documentation: “This page shows you how to use [Pub/Sub](/pubsub) to create notifications on state changes for Cloud KMS resources.”
- Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
- Cloud SQL depends on Cloud KMS From the official documentation: “Cloud SQL administrator operations, such as create, clone, or update, might fail due to Cloud KMS errors, and missing roles or permissions.”
- Cloud Storage works with Knowledge Catalog From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
- clustered tables is part of BigQuery From the official documentation: “BigQuery supports clustering for both partitioned and non-partitioned tables.”
- Customer-Managed Encryption Keys is part of Cloud KMS 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 Dataflow.”
- Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
- Customer-Managed Encryption Keys secures dataset From the official documentation: “For **datasets**, when a user imports data into dataset, the data items and annotations are CMEK-encrypted.”
- Knowledge Catalog works with Pub/Sub From the official documentation: “Knowledge Catalog is an intelligent governance solution for data and AI assets in Google Cloud. It provides a centralized inventory where you can discover, manage, and govern your data across Google Cloud data sources like BigQuery, Cloud Storage, Pub/Sub, and Spanner.”
- BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
- BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
- BigQuery dataset works with Cloud Run From the official documentation: “The Cloud Run service can interact with the BigQuery dataset.”
- BigQuery dataset works with Knowledge Catalog From the official documentation: “If Knowledge Catalog needs to access resources in other projects (for example, Cloud Storage buckets or BigQuery datasets that you want to attach as assets or scan for data profiles), you must grant this service agent the required permissions in the projects containing those…”
- BigQuery dataset works with Pub/Sub From the official documentation: “The Pub/Sub subscription can write messages to the BigQuery dataset.”
- BigQuery dataset is part of region From the official documentation: “BigQuery considers datasets, column policies, and slot commitments to be regional resources. Slots can only access datasets in the local region, and column policies can only be applied to tables within local datasets.”
- Bigtable is an alternative to Cloud SQL 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.”
- Bigtable works with Cloud Storage From the official documentation: “For example, if you frequently write data to Bigtable from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your Bigtable cluster in a zone within `us-central1`.”
How learners score on this topic
Last updated