Buildpacks for source-based deployment in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy an app using Cloud Buildpacks with gcloud.

GCP

gcloud run deploy my-app --source=[1]

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

A./source

B./build

C./app

D./deploy

Attempts:

3 left

💡 Hint

Common Mistakes

Using a folder that does not contain source code

Omitting the --source flag

The --source flag specifies the directory containing your source code. Here, ./source is the correct folder.

2fill in blank

medium

Complete the command to specify the platform for Cloud Run deployment.

GCP

gcloud run deploy my-app --source=./source --platform=[1]

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

Alocal

Bcontainer

Ccustom

Dmanaged

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'local' or 'container' which are invalid platform options

Omitting the platform flag

The --platform=managed option tells Cloud Run to deploy on the fully managed platform.

3fill in blank

hard

Fix the error in the buildpack deployment command by completing the missing flag.

GCP

gcloud run deploy my-app --source=./source [1] my-region

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

A--location

B--region

C--area

D--zone

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect flags like --zone or --location

Not specifying any region flag

The correct flag to specify the deployment region is --region.

4fill in blank

hard

Fill both blanks to set the memory and CPU limits for the Cloud Run service.

GCP

gcloud run deploy my-app --memory=[1] --cpu=[2] --source=./source

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

A512Mi

B1

C256Mi

D2

Attempts:

3 left

💡 Hint

Common Mistakes

Using CPU as a string with units

Setting memory without units

Memory is set to 512Mi and CPU to 1 core for balanced resource allocation.

5fill in blank

hard

Fill all three blanks to create a buildpack deployment command with service name, region, and platform.

GCP

gcloud run deploy [1] --region=[2] --platform=[3] --source=./source

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

Amy-service

Bus-central1

Cmanaged

Deurope-west1

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid region names

Omitting the platform flag

The service name is my-service, region is us-central1, and platform is managed for a typical Cloud Run deployment.

Practice

1. What is the main benefit of using buildpacks for source-based deployment in Google Cloud Run?

easy

A. They only work with pre-built container images.

B. They require you to write Dockerfiles manually.

C. They automate building and containerizing your app from source code.

D. They disable automatic scaling of your app.

Solution

1. Step 1: Understand buildpacks purpose

   Buildpacks automate the process of building and packaging apps from source code without manual Dockerfile creation.

2. Step 2: Compare options

   Claims that buildpacks only work with pre-built images or require manual Dockerfiles contradict automation; disabling scaling is unrelated.

3. Final Answer:

   They automate building and containerizing your app from source code. -> Option C

4. Quick Check:

   Buildpacks = automate build and containerization [OK]

Hint: Buildpacks automate build and container creation from source [OK]

Common Mistakes:

• Thinking buildpacks require manual Dockerfiles
• Assuming buildpacks only work with images
• Confusing buildpacks with scaling features

2. Which command correctly deploys source code to Cloud Run using buildpacks?

easy

A. gcloud run deploy --source ./app

B. gcloud run deploy --image gcr.io/my-project/my-image

C. gcloud run deploy --dockerfile Dockerfile

D. gcloud run deploy --buildpack my-buildpack

Solution

1. Step 1: Identify source-based deploy syntax

   The correct command uses '--source' flag with the path to source code.

2. Step 2: Eliminate other options

   Using --image deploys a container image; --dockerfile uses a Dockerfile directly; --buildpack is an invalid flag.

3. Final Answer:

   gcloud run deploy --source ./app -> Option A

4. Quick Check:

   Source deploy uses --source flag [OK]

Hint: Use --source flag to deploy source code directly [OK]

Common Mistakes:

• Using --image instead of --source for source deploy
• Trying to specify Dockerfile with buildpacks
• Using invalid flags like --buildpack

3. Given this command:
gcloud run deploy my-app --source ./myapp
What happens during deployment?

medium

A. Cloud Run builds a container image from source using buildpacks and deploys it.

B. Cloud Run deploys the source code directly without building a container.

C. Cloud Run requires a Dockerfile in ./myapp to build the container.

D. Cloud Run deploys a default container ignoring the source code.

Solution

1. Step 1: Understand --source deploy behavior

   Using --source triggers Cloud Run to build a container image from source using buildpacks automatically.

2. Step 2: Evaluate other options

   Cloud Run does not deploy source code directly without building a container, as it always builds one; a Dockerfile is not required; it does not ignore the source code.

3. Final Answer:

   Cloud Run builds a container image from source using buildpacks and deploys it. -> Option A

4. Quick Check:

   --source triggers buildpacks build [OK]

Hint: Deploy with --source builds container via buildpacks [OK]

Common Mistakes:

• Thinking source code is deployed without container
• Assuming Dockerfile is mandatory
• Believing Cloud Run ignores source with --source flag

4. You run gcloud run deploy --source ./app but get an error: "No supported buildpack detected." What should you do?

medium

A. Restart Cloud Run service and try again.

B. Remove the --source flag and deploy with --image instead.

C. Create a Dockerfile manually in the source directory.

D. Add a supported language file (like package.json or requirements.txt) to your source directory.

Solution

1. Step 1: Understand buildpack detection

   Buildpacks detect app type by files like package.json (Node.js) or requirements.txt (Python).

2. Step 2: Fix missing detection files

   Adding these files helps buildpacks identify how to build the app, resolving the error.

3. Final Answer:

   Add a supported language file (like package.json or requirements.txt) to your source directory. -> Option D

4. Quick Check:

   Buildpacks need language files to detect app type [OK]

Hint: Include language files so buildpacks detect app type [OK]

Common Mistakes:

• Ignoring missing detection files
• Trying to deploy without source files
• Restarting service without fixing source

5. You want to deploy a Python app with source-based deployment using buildpacks. Your source folder contains app.py and requirements.txt. Which command and environment variable setup ensures the app runs on port 8080 as Cloud Run expects?

hard

A. gcloud run deploy my-python-app --source ./app

B. gcloud run deploy my-python-app --source ./app --set-env-vars PORT=8080

C. gcloud run deploy my-python-app --image python:latest

D. gcloud run deploy my-python-app --source ./app --set-env-vars PORT=80

Solution

1. Step 1: Use source deploy with buildpacks

   Deploying with --source triggers buildpacks to build the container from Python source.

2. Step 2: Set PORT environment variable to 8080

   Cloud Run expects apps to listen on port 8080; setting PORT=8080 ensures the app uses the correct port.

3. Step 3: Evaluate other options

   Using --set-env-vars PORT=80 sets the wrong port; using --image deploys a pre-built image instead of source; omitting the PORT=8080 setting may cause failure.

4. Final Answer:

   gcloud run deploy my-python-app --source ./app --set-env-vars PORT=8080 -> Option B

5. Quick Check:

   Set PORT=8080 for Cloud Run apps [OK]

Hint: Set PORT=8080 env var when deploying source apps [OK]

Common Mistakes:

• Not setting PORT environment variable
• Using default port 80 instead of 8080
• Deploying with image instead of source