Reliability design principles in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a managed instance group with automatic healing.

GCP

gcloud compute instance-groups managed create my-group --base-instance-name my-instance --size [1] --template my-template --zone us-central1-a

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

A3

B1

C0

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting size to 0 disables the group.

Setting size too high without need increases cost.

The size parameter sets the number of instances. Setting it to 1 ensures at least one instance is running for reliability.

2fill in blank

medium

Complete the code to enable health checks for the instance group.

GCP

gcloud compute instance-groups managed set-autohealing --instance-group my-group --health-check [1] --initial-delay 300 --zone us-central1-a

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

Ahealth-check-1

Bdefault-check

Cmy-health-check

Dcheck-health

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent health check name.

Typos in the health check name.

The health check name must match the existing health check resource to enable autohealing.

3fill in blank

hard

Fix the error in the command to create a regional managed instance group.

GCP

gcloud compute instance-groups managed create my-regional-group --base-instance-name my-instance --size 2 --template my-template --region [1]

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

Aus-central1

Bus-central1-c

Cus-central1-b

Dus-central1-a

Attempts:

3 left

💡 Hint

Common Mistakes

Using a zone name instead of a region name.

Confusing region and zone parameters.

Regional instance groups require a region, not a zone. 'us-central1' is a region, while 'us-central1-a' is a zone.

4fill in blank

hard

Fill both blanks to configure a Cloud Storage bucket with versioning and lifecycle rule.

GCP

gsutil mb -l [1] gs://my-bucket/
gsutil versioning set on gs://my-bucket/
gsutil lifecycle set [2] gs://my-bucket

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

Aus-central1

B{"rule": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]}

Ceurope-west1

D{"rule": [{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"}, "condition": {"age": 30}}]}

Attempts:

3 left

💡 Hint

Common Mistakes

Using a zone instead of a region for bucket location.

Incorrect JSON format for lifecycle rules.

The bucket location is set to 'us-central1' for low latency. The lifecycle JSON deletes objects older than 30 days to manage storage costs.

5fill in blank

hard

Fill all three blanks to create a Pub/Sub subscription with message retention and dead-letter topic.

GCP

gcloud pubsub subscriptions create my-subscription --topic my-topic --message-retention-duration=[1] --dead-letter-topic=[2] --max-delivery-attempts=[3]

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

A10m

Bprojects/my-project/topics/dead-letter-topic

C5

D24h

Attempts:

3 left

💡 Hint

Common Mistakes

Using short retention times that lose messages too soon.

Incorrect dead-letter topic format.

Setting max delivery attempts too high or too low.

Message retention is set to 24 hours to keep messages available. The dead-letter topic is specified by its full path. Max delivery attempts is 5 to limit retries.