You are developing a scalable web application for internal users. Your organization uses Google Workspace. You need to set up authentication to the application for the users, and then deploy the…

Question

Options

• ACreate a Compute Engine VM, configure a web server, and deploy the application in a VPC.
• BContainerize the application, and deploy it as a Cloud Run service.
• CConfigure Cloud SQL database with a table containing the users and password hashes. Add an
• DConfigure Identity Aware Proxy, and grant the roles/iap.httpsResourceAccessor IAM role to the
• EConfigure Identity Aware Proxy, and grant the roles/iap.tunnelResourceAccessor IAM role to the

• A
  11% (2)
• B
  53% (10)
• C
  32% (6)
• E
  5% (1)

Explanation

The question asks for a cloud-native deployment with minimal infrastructure management for Google Workspace users. Option B (Cloud Run) is correct because it is a fully managed, serverless container platform - no VMs or Kubernetes clusters to manage. Option D (Identity-Aware Proxy with roles/iap.httpsResourceAccessor) is correct because IAP integrates natively with Google Workspace identities to authenticate users via their Google accounts, with no custom auth code needed; the httpsResourceAccessor role grants access to HTTPS resources like web applications. Option A (Compute Engine VM) requires manual server management, contradicting the 'minimize infrastructure' goal. Option C (Cloud SQL password table) requires building custom authentication instead of leveraging the existing Google Workspace identity. Option E grants roles/iap.tunnelResourceAccessor, which is for SSH/TCP tunnel access (e.g., connecting to VMs), not for web application authentication.

No community discussion yet for this question.