Function deployment and testing in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the first step to deploy a function on Google Cloud Platform?

The first step is to write your function code and prepare a deployment package or source code in a supported language.

beginner

Which Google Cloud service is used to deploy serverless functions?

Google Cloud Functions is the service used to deploy serverless functions that run in response to events.

intermediate

What command is used to deploy a function using the gcloud CLI?

Use the command: gcloud functions deploy FUNCTION_NAME --runtime RUNTIME --trigger-http to deploy a function with an HTTP trigger.

beginner

How can you test a deployed Google Cloud Function?

You can test it by sending an HTTP request if it has an HTTP trigger, or by triggering the event it listens to, then checking logs or output.

beginner

Why is it important to check logs after deploying a function?

Logs help you see if the function ran correctly or if there were errors, making it easier to fix problems.

Which command deploys a Google Cloud Function with an HTTP trigger?

A gcloud function create myFunc --trigger-http

B gcloud deploy function myFunc --runtime python39

C gcloud functions start myFunc --http

D gcloud functions deploy myFunc --runtime python39 --trigger-http

The correct command is 'gcloud functions deploy FUNCTION_NAME --runtime RUNTIME --trigger-http'.

What is a common way to test a function with an HTTP trigger?

A Send an HTTP request to the function's URL

B Restart the Google Cloud project

C Upload a file to Cloud Storage

D Run a SQL query

Functions with HTTP triggers respond to HTTP requests, so sending a request tests them.

Where can you find detailed error messages if a function fails?

A In the Cloud Storage bucket

B In the billing section

C In the function's logs on Google Cloud Console

D In the Compute Engine dashboard

Logs provide detailed information about function execution and errors.

Which runtime is NOT supported by Google Cloud Functions?

A Python 3.9

B Ruby 3.0

C Java 17

D Node.js 16

Ruby is not currently supported as a runtime for Google Cloud Functions.

What does the '--trigger-http' flag do during deployment?

A Makes the function respond to HTTP requests

B Triggers the function on file upload

C Runs the function on a schedule

D Deploys the function without a trigger

The '--trigger-http' flag sets the function to respond to HTTP requests.

Explain the steps to deploy a Google Cloud Function and how to test it after deployment.

Think about writing code, deploying with gcloud, then testing and checking logs.

Describe why logs are important in function deployment and testing.

Logs are like a diary for your function's actions.

Practice

1. What does deploying a Cloud Function in GCP mean?

easy

A. Uploading your code to the cloud so it can run when needed

B. Writing code on your local computer only

C. Deleting old versions of your code

D. Running your code only on your personal device

Solution

1. Step 1: Understand deployment meaning

   Deployment means putting your code on the cloud so it can be accessed and run remotely.

2. Step 2: Compare options

   Only Uploading your code to the cloud so it can run when needed describes uploading code to the cloud to run on demand, which matches deployment.

3. Final Answer:

   Uploading your code to the cloud so it can run when needed -> Option A

4. Quick Check:

   Deploy = Upload code to cloud [OK]

Hint: Deployment means putting code on cloud to run [OK]

Common Mistakes:

• Confusing deployment with local coding
• Thinking deployment deletes code
• Assuming deployment runs code only locally

2. Which command correctly deploys a Cloud Function named helloWorld with runtime python39 and trigger HTTP?

easy

A. gcloud functions run helloWorld --runtime python39 --trigger-http

B. gcloud deploy function helloWorld --runtime python39 --trigger-http

C. gcloud functions create helloWorld --runtime python39 --trigger-http

D. gcloud functions deploy helloWorld --runtime python39 --trigger-http

Solution

1. Step 1: Recall correct deploy syntax

   The correct command starts with 'gcloud functions deploy' followed by the function name and flags.

2. Step 2: Check options

   Only gcloud functions deploy helloWorld --runtime python39 --trigger-http uses 'gcloud functions deploy' with correct flags for runtime and trigger.

3. Final Answer:

   gcloud functions deploy helloWorld --runtime python39 --trigger-http -> Option D

4. Quick Check:

   Deploy command = 'gcloud functions deploy' [OK]

Hint: Deploy uses 'gcloud functions deploy' command [OK]

Common Mistakes:

• Using 'create' instead of 'deploy'
• Using 'run' instead of 'deploy'
• Wrong command order or missing flags

3. Given this deployment command:

gcloud functions deploy greetUser --runtime nodejs18 --trigger-http --allow-unauthenticated

What is the effect of the --allow-unauthenticated flag?

medium

A. Only authenticated users can call the function

B. Anyone can call the function without signing in

C. The function will not be deployed

D. The function will require a password to run

Solution

1. Step 1: Understand the flag meaning

   The flag '--allow-unauthenticated' means the function can be called by anyone without login.

2. Step 2: Match options

   Anyone can call the function without signing in correctly states that anyone can call the function without signing in.

3. Final Answer:

   Anyone can call the function without signing in -> Option B

4. Quick Check:

   Allow unauthenticated = open access [OK]

Hint: Allow unauthenticated means open access [OK]

Common Mistakes:

• Thinking it restricts access
• Confusing with authentication required
• Assuming it blocks deployment

4. You deployed a function but get an error when testing it. Which of these is a common cause?

medium

A. The function name in the deploy command does not match the code's exported function

B. You used the correct runtime but forgot to deploy

C. The function was deployed with the correct trigger and runs fine

D. You tested the function before writing any code

Solution

1. Step 1: Identify common deployment error

   If the deployed function name does not match the exported function in code, it causes errors on test.

2. Step 2: Evaluate options

   The function name in the deploy command does not match the code's exported function correctly points out this mismatch as a common cause of errors.

3. Final Answer:

   The function name in the deploy command does not match the code's exported function -> Option A

4. Quick Check:

   Name mismatch causes test errors [OK]

Hint: Match deploy name with exported function name [OK]

Common Mistakes:

• Ignoring function name mismatch
• Assuming deployment without code causes errors
• Testing before code exists

5. You want to deploy a function that triggers on new files in a Cloud Storage bucket named my-bucket. Which command correctly sets this trigger?

hard

A. gcloud functions deploy processFile --runtime python39 --trigger-http

B. gcloud functions deploy processFile --runtime python39 --trigger-topic my-bucket

C. gcloud functions deploy processFile --runtime python39 --trigger-resource my-bucket --trigger-event google.storage.object.finalize

D. gcloud functions deploy processFile --runtime python39 --trigger-bucket my-bucket

Solution

1. Step 1: Identify correct trigger for Cloud Storage

   Cloud Storage triggers use '--trigger-resource' with bucket name and '--trigger-event' with event type like 'google.storage.object.finalize'.

2. Step 2: Check options

   gcloud functions deploy processFile --runtime python39 --trigger-resource my-bucket --trigger-event google.storage.object.finalize correctly uses '--trigger-resource my-bucket' and '--trigger-event google.storage.object.finalize'. Others use wrong triggers.

3. Final Answer:

   gcloud functions deploy processFile --runtime python39 --trigger-resource my-bucket --trigger-event google.storage.object.finalize -> Option C

4. Quick Check:

   Storage trigger = resource + event flags [OK]

Hint: Use --trigger-resource and --trigger-event for storage triggers [OK]

Common Mistakes:

• Using --trigger-http for storage events
• Using --trigger-topic instead of resource/event
• Using non-existent --trigger-bucket flag