You are responsible for deploying a new API. That API will have three different URL paths: - https://yourcompany.com/students - https://yourcompany.com/teachers - https://yourcompany.com/classes You n

Question

Options

• ACreate one Cloud Function as a backend service exposed using an HTTPS load balancer.
• BCreate three Cloud Functions exposed directly.
• CCreate one Cloud Function exposed directly.
• DCreate three Cloud Functions as three backend services exposed using an HTTPS load balancer.

• A
  9% (4)
• B
  2% (1)
• C
  4% (2)
• D
  85% (40)

Explanation

An HTTPS load balancer with a URL map allows path-based routing rules (e.g., /students → function-A, /teachers → function-B, /classes → function-C) all under a single domain (yourcompany.com). Each Cloud Function is configured as a separate serverless NEG (Network Endpoint Group) backend service. This is the only option that keeps all three paths on one domain while dispatching to separate function implementations. Three directly-exposed Cloud Functions (B) each get their own unique Cloud Functions URL - you cannot make them appear under the same custom domain path without a load balancer. One function (A or C) would require internal routing logic inside a single function rather than true independent function separation, and cannot cleanly satisfy the path-to-function mapping requirement at the infrastructure level.

No community discussion yet for this question.