Why serverless patterns matter in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy a serverless function on Google Cloud Functions.

GCP

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

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

Apython39

Bnodejs16

Cgo113

Djava11

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a runtime that does not support Python 3.9

Using an unsupported or outdated runtime version

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

2fill in blank

medium

Complete the code to set the memory allocation for a Cloud Function.

GCP

gcloud functions deploy myFunction --runtime python39 --memory [1] --trigger-http

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

A128MB

B512MB

C256MB

D1GB

Attempts:

3 left

💡 Hint

Common Mistakes

Using memory sizes without units

Choosing memory sizes not supported by Cloud Functions

256MB is a common memory allocation for lightweight serverless functions balancing cost and performance.

3fill in blank

hard

Fix the error in the Cloud Function trigger type to respond to HTTP requests.

GCP

gcloud functions deploy myFunction --runtime python39 --trigger-[1] --allow-unauthenticated

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

Abucket

Bhttp

Ctopic

Dpubsub

Attempts:

3 left

💡 Hint

Common Mistakes

Using bucket or pubsub triggers for HTTP functions

Misspelling the trigger type

The correct trigger for HTTP requests is http. Other triggers are for storage buckets or messaging.

4fill in blank

hard

Fill both blanks to create a serverless function that scales automatically and logs output.

GCP

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

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

Amax-instances=5

Bmin-instances=0

CDEBUG

DINFO

Attempts:

3 left

💡 Hint

Common Mistakes

Setting max-instances instead of min-instances for scaling

Using DEBUG level when INFO is preferred for general logs

Setting min-instances=0 allows automatic scaling to zero when idle. Setting LOG_LEVEL=INFO configures logging verbosity.

5fill in blank

hard

Fill all three blanks to define a serverless function with a timeout, memory, and environment variable.

GCP

gcloud functions deploy myFunction --runtime python39 --timeout=[1] --memory=[2] --set-env-vars MODE=[3]

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

A60s

B256MB

Cproduction

D120s

Attempts:

3 left

💡 Hint

Common Mistakes

Using too short timeout causing function to stop early

Choosing memory sizes too small for workload

Setting environment variables incorrectly

A 120-second timeout allows longer processing. 256MB memory balances cost and performance. Setting MODE to production configures the function for live use.

Practice

1. What is the main benefit of using serverless patterns in cloud applications?

easy

A. Fixed monthly billing regardless of usage

B. Manual control over server hardware

C. Automatic scaling without managing servers

D. Requires setting up virtual machines

Solution

1. Step 1: Understand serverless basics

   Serverless means the cloud provider manages servers, so you don't have to.

2. Step 2: Identify key benefit

   Serverless apps scale automatically based on demand without manual server management.

3. Final Answer:

   Automatic scaling without managing servers -> Option C

4. Quick Check:

   Serverless = automatic scaling [OK]

Hint: Serverless means no server setup needed [OK]

Common Mistakes:

• Thinking serverless means no servers exist
• Assuming fixed billing regardless of usage
• Confusing serverless with manual server control

2. Which of the following is the correct way to define a Cloud Function trigger in GCP serverless pattern?

easy

A. trigger: http

B. trigger: virtual_machine

C. trigger: manual_start

D. trigger: database_backup

Solution

1. Step 1: Recall Cloud Function triggers

   Cloud Functions commonly trigger on HTTP requests or events, not manual or VM triggers.

2. Step 2: Identify valid trigger

   trigger: http is the correct syntax for HTTP-triggered functions.

3. Final Answer:

   <code>trigger: http</code> -> Option A

4. Quick Check:

   HTTP trigger syntax = correct [OK]

Hint: Cloud Functions trigger on events like HTTP [OK]

Common Mistakes:

• Using triggers that don't exist like manual_start
• Confusing VM triggers with serverless triggers
• Assuming database_backup is a trigger

3. Given this serverless function code snippet in GCP:

def hello_world(event, context):
    print('Hello, world!')

What happens when this function is deployed and triggered by an event?

medium

A. The function prints 'Hello, world!' to the logs

B. The function returns 'Hello, world!' to the caller

C. The function fails because of missing return statement

D. The function runs only once and then stops

Solution

1. Step 1: Understand function behavior

   The function prints a message to logs when triggered; no return value is needed.

2. Step 2: Identify output

   Print statements appear in logs, not as return to caller.

3. Final Answer:

   The function prints 'Hello, world!' to the logs -> Option A

4. Quick Check:

   Print output = logs [OK]

Hint: Print outputs go to logs, not caller [OK]

Common Mistakes:

• Expecting print to return value to caller
• Thinking missing return causes failure
• Assuming function runs only once

4. You deployed a serverless function but it never triggers on new file uploads to Cloud Storage. What is the most likely cause?

medium

A. The function code has syntax errors

B. The function trigger is not set to Cloud Storage events

C. The Cloud Storage bucket is empty

D. The function is set to manual trigger only

Solution

1. Step 1: Check trigger configuration

   For automatic runs on file uploads, the function must have a Cloud Storage event trigger.

2. Step 2: Identify cause of no trigger

   If trigger is missing or incorrect, function won't run on uploads.

3. Final Answer:

   The function trigger is not set to Cloud Storage events -> Option B

4. Quick Check:

   Trigger mismatch = no function run [OK]

Hint: Check event trigger matches source action [OK]

Common Mistakes:

• Assuming empty bucket stops triggers
• Blaming code errors without checking triggers
• Confusing manual trigger with event trigger

5. You want to build a serverless app that processes images uploaded to Cloud Storage and stores metadata in Firestore. Which serverless pattern best fits this use case?

hard

A. Using a scheduled job to scan the bucket every hour

B. Manual invocation of functions via HTTP requests

C. Running a VM continuously to watch the bucket

D. Event-driven functions triggered by Cloud Storage events

Solution

1. Step 1: Analyze use case requirements

   The app needs to react immediately to image uploads and process them.

2. Step 2: Match pattern to requirement

   Event-driven functions triggered by Cloud Storage events run code automatically on uploads.

3. Step 3: Evaluate other options

   Manual HTTP triggers, VMs, or scheduled jobs are less efficient or not real-time.

4. Final Answer:

   Event-driven functions triggered by Cloud Storage events -> Option D

5. Quick Check:

   Event-driven = automatic, real-time processing [OK]

Hint: Use event triggers for real-time processing [OK]

Common Mistakes:

• Choosing manual triggers for automatic events
• Using VMs instead of serverless functions
• Relying on scheduled jobs for immediate processing