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
Autoclass
Topic in 4 exam domains
Also called: Autoclass feature
A Cloud Storage feature that automatically manages object storage classes.
Where this appears on the exam
3 objectives in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicApplication Default CredentialsFeatureCloud StorageServiceObject Lifecycle ManagementFeaturecustomer-managed encryption keysFeatureGoogle Cloud StorageServiceBigQueryServiceCloud SQLServiceDatastreamService
AutoclassFeature
Google SecOpsServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Autoclass is part of Cloud Storage From the official documentation: “This page shows you how to enable, disable, and check the status of the [Autoclass feature](/storage/docs/autoclass), which is set on a bucket in Cloud Storage.”
- Autoclass is part of Google Cloud Storage From the official documentation: “either select a **default storage class** for the bucket, or select **Autoclass** for automatic storage class management.”
- Autoclass is an alternative to Object Lifecycle Management From the official documentation: “To resolve this finding, use Object Lifecycle Management to delete noncurrent versions or move them to colder storage, or enable Autoclass to automatically manage storage classes based on access patterns.”
- 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.”
- 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.”
- Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
- 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.”
- Application Default Credentials works with Google Cloud Storage 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.”
- Google Cloud Storage works with Google SecOps From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
- BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
- 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 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 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.”
- 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.”
- BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
- Cloud SQL works with Google Cloud Storage From the official documentation: “Imports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage.”
- Google Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- 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.”
- Datastream works with Google Cloud Storage From the official documentation: “| How are files created in Cloud Storage? | Datastream creates a folder for each table.”
- Google SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
- Google SecOps depends on Google Cloud Storage From the official documentation: “This document explains how to ingest Desynova Contido logs to Google Security Operations using Google Cloud Storage V2.”
- 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).”
- Application Default Credentials secures Google Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- 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.”
- Cloud SQL works with customer-managed encryption keys From the official documentation: “To learn more about using customer-managed encryption keys with Cloud SQL, see [Overview of customer-managed encryption keys](/sql/docs/postgres/cmek).”
- Cloud SQL works with Google SecOps From the official documentation: “This document describes how fields of Cloud SQL context logs map to Google Security Operations Unified Data Model (UDM) fields.”
- 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 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.”
- customer-managed encryption keys secures Google Cloud Storage From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
- Object Lifecycle Management is part of Cloud Storage From the official documentation: “Ensure that lifecycle management of Cloud Storage is enabled and configured.”
How learners score on this topic
Last updated