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 service
Application Load Balancer
Topic in 1 exam domain
- Application Load Balancer · Service
- Application Load Balancer · Feature
- application load balancer · Feature · Google Cloud load balancer
- Application Load Balancer · Concept
Also called: ALB, Application Load Balancers, external Application Load Balancers, external regional application load balancer, global HTTPS load balancer, Google Cloud application load balancer, HTTPS Application Load Balancer, internal application load balancer (HTTPS), Layer 7 Application Load Balancer, Layer 7 external and internal Application Load Balancers with HTTP or HTTPS traffic, regional Application Load Balancer, regional Google Cloud Application Load Balancer (HTTPS)
A Google Cloud load balancing component that can be targeted in fault injection testing to simulate traffic degradation and approximate zone or region failures.
Where this appears on the exam
1 subdomain in 1 of 5 domains
~25% of exam
Related topics
FoundationsThis topicWorks alongsideBuilds on theseAppliedCloud Load BalancingServiceCloud LoggingServiceApplication Default CredentialsFeatureIdentity and Access ManagementService
Application Load BalancerService
Cloud MonitoringServiceBigQueryServiceCompute EngineServiceCloud StorageServiceCloud ComposerServicePrivate Service ConnectFeatureCloud SQLServiceIdentity-Aware ProxyServiceGKEServiceManaged Service for Apache SparkServiceCloud RunServicePoints to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
- Application Load Balancer is part of Cloud Load Balancing From the official documentation: “To see an overview of all the Cloud Load Balancing products available, see [Cloud Load Balancing overview](/load-balancing/docs/load-balancing-overview). To determine which Cloud Load Balancing product to use, you must first determine the traffic type that your load balancers…”
- Application Load Balancer works with Cloud Logging From the official documentation: “Application Load Balancers provide detailed logging capabilities that allow you to monitor server certificate validation, identify potential issues, and troubleshoot connection problems. This section outlines the different types of errors that can occur during mTLS validation…”
- Application Load Balancer works with Cloud Monitoring From the official documentation: “Application Load Balancers export monitoring data to [Cloud Monitoring](/monitoring/docs).”
- Application Load Balancer works with Cloud Run From the official documentation: “This page shows you how to deploy a regional external Application Load Balancer with a Cloud Run backend.”
- Application Load Balancer works with Cloud Storage From the official documentation: “The Application Load Balancer distributes HTTP and HTTPS traffic to backends hosted on a variety of Google Cloud platforms—such as Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud Run—as well as external backends connected over the internet or by using…”
- Application Load Balancer works with Compute Engine From the official documentation: “The Application Load Balancer distributes HTTP and HTTPS traffic to backends hosted on a variety of Google Cloud platforms—such as Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud Run—as well as external backends connected over the internet or by using…”
- Application Load Balancer works with GKE From the official documentation: “In this model, the Google external Application Load Balancer provides global load balancing across GKE clusters that have Cloud Service Mesh meshes in distinct clusters.”
- Application Load Balancer works with Identity-Aware Proxy From the official documentation: “For proxy load balancers such as the internal and external Application Load Balancers, we recommend that you use Identity-Aware Proxy (IAP) as your authentication method instead.”
- Application Load Balancer configures Identity-Aware Proxy From the official documentation: “- **An Application Load Balancer:** This load balancer will handle all ingress HTTP traffic using a Private Service Connect (PSC) endpoint and lets you configure IAP.”
- Application Load Balancer works with Private Service Connect From the official documentation: “- **An Application Load Balancer:** This load balancer will handle all ingress HTTP traffic using a Private Service Connect (PSC) endpoint and lets you configure IAP.”
- 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”
- Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
- BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
- 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.”
- Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
- Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
- Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
- Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
- Cloud SQL works with Private Service Connect From the official documentation: “`--psc` Connect to the Cloud SQL instance using Private Service Connect.”
- BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
- 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.”
- Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
- 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.”
- Application Default Credentials secures Managed Service for Apache Spark From the official documentation: “To authenticate to Managed Service for Apache Spark, set up Application Default Credentials.”
- Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
- Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
- 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 Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
- Cloud Storage works with Managed Service for Apache Spark From the official documentation: “Managed Service for Apache Spark accesses these files on Cloud Storage.”
- 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.”
- Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
- Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
- 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 Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
- 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:”
- Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
- Compute Engine works with Managed Service for Apache Spark From the official documentation: “Google Compute Engine provides a runtime environment for all features provided by Managed Service for Apache Spark and Gemini Enterprise Agent Platform.”
- GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
- Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
- 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.”
- Managed Service for Apache Spark depends on Cloud Storage From the official documentation: “Managed Service for Apache Spark uses Cloud Storage as its default distributed file system.”
- Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, 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 works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
- Application Default Credentials works with Managed Service for Apache Spark From the official documentation: “To authenticate to Managed Service for Apache Spark, set up Application Default Credentials.”
- 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.”
- BigQuery works with Managed Service for Apache Spark From the official documentation: “This means you can quickly read and write BigQuery data to and from Managed Service for Apache Spark.”
- BigQuery works with Private Service Connect From the official documentation: “Click the private zone that contains the DNS records for the Private Service Connect endpoints, which you created to allow BigQuery Toolkit for SAP to privately connect to the BigQuery and IAM APIs.”
How learners score on this topic
Last updated