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
load balancer
Topic in 1 exam domain
- load balancer · Concept
- Load Balancer · Service · Compute Engine
- load balancer · Service
- load balancer · Feature
- Load balancer · Concept
- Load Balancer · Concept · service load balancing for DBCluster
Also called: another load balancer, Compute Engine Load Balancer, Compute Engine load balancers, load balancer URL, load balancer with a Cloud Run backend, load balancer's, load balancers
The load balancing system comprising frontend components, proxies, URL maps, and backends.
Where this appears on the exam
1 subdomain in 1 of 5 domains
~25% of exam
Related topics
FoundationsBuilding blocksBuilding blocksBuilding blocksBuilding blocksThis topicWorks alongsideCloud Load BalancingServiceIdentity and Access ManagementServiceIdentity-Aware ProxyServiceBigQueryServiceservice accountConceptCloud RunServiceCompute EngineServiceGKEServiceCloud SQLServicemanaged instance groupFeature
load balancerConcept
failoverConceptswitchoverConceptLookerServiceCloud MonitoringServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- load balancer is part of Cloud SQL From the official documentation: “Each Cloud SQL instance consists of a forwarding rule and a load balancer.”
- failover works with load balancer From the official documentation: “Another important mechanism that aids smoother switchover and failover procedures is the presence of a load balancer.”
- load balancer works with switchover From the official documentation: “Another important mechanism that aids smoother switchover and failover procedures is the presence of a load balancer.”
- Cloud Load Balancing configures load balancer From the official documentation: “You use [Cloud Load Balancing](/load-balancing/docs/load-balancing-overview) to create a load balancer that uses the `asm-ingressgateway` Services in both clusters as backends.”
- Cloud Run works with load balancer From the official documentation: “It configures the load balancer to connect to the Cloud Run service.”
- Identity-Aware Proxy works with load balancer From the official documentation: “Identity-Aware Proxy is enabled on a load balancer, and will support *at most* the location capabilities of the chosen load balancer.”
- load balancer works with Looker From the official documentation: “From a high level, the load balancer would be configured to listen on port 443 and forward all requests to Looker on port 9999.”
- load balancer works with managed instance group From the official documentation: “Abandoning an instance from a group also removes the instance from [load balancers](/compute/docs/load-balancing) that were assigned to the managed instance group.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- BigQuery works with Looker From the official documentation: “Connect Looker to the BigQuery project.”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
- Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
- Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
- Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
- Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
- Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
- GKE works with Identity-Aware Proxy From the official documentation: “If you are running GKE version 1.24 or later, you can configure IAP and GKE by using the Kubernetes Gateway API.”
- Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
- Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management works with Identity-Aware Proxy From the official documentation: “IAP re-checks Identity and Access Management (IAM) authorization for all requests during valid sessions.”
- service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
- BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
- Cloud Load Balancing works with Cloud Run From the official documentation: “If you are using Cloud Load Balancing with Cloud Run, configure custom error responses at the load balancer level.”
- Cloud Load Balancing works with managed instance group From the official documentation: “It configures the load balancer to connect to the instance group.”
- Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of 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 Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
- Compute Engine works with Identity-Aware Proxy From the official documentation: “Set up a Compute Engine instance with IAP.”
- Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
- Identity-Aware Proxy works with service account From the official documentation: “Authenticate a service account to access resources secured by IAP.”
- managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
- 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 Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
- BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
- BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
- Cloud Load Balancing works with Cloud Monitoring From the official documentation: “Key performance and health metrics reported by Cloud Monitoring for Cloud Load Balancing resources.”
- Cloud Load Balancing works with GKE From the official documentation: “GKE and GKE Enterprise network controllers also support the deployment of Cloud Load Balancing for built-in integration with container networking.”
- Cloud Load Balancing works with Identity and Access Management From the official documentation: “Cloud Load Balancing caches IAM permissions for five minutes, so it takes up to five minutes for a role change to become effective.”
- Cloud Load Balancing works with Identity-Aware Proxy From the official documentation: “IAP also supports and seamlessly integrates with Cloud Load Balancing, making it the most efficient security management option for this tutorial.”
- 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 Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
- Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
- Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
- Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
- Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
- Cloud SQL works with Looker From the official documentation: “To get started, see [Use Looker with Cloud SQL](/sql/docs/sqlserver/looker).”
- Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
- GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
- 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.”
- Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
- Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
- Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”
- Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
- Identity-Aware Proxy secures GKE From the official documentation: “Securing Google Kubernetes Engine apps Enable IAP for GKE apps.”
- service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
- service account secures Cloud SQL From the official documentation: “Cloud SQL uses service accounts for authentication between Cloud SQL and other Google Cloud products.”
How learners score on this topic
Last updated