HTTP triggered functions in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an HTTP triggered function in cloud computing?

An HTTP triggered function is a small piece of code that runs in the cloud when it receives an HTTP request, like when you visit a website or call an API.

beginner

How does an HTTP triggered function receive input?

It receives input through the HTTP request's URL, headers, query parameters, or body sent by the client.

beginner

What happens after an HTTP triggered function finishes running?

It sends back an HTTP response to the caller, which can include data like text, JSON, or status codes.

beginner

Why are HTTP triggered functions useful for beginners?

Because they let you run code easily without managing servers, just by calling a web address, making it simple to build apps or APIs.

beginner

What is a common use case for HTTP triggered functions?

They are often used to create APIs, handle form submissions, or respond to webhooks from other services.

What triggers an HTTP triggered function in GCP?

A An incoming HTTP request

B A file upload to storage

C A scheduled timer

D A database update

HTTP triggered functions run when they receive an HTTP request from a client.

Which of these can be part of the input to an HTTP triggered function?

A CPU usage of the server

B Query parameters in the URL

C User's screen resolution

D Local file system data

Query parameters in the URL are sent as part of the HTTP request and can be used as input.

What does an HTTP triggered function return after execution?

A A cloud storage bucket

B A new virtual machine

C An HTTP response

D A database record

It returns an HTTP response to the caller, which can include data or status codes.

Which is NOT a typical use of HTTP triggered functions?

A Running background batch jobs without HTTP

B Handling API requests

C Responding to webhooks

D Processing form submissions

Background batch jobs usually use other triggers, not HTTP requests.

Why do HTTP triggered functions not require managing servers?

A Because they only run once a year

B Because they run on your local machine

C Because they use physical servers you manage

D Because they run on serverless platforms

They run on serverless platforms that handle servers automatically for you.

Explain how an HTTP triggered function works from receiving a request to sending a response.

Think about the journey of a web request to a cloud function and back.

List three common use cases for HTTP triggered functions and why they are suitable for those tasks.

Consider simple web tasks that need quick responses without managing servers.