Exam Professional Cloud Developer topic 1 question 212 discussion

Option D is correct. You need loadbalancer and dns to name your 3 services (yourcompany.com/path). without it, if you select answer B, you will have cloudFunctionName-1/path, cloudFunctionName-2/path, cloudFunctionName-3/path. Its ruined user experience.

There's no purpose for a Load Balancer here as you are not balancing traffic across multiple backend server instances. You need 3 different Cloud Functions each with their own Endpoint that's all. See this example: https://cloud.google.com/functions/docs/create-deploy-gcloud-1st-gen

option D. When users query "yourcompany.com," they receive an IP address and access the load balancer. Consequently, the load balancer then executes path-based routing. B is Wrong. It is not possible to deploy three cloud functions with the same domain name.

i go for B because i don't understand the necessity of LB in this case

I go with B. Exposed using an HTTPS load balancer is not required. Those three are different end points of the service. We no need to setup load balancer in case of Cloud functions, it is serverless.

D. The differences between B and D are: 1. Cost: 3 Cloud Function exposed directly (B) will create 3 endpoints / load balancers, whereas D only exposed one load balancer. 2. Scalability: exposing directly with endpoint or instance itself would cause scalability problem - can't upscale the endpoint instance fast enough. 3. Handling service-to-service call: In B, all services rely on external DNS resolution, which is slower. In D, it has chance that cross-service call can be resolved internally.

Option B (Create three Cloud Functions exposed directly) is the best choice in this scenario, as it allows you to create a separate Cloud Function for each API URL path and configure each one to invoke a different function in your code. Option A (Create one Cloud Function as a backend service exposed using an HTTPS load balancer) and Option D (Create three Cloud Functions as three backend services exposed using an HTTPS load balancer) both involve using an HTTPS load balancer, which adds additional complexity and configuration overhead. These options may be appropriate for more complex scenarios, but in this case, they are not necessary. Option C (Create one Cloud Function exposed directly) would require all three API URL paths to invoke the same function in your code, which does not meet the requirement of invoking different functions for each URL path.

i choose D

Each function is defined as an HTTP trigger, which allows it to be triggered by incoming HTTP requests. The endpoint for each function is defined in the function name (e.g. "students", "teachers", "classes"). This means that the APIs would be accessible at the following endpoints: • https://yourcompany.com/students • https://yourcompany.com/teachers • https://yourcompany.com/classes Note that you would need to configure "yourcompany.com" DNS registry. In this case, option B, "Create three Cloud Functions exposed directly", would be correct.

Why there is the need of LB?

option D

D is the answer.

D is correct