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
dataset
Topic in 1 exam domain
- dataset · Concept
- Dataset · Concept
- dataset · Feature · Cloud Healthcare API
Also called: AdaptiveMtDataset, Cloud Healthcare API dataset, Cloud Healthcare API datasets, dataset level, dataset-level, datasets, Healthcare Datasets, labeled dataset, parent dataset, primary dataset, underlying dataset, unstructured dataset
A top-level container within the Cloud Healthcare API that holds data stores.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicAppliedBigQuery dataset replicationFeatureIdentity and Access ManagementServiceCloud KMSServiceCloud Key Management ServiceServiceCustomer-Managed Encryption KeysFeatureCloud StorageServiceDatastreamServicePub/SubServiceCloud SQLServiceCloud Audit LogsFeatureBigQueryService
datasetConcept
tableConceptPoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- 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.”
- BigQuery dataset replication configures dataset From the official documentation: “With BigQuery dataset replication, you can set up automatic replication of a dataset between two different regions or multi-regions.”
- Cloud Audit Logs works with dataset From the official documentation: “Check whether the table or dataset expired or was deleted by querying [`INFORMATION_SCHEMA.TABLE_STORAGE`](/bigquery/docs/information-schema-table-storage) or inspecting Cloud Audit Logs for `DeleteTable` or `InternalTableExpired` events.”
- dataset is part of BigQuery From the official documentation: “Create a BigQuery dataset to store your models and sample data:”
- Identity and Access Management secures dataset From the official documentation: “IAM lets you control who has access to your datasets and data stores.”
- table is part of dataset From the official documentation: “The table or view also inherits access controls specified at the dataset level and higher.”
- 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”
- Customer-Managed Encryption Keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Datastream From the official documentation: “Datastream supports three types of partitioning for BigQuery tables:”
- 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 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 Storage works with Datastream From the official documentation: “Because Cloud Storage is in the same network as Datastream, no special connectivity is required.”
- 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”
- 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.”
- 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.”
- Customer-Managed Encryption Keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
- Cloud Audit Logs works with Cloud Key Management Service From the official documentation: “Cloud Audit Logs for Cloud KMS in the Activity stream read like generic logs, and are not easily read by a human.”
- 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 works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
- 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.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- 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.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- 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 Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
- 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 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 SQL works with Datastream From the official documentation: “The change data capture pipeline uses VPC peering to establish a connection between Datastream and private IP Cloud SQL.”
- 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 table From the official documentation: “// createTableWithCMEK demonstrates creating a table protected with a customer managed encryption key.”
- 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 Audit Logs secures BigQuery From the official documentation: “For BigQuery, [Cloud Audit Logs](/logging/docs/audit) is used for both data access logs and audit logs, which are enabled by default.”
- Cloud Audit Logs works with Cloud KMS From the official documentation: “To access the justification, you first need to enable Cloud Audit Logs with Cloud KMS on the project containing the key used for encryption.”
- Cloud Audit Logs is part of Cloud SQL From the official documentation: “Cloud Audit Logs for Cloud SQL let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
- Cloud Audit Logs works with Datastream From the official documentation: “Cloud Audit Logs for Datastream let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
- Cloud Audit Logs works with table From the official documentation: “Check Cloud Audit Logs for a `google.cloud.bigquery.v2.TableService.DeleteTable` event.”
- Cloud Key Management Service is an alternative to Customer-Managed Encryption Keys From the official documentation: “Unless your control package mandates a certain encryption key strategy, you can use any Google key management service, including Cloud Key Management Service, Cloud External Key Manager, or CMEK.”
- Cloud Key Management Service depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
- Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
- 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.”
- 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 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).”
- Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
- Customer-Managed Encryption Keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
- Customer-Managed Encryption Keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
- Customer-Managed Encryption Keys works with Datastream 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 Datastream.”
- Customer-Managed Encryption Keys secures Datastream From the official documentation: “The CMEK feature lets you use your own cryptographic keys for data at rest in Datastream.”
- Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
How learners score on this topic
Last updated