Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are deploying a customer-facing web application on a VPC-native GKE cluster that uses container-native load balancing (NEGs) and also has a third-party Ingress controller installed. You must provision an external Application Load Balancer using the GKE Ingress controller with these requirements:
/healthz on Pod containerPort 9090, while the Service forwards application traffic to targetPort 8080.Which configuration should you deploy?
Ingress setting spec.ingressClassName: "gce" without the kubernetes.io/ingress.class annotation, and attach a FrontendConfig for the SSL policy and redirect settings. Annotate the Service to reference a single BackendConfig that enables Cloud Armor, IAP, Cloud CDN for edge caching, and a custom HTTP health check on port 9090 for /healthz.spec.ingressClassName and combined Cloud CDN/IAP settings doIn standard Kubernetes networking, spec.ingressClassName identifies which controller should reconcile an Ingress object. Separately, BackendConfig exposes configuration blocks for Google Cloud Armor, Identity-Aware Proxy (IAP), and Cloud CDN to control edge security, user authentication, and caching on GKE-provisioned backend services.
kubernetes.io/ingress.class is deprecated in upstream Kubernetes, the GKE Ingress controller relies exclusively on that annotation. When kubernetes.io/ingress.class is omitted and spec.ingressClassName is set to any value, the GKE Ingress controller takes no action, allowing a third-party controller to claim the Ingress or leaving no load balancer provisioned.BackendConfig creates an invalid configuration that breaks reconciliation or disables caching/authentication guarantees.kubernetes.io/ingress.class: "gce" for external load balancers or "gce-internal" for internal load balancers; any ingressClassName value is ignored when the annotation is set, and if the annotation is missing while ingressClassName is set, GKE skips the resource.(Service, port) pair can consume only one BackendConfig, and that BackendConfig cannot simultaneously enable IAP and Cloud CDN.The Ingress included the kubernetes.io/ingress.class: "gce" annotation, and the BackendConfig omitted Cloud CDN while keeping IAP, Cloud Armor, and the port 9090 health check.
Ingress annotated with kubernetes.io/ingress.class: "gce", then apply a GCPBackendPolicy for Cloud Armor and a HealthCheckPolicy targeting port 9090 on /healthz against the Service. Configure IAP, the SSL policy, and the HTTP-to-HTTPS redirect directly on the provisioned Compute Engine backend service and target proxy.GCPBackendPolicy, HealthCheckPolicy, and manual Compute Engine edits doGCPBackendPolicy and HealthCheckPolicy are custom resources defined under the networking.gke.io/v1 API group specifically for the GKE Gateway controller (Google's implementation of the Kubernetes Gateway API). Meanwhile, Compute Engine APIs (gcloud or console) directly expose underlying load balancer objects such as BackendService, TargetHttpsProxy, and UrlMap.
GCPBackendPolicy or HealthCheckPolicy. Applying those policies has no effect on a load balancer provisioned by a Kubernetes Ingress object.BackendConfig (cloud.google.com/v1) and FrontendConfig (networking.gke.io/v1beta1), whereas GKE Gateway uses GCPBackendPolicy, GCPGatewayPolicy, and HealthCheckPolicy (networking.gke.io/v1).spec.securityPolicy unset (null) in BackendConfig avoids overwriting a Compute Engine security policy, but other GKE-managed fields on backend services, target proxies, and URL maps are continuously reconciled by the Ingress controller.You migrated from GKE Ingress to the GKE Gateway API (deploying Gateway and HTTPRoute resources instead of Ingress) and used Gateway-native policies (GCPBackendPolicy, HealthCheckPolicy, and GCPGatewayPolicy) rather than manual Compute Engine modifications.
Ingress annotated with kubernetes.io/ingress.class: "gce" and networking.gke.io/v1beta1.FrontendConfig referencing a FrontendConfig with the SSL policy and redirect settings, and configure TLS using a pre-shared certificate, Google-managed certificate, or Kubernetes Secret. Annotate the Service with cloud.google.com/backend-config referencing a BackendConfig that specifies the Cloud Armor security policy, IAP settings without Cloud CDN, and an HTTP health check on port 9090 for /healthz.The GKE Ingress controller translates Kubernetes Ingress and Service objects into a Google Cloud classic Application Load Balancer with GCE_VM_IP_PORT Network Endpoint Groups (NEGs) for container-native load balancing. To configure advanced Google Cloud load balancer features declaratively, GKE uses two custom resource definitions (CRDs): FrontendConfig (attached to the Ingress) for frontend listener behavior and BackendConfig (attached to the Service) for backend service settings.
kubernetes.io/ingress.class: "gce" annotation instructs the built-in GKE Ingress controller to claim the resource and provision an external Application Load Balancer, ensuring the co-located third-party controller does not handle it.FrontendConfig via the networking.gke.io/v1beta1.FrontendConfig annotation on the external Ingress enforces the Google Cloud SSL policy and HTTP-to-HTTPS redirect, while pre-shared certificates, ManagedCertificate resources, or Kubernetes Secrets provide supported TLS termination.Service with cloud.google.com/backend-config binds a BackendConfig that attaches the Cloud Armor security policy and enables Identity-Aware Proxy (IAP) without enabling Cloud CDN (which is incompatible with IAP).9090 and path /healthz in BackendConfig allows probing containerPort 9090 even though the Service targetPort is 8080.FrontendConfig and BackendConfig policies across multiple Ingresses or Services.This configuration uses the exact annotations, CRDs, and certificate mechanisms supported by GKE Ingress while respecting platform constraints around IAP/Cloud CDN exclusivity and container-native NEG health checking.
Ingress annotated with kubernetes.io/ingress.class: "gce" and networking.gke.io/certmap referencing a Certificate Manager certificate map. Reference both the FrontendConfig and BackendConfig in the Service annotations, and configure the BackendConfig health check to probe the Service's nodePort on /healthz.nodePort health checks doThe networking.gke.io/certmap annotation binds a Certificate Manager certificate map to a load balancer frontend, while nodePort health checks instruct a Google Cloud load balancer to probe Kubernetes worker node VM IP addresses on an exposed NodePort.
networking.gke.io/certmap is a GKE Gateway API annotation). Ingress TLS requires Google-managed certificates (ManagedCertificate), pre-shared Compute Engine SSL certificates, or Kubernetes Secrets.FrontendConfig reference: FrontendConfig resources govern frontend load balancer attributes (SSL policies and HTTP-to-HTTPS redirects) and must be referenced on an external Ingress object via networking.gke.io/v1beta1.FrontendConfig, not on a Service object.nodePort applies to instance group backends, not container-native load balancing. Moreover, the requirement specifies probing Pod containerPort 9090 directly rather than the Service port.FrontendConfig attaches to Ingress (external only), while BackendConfig attaches to Service.GCE_VM_IP_PORT zonal NEGs), health check probe systems connect directly to Pod IP addresses on a specified containerPort, independent of the Service's targetPort or nodePort.The FrontendConfig and a supported Ingress certificate mechanism (such as a ManagedCertificate, pre-shared certificate, or Secret) were configured on the Ingress, and the BackendConfig on the Service probed Pod containerPort 9090.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated