Cloud Functions generations (1st vs 2nd) in GCP - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the generation of the Cloud Function.

GCP

gcloud functions deploy my-function --runtime python39 --trigger-http --gen [1]

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

A1

B2

C3

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using '1' instead of '2' for the generation flag.

Using 'latest' which is not a valid generation option.

The --gen 2 flag specifies the second generation Cloud Function, which supports newer features.

2fill in blank

medium

Complete the code to set the region for a 2nd generation Cloud Function.

GCP

gcloud functions deploy my-function --runtime nodejs18 --trigger-http --gen 2 --region [1]

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

Aeurope-west1

Bglobal

Cus-east1

Dus-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'global' which is not supported for 2nd gen functions.

Choosing a region not supported by Cloud Functions.

Second generation Cloud Functions require specifying a region like us-central1.

3fill in blank

hard

Fix the error in the deployment command for a 1st generation Cloud Function.

GCP

gcloud functions deploy my-function --runtime python39 --trigger-http --gen [1] --region us-central1

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

A1

B3

C2

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--gen 2' for a first generation function.

Omitting the generation flag when required.

First generation Cloud Functions use --gen 1. The region flag is optional but allowed.

4fill in blank

hard

Fill both blanks to configure a 2nd generation Cloud Function with memory and timeout.

GCP

gcloud functions deploy my-function --runtime go120 --trigger-http --gen 2 --memory [1] --timeout [2]

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

A512MB

B60s

C128MB

D540s

Attempts:

3 left

💡 Hint

Common Mistakes

Using too low memory like 128MB for heavier workloads.

Setting timeout too high or without 's' suffix.

Second generation functions support memory like 512MB and timeout like 60s.

5fill in blank

hard

Fill all three blanks to create a 2nd generation Cloud Function with environment variables and service account.

GCP

gcloud functions deploy my-function --runtime nodejs18 --trigger-http --gen 2 --set-env-vars [1] --service-account [2] --region [3]

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

AENV=prod,DEBUG=false

[e-mail]

Cus-central1

DENV=dev,DEBUG=true

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid environment variable format.

Using a wrong or missing service account.

Choosing an unsupported region.

Set environment variables as key=value pairs separated by commas, specify the service account email, and choose a valid region.

Practice

1. Which generation of Cloud Functions supports automatic scaling with more control over CPU and memory allocation?

easy

A. 2nd generation

B. 1st generation

C. Both generations support the same scaling features

D. Neither generation supports automatic scaling

Solution

1. Step 1: Understand scaling features of 1st gen

   1st gen Cloud Functions scale automatically but have limited control over CPU and memory.

2. Step 2: Understand scaling features of 2nd gen

   2nd gen Cloud Functions provide automatic scaling with more control over CPU and memory allocation.

3. Final Answer:

   2nd generation -> Option A

4. Quick Check:

   More control and scaling = 2nd generation [OK]

Hint: Remember: 2nd gen adds more control and features [OK]

Common Mistakes:

• Thinking 1st gen has advanced scaling controls
• Assuming both generations have identical features
• Believing scaling is manual in both generations

2. Which command correctly deploys a Cloud Function using the 2nd generation environment?

easy

A. gcloud functions create my-function --gen=2

B. gcloud functions deploy my-function --gen=2

C. gcloud deploy function my-function --gen=2

D. gcloud functions deploy my-function --generation=2

Solution

1. Step 1: Recall correct gcloud syntax for generation

   The correct flag to specify generation is --gen=2 with gcloud functions deploy.

2. Step 2: Check command structure

   Only gcloud functions deploy my-function --gen=2 uses the correct command and flag syntax.

3. Final Answer:

   gcloud functions deploy my-function --gen=2 -> Option B

4. Quick Check:

   Use --gen=2 with deploy command [OK]

Hint: Use --gen=2 with 'gcloud functions deploy' [OK]

Common Mistakes:

• Using --generation=2 instead of --gen=2
• Using 'create' instead of 'deploy'
• Incorrect command order or syntax

3. Given this deployment command:
gcloud functions deploy helloWorld --runtime python312 --trigger-http --gen=1
What is the expected behavior compared to using --gen=2?

medium

A. Function runs with limited CPU and memory options and no concurrency

B. Function supports concurrency and custom CPU allocation

C. Function cannot be triggered by HTTP

D. Function runs only on App Engine environment

Solution

1. Step 1: Analyze 1st gen deployment features

   1st gen Cloud Functions have fixed CPU and memory limits and do not support concurrency.

2. Step 2: Compare with 2nd gen features

   2nd gen supports concurrency and custom CPU allocation, unlike 1st gen.

3. Final Answer:

   Function runs with limited CPU and memory options and no concurrency -> Option A

4. Quick Check:

   1st gen = limited resources, no concurrency [OK]

Hint: 1st gen lacks concurrency and CPU control [OK]

Common Mistakes:

• Assuming 1st gen supports concurrency
• Confusing trigger types with generation features
• Thinking 1st gen runs on App Engine

4. You deployed a Cloud Function with --gen=2 but it fails to start due to missing environment variables. What is the likely cause?

medium

A. 1st gen functions do not support environment variables

B. The function runtime does not support environment variables

C. Environment variables were not set using the correct 2nd gen syntax

D. Cloud Functions do not support environment variables in any generation

Solution

1. Step 1: Understand environment variable support

   Both generations support environment variables, but 2nd gen requires specific syntax to set them.

2. Step 2: Identify common deployment mistake

   Using 1st gen syntax or missing flags causes environment variables to be unset in 2nd gen.

3. Final Answer:

   Environment variables were not set using the correct 2nd gen syntax -> Option C

4. Quick Check:

   2nd gen needs correct env var syntax [OK]

Hint: Use correct env var flags for 2nd gen deployment [OK]

Common Mistakes:

• Assuming env vars are unsupported in 1st gen
• Ignoring syntax differences between generations
• Believing runtime limits env var usage

5. You want to deploy a Cloud Function that handles high traffic with concurrency and custom CPU allocation. Which generation should you choose and why?

hard

A. 2nd generation, but it does not support CPU customization

B. 1st generation, because it is simpler and scales automatically

C. 1st generation, because it supports concurrency by default

D. 2nd generation, because it supports concurrency and CPU customization

Solution

1. Step 1: Identify requirements

   The function needs to handle high traffic with concurrency and custom CPU allocation.

2. Step 2: Match features to generation

   2nd gen supports concurrency and lets you customize CPU; 1st gen does not support concurrency or CPU customization.

3. Final Answer:

   2nd generation, because it supports concurrency and CPU customization -> Option D

4. Quick Check:

   Concurrency + CPU control = 2nd gen [OK]

Hint: Choose 2nd gen for concurrency and CPU control [OK]

Common Mistakes:

• Choosing 1st gen for concurrency
• Ignoring CPU customization needs
• Confusing simplicity with feature support