Cloud Run vs Cloud Functions decision in GCP - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to choose the service best suited for running containerized applications.

GCP

service = '[1]'  # Choose between Cloud Run and Cloud Functions

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

ACloud Run

BCloud Functions

CApp Engine

DCompute Engine

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Cloud Functions for containerized apps

Confusing App Engine with Cloud Run

Cloud Run is designed to run containerized applications, making it the best choice here.

2fill in blank

medium

Complete the code to select the service that automatically scales based on HTTP requests.

GCP

scaling_service = '[1]'  # Cloud Run or Cloud Functions

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

AKubernetes Engine

BCloud Functions

CCompute Engine

DCloud Run

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Compute Engine which requires manual scaling

Confusing Kubernetes Engine with serverless scaling

Cloud Functions automatically scale based on incoming HTTP requests or events.

3fill in blank

hard

Fix the error in the code to deploy a service that supports any programming language via containers.

GCP

deploy_service = '[1]'  # Choose Cloud Run or Cloud Functions

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

AFirebase Hosting

BApp Engine Standard

CCloud Functions

DCloud Run

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Cloud Functions for any language support

Confusing App Engine Standard with container support

Cloud Run supports any language because it runs containers, unlike Cloud Functions which have runtime restrictions.

4fill in blank

hard

Fill both blanks to configure a service that supports background tasks and HTTP triggers.

GCP

service_type = '[1]'
trigger_type = '[2]'  # Options: HTTP, Background

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

ACloud Functions

BCloud Run

CHTTP

DBackground

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Cloud Run for background triggers

Mixing trigger types incorrectly

Cloud Functions support both HTTP and background triggers, making it suitable for event-driven tasks.

5fill in blank

hard

Fill all three blanks to set up a service with custom CPU allocation, container image, and automatic scaling.

GCP

service = '[1]'
container_image = '[2]'
cpu_allocation = '[3]'  # e.g., 2 vCPU

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

ACloud Run

Bgcr.io/my-project/my-image

C2 vCPU

DCloud Functions

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Cloud Functions for container images

Setting CPU allocation on unsupported services

Cloud Run allows custom CPU allocation and runs container images with automatic scaling.

Practice

1. Which Google Cloud service is best suited for running simple event-driven code without managing servers?

easy

A. Compute Engine

B. Cloud Run

C. Cloud Functions

D. App Engine

Solution

1. Step 1: Understand event-driven code needs

   Simple event-driven code triggers automatically on events and requires minimal setup.

2. Step 2: Match service to event-driven model

   Cloud Functions is designed for event-driven code without server management.

3. Final Answer:

   Cloud Functions -> Option C

4. Quick Check:

   Event-driven code = Cloud Functions [OK]

Hint: Simple event-driven? Choose Cloud Functions [OK]

Common Mistakes:

• Choosing Cloud Run for simple event-driven tasks
• Confusing Compute Engine with serverless options
• Thinking App Engine is event-driven by default

2. Which of the following is the correct way to deploy a container image to Cloud Run using gcloud CLI?

easy

A. gcloud run deploy SERVICE --image IMAGE_URL --platform managed

B. gcloud functions deploy SERVICE --image IMAGE_URL

C. gcloud compute instances create SERVICE --image IMAGE_URL

D. gcloud app deploy SERVICE --image IMAGE_URL

Solution

1. Step 1: Identify correct command for Cloud Run deployment

   Cloud Run uses 'gcloud run deploy' with --image and --platform flags.

2. Step 2: Eliminate incorrect commands

   Functions, Compute, and App Engine use different commands and flags.

3. Final Answer:

   gcloud run deploy SERVICE --image IMAGE_URL --platform managed -> Option A

4. Quick Check:

   Cloud Run deploy = gcloud run deploy [OK]

Hint: Cloud Run deploy uses 'gcloud run deploy' with --image [OK]

Common Mistakes:

• Using 'gcloud functions deploy' for Cloud Run
• Confusing Compute Engine commands with Cloud Run
• Omitting --platform flag for Cloud Run

3. Given this scenario: You have a containerized app that needs to handle HTTP requests with custom runtime and environment variables. Which service will work correctly?

1. Deploy container to Cloud Run
2. Set environment variables in deployment
3. App handles HTTP requests

medium

A. Cloud Functions only

B. Cloud Run only

C. Both Cloud Run and Cloud Functions

D. Neither Cloud Run nor Cloud Functions

Solution

1. Step 1: Check container support and environment variables

   Cloud Run supports containerized apps and environment variables; Cloud Functions has limited container support and environment variable use.

2. Step 2: Match HTTP handling with service capabilities

   Cloud Run is designed for HTTP container apps with custom runtimes; Cloud Functions is for simpler functions.

3. Final Answer:

   Cloud Run only -> Option B

4. Quick Check:

   Container + env vars + HTTP = Cloud Run [OK]

Hint: Containerized HTTP app? Use Cloud Run [OK]

Common Mistakes:

• Assuming Cloud Functions supports full container apps
• Ignoring environment variable support differences
• Thinking both services handle custom runtimes equally

4. You tried deploying a container to Cloud Functions but got an error. What is the likely cause?

medium

A. Cloud Functions requires source code, not containers

B. Cloud Functions requires container images from Container Registry

C. Cloud Functions supports containers but only with specific runtimes

D. Cloud Functions supports containers only in beta

Solution

1. Step 1: Understand Cloud Functions deployment model

   Cloud Functions deploys source code or zipped code, not container images directly.

2. Step 2: Identify cause of deployment error

   Trying to deploy a container image causes error because Cloud Functions expects source code.

3. Final Answer:

   Cloud Functions requires source code, not containers -> Option A

4. Quick Check:

   Cloud Functions deploys source code only [OK]

Hint: Cloud Functions deploys code, not containers [OK]

Common Mistakes:

• Thinking Cloud Functions supports container images
• Confusing beta features with general availability
• Assuming all serverless services accept containers

5. Your team needs to deploy a microservice that requires custom libraries, runs on HTTP, and must scale automatically. You want to avoid managing servers but need full control over the runtime environment. Which service should you choose and why?

hard

A. Compute Engine, because it offers full control and automatic scaling

B. Cloud Functions, because it scales automatically and supports custom runtimes

C. App Engine Standard, because it supports custom libraries and auto-scaling

D. Cloud Run, because it runs containerized apps with full runtime control and auto-scaling

Solution

1. Step 1: Analyze requirements for runtime control and scaling

   Need full runtime control and automatic scaling without managing servers.

2. Step 2: Match service capabilities

   Cloud Run runs containerized apps with full control and auto-scales; Cloud Functions has limited runtime control; App Engine Standard has restrictions; Compute Engine requires server management.

3. Final Answer:

   Cloud Run, because it runs containerized apps with full runtime control and auto-scaling -> Option D

4. Quick Check:

   Custom runtime + auto-scale + no servers = Cloud Run [OK]

Hint: Full control + auto-scale? Pick Cloud Run [OK]

Common Mistakes:

• Choosing Cloud Functions for full runtime control
• Confusing App Engine Standard with container support
• Selecting Compute Engine despite server management needs