Serverless vs GKE decision in GCP - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to choose the best option for a fully managed, event-driven compute service.

GCP

service = "[1]"  # Choose the serverless compute option

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

AGoogle Kubernetes Engine

BCloud Run

CCompute Engine

DApp Engine Flexible

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing GKE which requires cluster management.

Selecting Compute Engine which is VM-based, not serverless.

Cloud Run is a fully managed serverless platform that runs containers on demand, ideal for event-driven workloads.

2fill in blank

medium

Complete the code to select the best option for running containerized applications with full control over orchestration.

GCP

service = "[1]"  # Choose the container orchestration platform

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

AGoogle Kubernetes Engine

BApp Engine Standard

CCloud Run

DCloud Functions

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Cloud Run which is serverless and abstracts orchestration.

Selecting Cloud Functions which is for event-driven functions, not containers.

Google Kubernetes Engine (GKE) provides full control over container orchestration and cluster management.

3fill in blank

hard

Fix the error in the decision code to select the best option for a workload needing automatic scaling without cluster management.

GCP

if workload == "event-driven" and needs_scaling:
    platform = "[1]"

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

AApp Engine Flexible

BGoogle Kubernetes Engine

CCloud Run

DCompute Engine

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing GKE which requires manual cluster management.

Selecting Compute Engine which is VM-based and not serverless.

Cloud Run automatically scales containers based on demand without requiring cluster management, ideal for event-driven workloads.

4fill in blank

hard

Fill both blanks to complete the decision logic for choosing between serverless and GKE based on control and scaling needs.

GCP

if needs_full_control == [1] and wants_serverless == [2]:
    platform = "Google Kubernetes Engine"

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

ATrue

BFalse

CNone

DMaybe

Attempts:

3 left

💡 Hint

Common Mistakes

Setting wants_serverless to True when choosing GKE.

Using None or Maybe which are not boolean values.

If full control is needed (True) and serverless is not wanted (False), GKE is the right choice.

5fill in blank

hard

Fill all three blanks to complete the function that decides the platform based on workload type, control, and scaling.

GCP

def choose_platform(workload_type, needs_control, auto_scale):
    if workload_type == [1] and not needs_control and auto_scale:
        return [2]
    else:
        return [3]

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

A"event-driven"

B"Cloud Run"

C"Google Kubernetes Engine"

D"batch"

Attempts:

3 left

💡 Hint

Common Mistakes

Using batch instead of event-driven for workload_type.

Returning GKE for event-driven without control needs.

For event-driven workloads without control needs and requiring auto scaling, Cloud Run is best. Otherwise, GKE is chosen.

Practice

1. Which option best describes a key benefit of using serverless computing in GCP?

easy

A. No need to manage servers and automatic scaling happens

B. You get full control over the underlying hardware

C. You must manually configure load balancers

D. You need to manage container orchestration

Solution

1. Step 1: Understand serverless basics

   Serverless means the cloud provider handles server management and scaling automatically.

2. Step 2: Compare options

   The other options describe manual management or container orchestration, which are not serverless benefits.

3. Final Answer:

   No need to manage servers and automatic scaling happens -> Option A

4. Quick Check:

   Serverless = No server management + auto scaling [OK]

Hint: Serverless means no servers to manage, auto scales itself [OK]

Common Mistakes:

• Confusing serverless with container management
• Thinking serverless requires manual scaling
• Assuming serverless means full hardware control

2. Which of the following is the correct way to deploy a containerized app on GKE?

easy

A. Use gcloud run deploy command

B. Use kubectl apply -f deployment.yaml command

C. Use firebase deploy command

D. Use gsutil cp to upload container image

Solution

1. Step 1: Identify GKE deployment command

   GKE uses Kubernetes commands like kubectl apply to deploy resources from YAML files.

2. Step 2: Check other commands

   gcloud run deploy is for serverless Cloud Run, firebase deploy is for Firebase apps, and gsutil cp uploads files to storage, not deploy containers.

3. Final Answer:

   Use kubectl apply -f deployment.yaml command -> Option B

4. Quick Check:

   GKE deploy = kubectl apply [OK]

Hint: GKE uses kubectl with YAML files to deploy containers [OK]

Common Mistakes:

• Using Cloud Run commands for GKE
• Confusing Firebase deploy with container deployment
• Uploading images with gsutil instead of container registry

3. You have a web app with unpredictable traffic spikes and want minimal management. Which GCP service behavior fits best?

medium

A. Serverless auto-scales instantly with no server management

B. GKE requires manual scaling and cluster management

C. GKE automatically scales without any configuration

D. Serverless requires you to provision VM instances

Solution

1. Step 1: Analyze traffic and management needs

   Unpredictable spikes need fast scaling and minimal management.

2. Step 2: Match service behavior

   Serverless auto-scales instantly and requires no server management. GKE needs manual or configured scaling and cluster upkeep.

3. Final Answer:

   Serverless auto-scales instantly with no server management -> Option A

4. Quick Check:

   Unpredictable traffic + minimal management = Serverless [OK]

Hint: Unpredictable traffic? Choose serverless for auto scaling [OK]

Common Mistakes:

• Assuming GKE scales automatically without config
• Thinking serverless needs VM provisioning
• Confusing manual and automatic scaling

4. You deployed a container on GKE but it fails to start. Which fix is most likely needed?

medium

A. Enable serverless API in GCP console

B. Increase Cloud Run memory allocation

C. Check and fix container image path in deployment YAML

D. Upload container image to Firebase hosting

Solution

1. Step 1: Identify cause of container start failure

   Common cause is incorrect container image path or tag in deployment YAML.

2. Step 2: Evaluate options

   Increasing Cloud Run memory or enabling serverless API does not affect GKE container start. Firebase hosting is unrelated to container images.

3. Final Answer:

   Check and fix container image path in deployment YAML -> Option C

4. Quick Check:

   Container start fail? Fix image path in YAML [OK]

Hint: Check container image path in YAML if GKE pod fails [OK]

Common Mistakes:

• Trying serverless fixes for GKE issues
• Uploading images to wrong services
• Ignoring deployment YAML errors

5. Your app needs custom networking, persistent storage, and runs long background jobs. Which GCP choice fits best?

hard

A. Use serverless Cloud Run for easy scaling and no management

B. Use Firebase hosting for backend processing

C. Use App Engine standard environment for background jobs

D. Use GKE for full control over networking and storage

Solution

1. Step 1: Identify app requirements

   Custom networking, persistent storage, and long background jobs require control and flexibility.

2. Step 2: Match requirements to GCP services

   GKE offers container orchestration with networking and storage control. Serverless Cloud Run lacks persistent storage and complex networking. App Engine standard has limitations on background jobs. Firebase hosting is for static content.

3. Final Answer:

   Use GKE for full control over networking and storage -> Option D

4. Quick Check:

   Custom network + storage + long jobs = GKE [OK]

Hint: Need control and storage? Choose GKE over serverless [OK]

Common Mistakes:

• Choosing serverless despite storage needs
• Using App Engine for heavy background jobs
• Confusing Firebase hosting with backend services