Revision management in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy a new revision of a Cloud Run service.

GCP

gcloud run deploy my-service --image gcr.io/my-project/my-image:[1] --region us-central1

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

Astable

Bprod

Cv1

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' can cause unexpected updates.

Using environment names like 'prod' without tagging the image.

The revision tag v1 specifies the version of the container image to deploy as a new revision.

2fill in blank

medium

Complete the command to list all revisions of a Cloud Run service.

GCP

gcloud run revisions list --service=[1] --region us-central1

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

Alatest

Bdefault

Call

Dmy-service

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' which is not a service name.

Using 'latest' which is a tag, not a service.

The --service flag requires the name of the Cloud Run service, here my-service, to list its revisions.

3fill in blank

hard

Fix the error in the command to delete a specific revision.

GCP

gcloud run revisions delete [1] --region us-central1 --service my-service

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

Amy-service-00001-abc

Blatest

Cmy-service

Dall

Attempts:

3 left

💡 Hint

Common Mistakes

Using the service name instead of the revision name.

Using 'latest' which is not a revision identifier.

The revision name like my-service-00001-abc uniquely identifies the revision to delete.

4fill in blank

hard

Fill both blanks to set traffic to 100% on a specific revision.

GCP

gcloud run services update-traffic my-service --to-revisions [1]=100 --region [2]

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

Amy-service-00002-def

Bus-central1

Ceurope-west1

Dmy-service-00001-abc

Attempts:

3 left

💡 Hint

Common Mistakes

Using the service name instead of the revision name.

Using the wrong region.

Use the revision name my-service-00002-def and the region us-central1 to route all traffic to that revision.

5fill in blank

hard

Fill all three blanks to create a new revision with environment variables and specify the region.

GCP

gcloud run deploy my-service --image gcr.io/my-project/my-image:[1] --set-env-vars [2]=production --region [3]

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

Av3

BENV

Cus-east1

Dv2

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect image tag.

Using an invalid environment variable name.

Specifying the wrong region.

Deploy revision v2 with environment variable ENV=production in region us-east1.

Practice

1. What is the main purpose of revision management in Google Cloud services?

easy

A. To track and control different versions of your cloud services

B. To increase the storage capacity of your cloud database

C. To monitor network traffic between services

D. To automatically scale the number of virtual machines

Solution

1. Step 1: Understand revision management concept

   Revision management is about keeping track of different versions of your cloud services.

2. Step 2: Identify the main goal

   The main goal is to control versions for safe updates and rollbacks.

3. Final Answer:

   To track and control different versions of your cloud services -> Option A

4. Quick Check:

   Revision management = version control [OK]

Hint: Revision management means version control of services [OK]

Common Mistakes:

• Confusing revision management with scaling
• Thinking it manages storage or network
• Mixing it with monitoring tools

2. Which gcloud command is used to list all revisions of a Cloud Run service named my-service?

easy

A. gcloud run revisions list --service=my-service

B. gcloud run services list --revisions=my-service

C. gcloud revisions describe my-service

D. gcloud run deploy revisions --service=my-service

Solution

1. Step 1: Identify correct command structure

   The command to list revisions uses gcloud run revisions list with the service flag.

2. Step 2: Match service name parameter

   Using --service=my-service correctly specifies the service.

3. Final Answer:

   gcloud run revisions list --service=my-service -> Option A

4. Quick Check:

   List revisions = gcloud run revisions list --service [OK]

Hint: List revisions with 'gcloud run revisions list --service' [OK]

Common Mistakes:

• Using 'services list' instead of 'revisions list'
• Mixing 'describe' with listing
• Wrong command order or flags

3. Given the following commands, what will be the output of gcloud run revisions list --service=my-app after deploying twice?

gcloud run deploy my-app --image=image:v1 --no-traffic
gcloud run deploy my-app --image=image:v2 --no-traffic

medium

A. One revision with image:v2

B. No revisions because traffic is zero

C. Two revisions: one with image:v1 and one with image:v2

D. Error because --no-traffic disables revisions

Solution

1. Step 1: Understand deployment with --no-traffic

   Deploying with --no-traffic creates a new revision but does not route traffic to it.

2. Step 2: Analyze multiple deployments

   Deploying twice with different images creates two separate revisions.

3. Final Answer:

   Two revisions: one with image:v1 and one with image:v2 -> Option C

4. Quick Check:

   Each deploy creates a revision even with no traffic [OK]

Hint: Each deploy creates a revision, traffic doesn't affect revision count [OK]

Common Mistakes:

• Assuming no traffic means no revision
• Thinking only latest revision exists
• Confusing traffic routing with revision creation

4. You deployed a new revision but it is not receiving traffic. Which command fixes this by routing 100% traffic to the latest revision named my-app-00002?

medium

A. gcloud run revisions set-traffic my-app-00002 --percent=100

B. gcloud run services update-traffic my-app --to-revisions my-app-00002=100

C. gcloud run services update my-app --traffic my-app-00002=100

D. gcloud run services update-traffic my-app --to-revision my-app-00002=100

Solution

1. Step 1: Identify correct command to update traffic

   The command to update traffic routing is gcloud run services update-traffic.

2. Step 2: Use correct syntax for traffic split

   The syntax --to-revisions my-app-00002=100 routes 100% traffic to that revision.

3. Final Answer:

   gcloud run services update-traffic my-app --to-revisions my-app-00002=100 -> Option B

4. Quick Check:

   Update traffic with 'services update-traffic' and '--to-revisions' [OK]

Hint: Use 'gcloud run services update-traffic' with '--to-revisions' [OK]

Common Mistakes:

• Using 'update' instead of 'update-traffic'
• Wrong flag names like '--percent'
• Trying to set traffic on revision directly

5. You want to roll back your Cloud Run service web-app to a previous revision web-app-00003 safely without downtime. Which sequence of commands achieves this?

hard

A. gcloud run deploy web-app --image=web-app-00003

B. gcloud run services update web-app --revision web-app-00003

C. gcloud run revisions delete web-app-00004 && gcloud run services update-traffic web-app --to-revisions web-app-00003=100

D. gcloud run services update-traffic web-app --to-revisions web-app-00003=100

Solution

1. Step 1: Understand rollback via traffic routing

   Rolling back means routing traffic back to an existing previous revision.

2. Step 2: Use traffic update command

   Use gcloud run services update-traffic to send 100% traffic to the old revision.

3. Step 3: Avoid deleting revisions or redeploying

   Deleting or redeploying is unnecessary and may cause downtime.

4. Final Answer:

   gcloud run services update-traffic web-app --to-revisions web-app-00003=100 -> Option D

5. Quick Check:

   Rollback by routing traffic to old revision [OK]

Hint: Rollback by updating traffic to old revision, no redeploy needed [OK]

Common Mistakes:

• Trying to redeploy old revision as image
• Deleting newer revisions unnecessarily
• Using wrong commands to update revision