Function deployment and testing in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy a Cloud Function named 'helloWorld'.

GCP

gcloud functions deploy helloWorld --runtime [1] --trigger-http --allow-unauthenticated

Drag options to blanks, or click blank then click option'

Ago113

Bnodejs16

Cpython39

Druby27

Attempts:

3 left

💡 Hint

Common Mistakes

Using an unsupported runtime version.

Misspelling the runtime name.

The correct runtime for deploying a Python 3.9 Cloud Function is python39.

2fill in blank

medium

Complete the code to test the deployed Cloud Function using curl.

GCP

curl -X GET [1]

Drag options to blanks, or click blank then click option'

Ahttps://storage.googleapis.com/helloWorld

Bhttps://cloudfunctions.googleapis.com/v1/helloWorld

Chttps://console.cloud.google.com/functions/details/helloWorld

Dhttps://region-project.cloudfunctions.net/helloWorld

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Cloud Console URL instead of the function trigger URL.

Using a storage or API URL unrelated to the function trigger.

The correct URL to invoke the Cloud Function is the HTTPS trigger URL, which looks like https://region-project.cloudfunctions.net/helloWorld.

3fill in blank

hard

Fix the error in the deployment command by completing the missing flag.

GCP

gcloud functions deploy helloWorld [1] main --runtime python39 --trigger-http

Drag options to blanks, or click blank then click option'

A--entry-point

B--region

C--timeout

D--memory

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing entry point with memory or timeout flags.

Omitting the entry point when the function name is not default.

The --entry-point flag specifies the function in your code to execute. It is required if the function name differs from the default.

4fill in blank

hard

Fill both blanks to set environment variables during deployment.

GCP

gcloud functions deploy helloWorld --runtime python39 --trigger-http --set-env-vars [1]=[2]

Drag options to blanks, or click blank then click option'

AENVIRONMENT

Bproduction

CDEBUG

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping variable name and value.

Using invalid environment variable names.

Environment variables are set as key=value pairs. Here, ENVIRONMENT=production sets the environment to production.

5fill in blank

hard

Fill all three blanks to write a test command that sends JSON data to the function.

GCP

curl -X POST -H 'Content-Type: application/json' -d '{"name": "[1]"}' [2] [3]

Drag options to blanks, or click blank then click option'

AAlice

Bhttps://region-project.cloudfunctions.net/helloWorld

C--silent

DBob

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect URL.

Omitting the content type header.

Not formatting JSON data properly.

The JSON data includes a name field with value 'Alice'. The URL is the function's HTTPS trigger. The --silent flag suppresses curl progress output.

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