You need to containerize a web application that will be hosted on Google Cloud behind a global load balancer with SSL certificates. You don't have the time to develop authentication at the…

Question

Options

• AHost the application on Google Kubernetes Engine, and deploy an NGINX Ingress Controller to
• BHost the application on Google Kubernetes Engine, and deploy cert-manager to manage SSL
• CHost the application on Compute Engine, and configure Cloud Endpoints for your application.
• DHost the application on Google Kubernetes Engine, and use Identity-Aware Proxy (IAP) with

• A
  5% (1)
• B
  10% (2)
• C
  5% (1)
• D
  81% (17)

Explanation

The requirements are: containerized app, global load balancer, SSL offloading (managed), and authentication offloading (no time to build auth at the app level). Option D - GKE with Identity-Aware Proxy (IAP) - satisfies all: GKE hosts the containers, IAP is a Google-managed service that enforces identity-based authentication in front of the application (so no auth code is needed), and Cloud Load Balancing with Google-managed SSL certificates handles SSL termination. Option A (NGINX Ingress) requires manual certificate management, violating the 'managed services' requirement. Option B (cert-manager) automates certificate lifecycle but is not a fully managed Google service. Option C uses Compute Engine (not containerized) and Cloud Endpoints, which handles API management but not the same seamless IAP-level authentication offloading.

No community discussion yet for this question.