Google Professional Cloud Developer Question 331
Select 2Google Cloud PlatformYou are developing a REST API service and want to deploy it to a serverless environment using Google Cloud Functions. The API requires a custom domain, minimal scaling delay, and the ability to handle a high volume of traffic spikes. Which of the following considerations should you account for when deploying the application?
- A
Ensure your function is set to use a specific runtime that supports HTTP triggers.
- B
Configure a custom domain through Cloud Run, as Google Cloud Functions does not support custom domains directly.
- C
Use a global load balancer to manage traffic distribution for high availability.
- D
Optimize your function's cold start time by using a region close to your users.
- E
Enable the scaling concurrency setting to allow multiple requests to be processed simultaneously by a single function instance.
Show answer and explanation
Correct answers: A, D
Explanation
When deploying a REST API to Google Cloud Functions, it is important to consider runtime compatibility with HTTP triggers and optimize the function's location to reduce cold start latency. While Google Cloud Functions inherently handles traffic distribution and scalability, setting up a global load balancer or enabling concurrency is not applicable in this context. Similarly, while custom domains are supported, they do not require Cloud Run for this specific use case.
- A. Correct.
Correct. When deploying a REST API service on Google Cloud Functions, you must ensure that the runtime you select supports HTTP triggers for handling API requests.
- B. Incorrect.
Incorrect. Google Cloud Functions can use custom domains by integrating them with Firebase Hosting or other similar tools. Cloud Run is a different serverless environment and not required for this scenario.
- C. Incorrect.
Incorrect. A global load balancer is not necessary for Google Cloud Functions, as it inherently handles traffic distribution and scalability.
- D. Correct.
Correct. Deploying a function in a region close to your users reduces latency and improves performance, especially during cold starts.
- E. Incorrect.
Incorrect. Google Cloud Functions does not allow concurrency per instance. Each function instance handles one request at a time, so this option is not applicable.