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
Committed Use Discounts
Topic in 4 exam domains
- Committed Use Discounts · Feature · Compute Engine
- Committed use discounts · Feature
- Committed use discounts · Concept
- committed use discounts · Concept · Google Cloud billing
- committed use discounts · Feature
- committed-use discounts · Feature · Google Cloud billing feature
Also called: AlloyDB CUDs, Backup for GKE CUDs, Bigtable CUDs, Bigtable spend-based CUDs, Cloud SQL committed use discounts, Cloud SQL CUDs, Datastore mode CUDs, Firestore CUDs, NetApp Volumes CUDs, Spanner CUDs, Spanner spend-based CUDs, spend-based committed use discount, VMware Engine committed use discounts, VMware Engine CUDs
Discounted billing arrangements that can be applied to compute resource usage.
Where this appears on the exam
2 objectives in 1 of 5 domains
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksThis topicWorks alongsideBackup and DRServiceCloud BillingServiceIdentity and Access ManagementServiceMemorystore for ValkeyServiceCompute EngineServiceCloud StorageServiceFirestoreServiceMemorystore for RedisServicecustomer-managed encryption keysFeatureCloud SQLServiceCloud LoggingService
Committed Use DiscountsFeature
Cloud SQL Enterprise Plus editionFeatureBigQueryServiceAlloyDB for PostgreSQLServiceCloud RunServiceCloud MonitoringServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- AlloyDB for PostgreSQL works with Committed Use Discounts From the official documentation: “This page describes how committed use discounts (CUDs) work with AlloyDB for PostgreSQL.”
- Backup and DR works with Committed Use Discounts From the official documentation: “This page describes how committed use discounts work with Backup and DR for Oracle databases.”
- Cloud Run works with Committed Use Discounts From the official documentation: “Committed use discounts (CUDs) provide discounted prices in exchange for committing to continuously using Cloud Run for a specified period of time.”
- Cloud SQL Enterprise Plus edition works with Committed Use Discounts From the official documentation: “Cloud SQL CUDs automatically apply to both [Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition](/sql/docs/mysql/editions-intro) instances within the same region.”
- Committed Use Discounts depends on Cloud Billing From the official documentation: “You can purchase CUDs from any Cloud Billing account, and the discount applies to any eligible usage in projects that the Cloud Billing account pays for.”
- Committed Use Discounts is part of Cloud SQL From the official documentation: “*Committed use discounts (CUDs)* for Cloud SQL provide deeply discounted prices in exchange for your commitment to continuously use database instances in a particular region for a one- or three-year term.”
- Committed Use Discounts is part of Compute Engine From the official documentation: “For predictable workloads, Compute Engine provides committed use discounts (CUDs) that help to reduce the cost of your infrastructure by committing to a contract in return for heavily discounted VM usage prices.”
- Committed Use Discounts is part of Firestore From the official documentation: “Firestore offers two levels of discounts, depending on the commitment period:”
- Committed Use Discounts works with Memorystore for Redis From the official documentation: “The discount applies to any eligible usage of Memorystore for Valkey, Memorystore for Redis Cluster, Memorystore for Redis, or Memorystore for Memcached instances associated with the Cloud Billing account used to purchase the CUD, with the exception of Memorystore for Redis M1…”
- Committed Use Discounts is part of Memorystore for Valkey From the official documentation: “Committed use discounts (CUDs) for Memorystore for Valkey provide discounted prices in exchange for your commitment to continuously spend a minimum hourly amount on Memorystore for Valkey capacity for a year or longer.”
- 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 Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
- Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
- 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.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
- Cloud SQL Enterprise Plus edition is part of Cloud SQL From the official documentation: “For Cloud SQL Enterprise Plus edition instances:”
- BigQuery works with Cloud Billing From the official documentation: “To export Cloud Billing data to BigQuery, take the following steps:”
- Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
- Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- 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.”
- Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- 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”
- Identity and Access Management secures Firestore From the official documentation: “This page describes the IAM permissions and roles for Firestore.”
- Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
- 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).”
- Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
- Cloud Monitoring works with Memorystore for Valkey From the official documentation: “This section lists and describes Cloud Monitoring metrics that are available for Memorystore for Valkey.”
- 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.”
- AlloyDB for PostgreSQL works with BigQuery From the official documentation: “BigQuery AlloyDB federation lets BigQuery query data residing in AlloyDB in real time without copying or moving the data.”
- AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB supports importing and exporting compressed `.gz` files from Cloud Storage.”
- Backup and DR works with Compute Engine From the official documentation: “This page details how to use Backup and DR to back up the disks of a Compute Engine instance.”
- BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
- Cloud Run works with Firestore From the official documentation: “The Cloud Run app stores the result in Firestore.”
- Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
- Identity and Access Management secures Memorystore for Redis From the official documentation: “Management of Memorystore for Redis instances is secured using Identity and Access Management (IAM) role-based access control.”
- AlloyDB for PostgreSQL works with Cloud Run From the official documentation: “The Cloud Run service can connect to the AlloyDB instance.”
- AlloyDB for PostgreSQL is an alternative to Cloud SQL From the official documentation: “The sample code uses Cloud SQL as the vector database, whereas this reference architecture uses AlloyDB for PostgreSQL.”
- Backup and DR works with Cloud SQL From the official documentation: “Enable the Backup and DR API where the Cloud SQL instances are located.”
- Backup and DR works with Cloud Storage From the official documentation: “A storage pool, which associates a Cloud Storage bucket with Backup and DR,<br>was removed from the Backup and DR management console.”
- Backup and DR secures Compute Engine From the official documentation: “Backup and DR ensures that the chosen Compute Engine instances get backed up per the frequency set in the backup policy.”
- 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 works with Firestore From the official documentation: “You can load data from a Firestore with MongoDB compatibility export into BigQuery, but only if you specified a `collection-ids` filter.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
- Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
- Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
- Cloud Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
- Cloud SQL is an alternative to Firestore From the official documentation: “Check your application code for reliance on local filesystems, and replace it with file storage on [Cloud Storage](/storage) or data storage such as [Firestore](/firestore) or [Cloud SQL](/sql).”
- customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
- 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.”
How learners score on this topic
Last updated