Disaster recovery strategies in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a backup of a Cloud Storage bucket.

GCP

gsutil [1] gs://my-bucket gs://my-backup-bucket

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

Arm

Bcp

Crsync

Dmv

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cp' copies files but does not sync changes.

Using 'mv' moves files instead of copying.

Using 'rm' deletes files, which is not for backup.

The gsutil rsync command synchronizes the contents of two buckets, making it suitable for backups.

2fill in blank

medium

Complete the code to create a snapshot of a Compute Engine disk.

GCP

gcloud compute disks snapshots create my-snapshot --disk=[1] --zone=us-central1-a

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

Amy-disk

Bmy-snapshot

Cmy-instance

Dus-central1-a

Attempts:

3 left

💡 Hint

Common Mistakes

Using the instance name instead of the disk name.

Using the snapshot name as the disk name.

Using the zone name as the disk name.

The --disk flag requires the name of the disk to snapshot, which is my-disk.

3fill in blank

hard

Fix the error in the Terraform code to enable multi-region replication for a Cloud Storage bucket.

GCP

resource "google_storage_bucket" "backup" {
  name     = "my-backup-bucket"
  location = [1]
  force_destroy = true
}

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

A"US"

B"US-CENTRAL1"

C"MULTI_REGIONAL"

D"us-central1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a single region name instead of a multi-region.

Using incorrect casing for location names.

Using a string that is not a valid location.

To enable multi-region replication, the bucket location must be set to a multi-region like US, not a single region like us-central1.

4fill in blank

hard

Fill both blanks to configure a Cloud SQL instance for high availability with failover replicas.

GCP

resource "google_sql_database_instance" "primary" {
  name             = "primary-instance"
  database_version = "POSTGRES_14"
  region           = [1]
  settings {
    availability_type = [2]
  }
}

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

A"us-central1"

B"us-east1"

C"ZONAL"

D"REGIONAL"

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid region name.

Setting availability_type to ZONAL which disables failover.

Mixing region and availability_type values.

The region should be a valid GCP region like us-central1. For high availability, availability_type must be set to REGIONAL to enable failover replicas.

5fill in blank

hard

Fill all three blanks to define a Cloud DNS managed zone with private visibility for disaster recovery.

GCP

resource "google_dns_managed_zone" "private_zone" {
  name        = [1]
  dns_name    = [2]
  visibility  = [3]
}

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

A"private-zone-1"

B"example.internal."

C"private"

D"public"

Attempts:

3 left

💡 Hint

Common Mistakes

Using public visibility for private zones.

Omitting the trailing dot in dns_name.

Using invalid zone names.

The managed zone needs a name like private-zone-1, a DNS name ending with a dot like example.internal., and visibility set to private for internal use in disaster recovery.