Why serverless patterns matter in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Serverless Benefits

Which of the following is the primary benefit of using serverless patterns in cloud infrastructure?

A You manage the underlying servers directly for better control.

B You must provision fixed capacity ahead of time.

C It automatically scales with demand without manual intervention.

D It requires installing and maintaining operating systems.

💡 Hint

Think about how serverless handles changes in workload.

Serverless automatically adjusts resources based on demand, so you don't manage servers or capacity.

❓ Architecture

intermediate

Serverless Event-Driven Architecture

In a serverless event-driven architecture on GCP, which service is best suited to trigger functions based on file uploads to cloud storage?

A Cloud Pub/Sub

B Cloud Storage Triggers

C Cloud SQL

D Compute Engine

💡 Hint

Consider which service directly reacts to storage events.

Cloud Storage Triggers invoke serverless functions automatically when files are uploaded or changed.

❓ security

advanced

Securing Serverless Functions

Which practice best secures serverless functions to minimize risk of unauthorized access?

A Store secrets in a managed secret manager and grant least privilege access.

B Use environment variables with no encryption.

C Embed all secrets directly in the function code.

D Allow public internet access to all functions for easy testing.

💡 Hint

Think about secure secret storage and access control.

Using a secret manager with least privilege access protects sensitive data and limits exposure.

❓ service_behavior

advanced

Serverless Cold Start Impact

What is the typical impact of a cold start on serverless function performance?

A Functions may have a noticeable delay on first invocation after inactivity.

B Functions start instantly with no delay.

C Functions crash on cold start due to missing dependencies.

D Functions consume more memory but run faster on cold start.

💡 Hint

Consider what happens when a function is invoked after being idle.

Cold starts cause a delay because the platform initializes the function environment before running code.

✅ Best Practice

expert

Optimizing Cost with Serverless Patterns

Which approach best optimizes cost when designing serverless applications on GCP?

A Keep functions running continuously to avoid cold starts.

B Deploy all logic in a single large function to reduce invocation counts.

C Provision maximum memory for all functions regardless of workload.

D Use serverless functions only for short, infrequent tasks and offload heavy processing elsewhere.

💡 Hint

Think about matching workload patterns to serverless strengths.

Serverless is cost-effective for short, event-driven tasks; heavy or long-running tasks may be better elsewhere.

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