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 feature
BigQuery table snapshot
Topic in 1 exam domain
Also called: BigQuery table snapshots, table snapshot, table snapshots
A read-only copy that preserves the contents of a BigQuery table at a specific point in time, sharing unchanged storage blocks with the base table.
Where this appears on the exam
1 objective in 1 of 5 domains
Domain 3
Storing the data~20% of exam
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicApplication Default CredentialsFeatureIdentity and Access ManagementServiceSensitive Data ProtectionServiceCloud StorageServiceDatastreamServiceBigQueryServiceCloud SQLService
BigQuery table snapshotFeature
time travelFeatureauthorized viewsFeaturerow-level securityFeaturePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- BigQuery table snapshot is part of BigQuery From the official documentation: “BigQuery table snapshots”
- BigQuery table snapshot works with row-level security From the official documentation: “[Table snapshots](/bigquery/docs/table-snapshots-intro) support row-level security.”
- BigQuery table snapshot works with time travel From the official documentation: “You can take table snapshots and table clones using the BigQuery [time travel](/bigquery/docs/time-travel) feature (up to seven days in the past).”
- Identity and Access Management secures BigQuery table snapshot From the official documentation: “Access control for table snapshots is similar to access control for tables. For more information, see [Control access to resources with IAM](/bigquery/docs/control-access-to-resources-iam).”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Sensitive Data Protection depends on Application Default Credentials From the official documentation: “To authenticate to Sensitive Data Protection, 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.”
- BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
- 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.”
- BigQuery works with Datastream From the official documentation: “Permissions needed for datastream to write to BigQuery.”
- Application Default Credentials secures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- 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 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.”
- Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, 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 .”
- Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
- 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).”
- row-level security is part of BigQuery From the official documentation: “This document describes how to use row-level access security with other BigQuery features.”
- time travel is part of BigQuery From the official documentation: “BigQuery retains historical data for your tables for seven days. You can access a table's recent historical data by using the time travel feature.”
- Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- 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 Sensitive Data Protection From the official documentation: “Sensitive Data Protection starts identifying your Cloud SQL instances and creating a default connection for each instance.”
- 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.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
- authorized views is part of BigQuery From the official documentation: “In this tutorial, you create an authorized view in BigQuery that is used by your data analysts.”
- Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
- Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
- authorized views depends on Identity and Access Management From the official documentation: “To use authorized views, you need the following [IAM permissions](/resource-manager/docs/access-control-proj#permissions_and_roles):”
- authorized views is an alternative to row-level security From the official documentation: “Although authorized views are flexible and scalable, one of the following methods might better apply to your use case: - Set row-level policies on a table.”
- 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.”
- Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
- Identity and Access Management secures Datastream From the official documentation: “You can get and set permissions for Datastream using the Google Cloud Console, the IAM methods of the API, or the Google Cloud SDK.”
- row-level security is part of Cloud SQL From the official documentation: “In Cloud SQL, tables can have row-level security policies that restrict, on a per-user basis, which rows users can view by creating queries, or the rows that users can insert, update, or delete by running data modification commands.”
- Sensitive Data Protection secures BigQuery From the official documentation: “To help meet compliance requirements, use Sensitive Data Protection to inspect your BigQuery tables and to help protect your sensitive data.”
- Sensitive Data Protection depends on Identity and Access Management From the official documentation: “Sensitive Data Protection uses Identity and Access Management (IAM) to control access to resources.”
How learners score on this topic
Last updated