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
Object Versioning
Topic in 1 exam domain
- Object Versioning · Feature
- object versioning · Feature · Cloud Storage bucket capability
A feature in Cloud Storage that maintains multiple versions of an object in a bucket.
Where this appears on the exam
1 subdomain in 1 of 5 domains
Domain 3
Storing the data~20% of exam
Related topics
FoundationsBuilding blocksBuilding blocksThis topicBuilds on theseAppliedObject Lifecycle ManagementFeaturestorage classConceptCloud StorageService
Object VersioningFeature
Customer-Managed Encryption KeysFeatureCloud Storage bucketConceptBigQueryServiceCloud SQLServiceStorage Transfer ServiceServiceDataflowServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Object Lifecycle Management works with Object Versioning From the official documentation: “If you also have Object Versioning enabled on your bucket, deleted live objects become noncurrent and deleted noncurrent objects become soft-deleted.”
- Object Versioning is part of Cloud Storage From the official documentation: “Require Object Versioning for Cloud Storage Buckets”
- Object Versioning configures Cloud Storage bucket From the official documentation: “To keep the history of your deployments, enable [Object Versioning](/storage/docs/object-versioning):”
- 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”
- Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
- 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.”
- 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.”
- BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
- Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
- Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
- Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- 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.”
- Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
- 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).)”
- Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
- Storage Transfer Service depends on Cloud Storage From the official documentation: “Storage Transfer Service requires access to Cloud Storage buckets in order to move data into or between Cloud Storage buckets.”
- 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 works with Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
- BigQuery works with Storage Transfer Service From the official documentation: “If needed, you can load the full record of all transfer errors to BigQuery to check on files or evaluate errors that remained even after retries.”
- 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 Cloud Storage bucket From the official documentation: “If you exported into a Cloud Storage bucket, you can also check the log file created by Cloud SQL in the bucket for information about export status.”
- Cloud SQL works with Dataflow From the official documentation: “Use Datastream to replicate changes from your MySQL instance to either BigQuery or Cloud Storage, and then use Dataflow or Managed Service for Apache Spark to bring the data into your Cloud SQL instance.”
- Cloud Storage depends on storage class From the official documentation: “- The monthly availability of data stored in Cloud Storage depends on the storage class of the data and the location type of the bucket.”
- Cloud Storage bucket works with Dataflow From the official documentation: “Begin by creating a Cloud Storage bucket using Google Cloud CLI. This bucket is used as a temporary storage location by the Dataflow pipeline.”
- Cloud Storage bucket works with Storage Transfer Service From the official documentation: “You can use [Storage Transfer Service](/storage-transfer/docs/create-transfers) to transfer data between zonal buckets and other Cloud Storage buckets.”
- 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 configures Cloud Storage bucket From the official documentation: “If you want your data to remain encrypted with a customer-managed key during an export or import, you must set a customer-managed encryption key on the Cloud Storage bucket before exporting data to it.”
- Customer-Managed Encryption Keys works with Dataflow From the official documentation: “This sample shows how to use encryption keys managed by the customer, with a Dataflow pipeline.”
- Customer-Managed Encryption Keys secures Dataflow From the official documentation: “You can either create CMEKs manually to protect your Dataflow resources or use Cloud KMS Autokey.”
- Dataflow depends on Cloud Storage bucket From the official documentation: “Create a Cloud Storage bucket by using the gcloud CLI. This bucket is used as a temporary storage location by the Dataflow pipeline.”
- Object Lifecycle Management is part of Cloud Storage From the official documentation: “Ensure that lifecycle management of Cloud Storage is enabled and configured.”
- Object Lifecycle Management configures Cloud Storage bucket From the official documentation: “Enabling object versioning increases [storage costs](https://cloud.google.com/storage/pricing), which you can mitigate by configuring [Object Lifecycle Management](/storage/docs/lifecycle) to delete old state versions.”
- Object Lifecycle Management configures storage class From the official documentation: “You can change the storage class of an existing object either by [rewriting the object](/storage/docs/changing-storage-classes) or by using [Object Lifecycle Management](/storage/docs/lifecycle).”
- storage class configures Cloud Storage bucket From the official documentation: “Create a Cloud Storage bucket with storage class and location parameters.”
- Storage Transfer Service depends on Cloud Storage bucket From the official documentation: “The service agent running the transfer must have `storage.objects.get` permission for the bucket containing the manifest.”
How learners score on this topic
Last updated