You are developing a new ecommerce application that uses Cloud Run functions. You want to expose your application's APIs to public users while maintaining a high level of security. You need to…

Question

Options

• ADeploy your Cloud Functions behind Cloud Load Balancing, and use Cloud Armor to protect your
• BDeploy your Cloud Functions with Security Command Center enabled, and use IAM to manage
• CDeploy your Cloud Functions behind an Apigee proxy and use Apigee's authentication and
• DDeploy your Cloud Functions behind a Cloud API Gateway proxy. Create and use an API key to

• A
  7% (2)
• B
  13% (4)
• C
  57% (17)
• D
  23% (7)

Explanation

Apigee is Google Cloud's enterprise-grade API management platform and is the most scalable and secure option for exposing APIs publicly. It provides OAuth 2.0 / OpenID Connect authentication, JWT validation, API key management, rate limiting, threat protection, and analytics-all in one managed service. Deploying Cloud Functions behind an Apigee proxy means all traffic passes through a hardened API gateway that enforces auth policies before requests ever reach your backend. Option A (Cloud Armor) adds WAF/DDoS protection but not API-level authentication. Option B (Security Command Center + IAM) is for security posture management, not API gateway functionality. Option D (Cloud API Gateway + API key) offers only basic API key auth, which is far less secure and feature-rich than Apigee's full OAuth/JWT capabilities.

No community discussion yet for this question.