Cloud DNS for domain management in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new managed zone in Cloud DNS.

GCP

gcloud dns managed-zones create [1] --dns-name="example.com." --description="My zone"

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

Aexample-zone

Bmy-zone

Czone1

Ddns-zone

Attempts:

3 left

💡 Hint

Common Mistakes

Using the domain name with dots instead of a simple zone name.

Leaving the zone name empty.

The managed zone name should be a unique identifier like example-zone.

2fill in blank

medium

Complete the code to add an A record to the managed zone.

GCP

gcloud dns record-sets transaction start --zone=[1]

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

Amy-zone

Bexample-zone

Czone1

Ddns-zone

Attempts:

3 left

💡 Hint

Common Mistakes

Using the domain name instead of the zone name.

Using a zone name that does not exist.

You must specify the correct managed zone name where the record will be added.

3fill in blank

hard

Fix the error in the command to add an A record for www.example.com pointing to 1.2.3.4.

GCP

gcloud dns record-sets transaction add 1.2.3.4 --name=[1] --ttl=300 --type=A --zone=example-zone

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

Aexample.com

Bwww.example.com

Cexample.com.

Dwww.example.com.

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the trailing dot in the DNS name.

Using the domain name without 'www'.

The DNS name must end with a dot to indicate it is a fully qualified domain name.

4fill in blank

hard

Fill both blanks to complete the commands to describe the pending transaction and then execute it.

GCP

gcloud dns record-sets transaction [1] --zone=example-zone

gcloud dns record-sets transaction [2] --zone=example-zone

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

Aexecute

Bstart

Cdescribe

Dabort

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' or 'abort' instead of 'execute' to apply changes.

Confusing the order of commands.

First, describe the transaction to preview changes, then execute to apply them.

5fill in blank

hard

Fill all three blanks to create a TXT record for domain verification.

GCP

gcloud dns record-sets transaction add "[1]" --name=[2] --ttl=[3] --type=TXT --zone=example-zone

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

Agoogle-site-verification=abc123

Bexample.com.

C300

Dwww.example.com.

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the TXT value.

Omitting the trailing dot in the domain name.

Using an incorrect TTL value.

The TXT record value must be quoted, the name must be the domain with a trailing dot, and TTL is usually 300 seconds.

Practice

1. What is the main purpose of Cloud DNS in domain management?

easy

A. To manage user access permissions

B. To store website files and images

C. To create virtual machines

D. To connect your domain name to your website or service

Solution

1. Step 1: Understand what Cloud DNS does

   Cloud DNS translates domain names into IP addresses so browsers can find your website or service.

2. Step 2: Identify the correct purpose

   Connecting domain names to services is the core function of Cloud DNS, not storing files or managing users.

3. Final Answer:

   To connect your domain name to your website or service -> Option D

4. Quick Check:

   Cloud DNS connects domain to service = A [OK]

Hint: Cloud DNS links names to IPs, not files or users [OK]

Common Mistakes:

• Confusing DNS with storage services
• Thinking DNS manages virtual machines
• Mixing DNS with user permission controls

2. Which of the following is the correct way to create a managed zone using gcloud CLI?

easy

A. gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone"

B. gcloud dns create-zone my-zone example.com

C. gcloud create dns-zone --name my-zone --domain example.com

D. gcloud dns zones add my-zone example.com

Solution

1. Step 1: Recall the gcloud command syntax for creating managed zones

   The correct command uses 'gcloud dns managed-zones create' followed by the zone name and flags for DNS name and description.

2. Step 2: Match the correct syntax

   gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone" matches the official syntax exactly, others use incorrect commands or flags.

3. Final Answer:

   gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone" -> Option A

4. Quick Check:

   Correct gcloud create syntax = A [OK]

Hint: Use 'gcloud dns managed-zones create' with flags [OK]

Common Mistakes:

• Using wrong command verbs like 'create-zone'
• Omitting required flags like --dns-name
• Mixing command order or parameters

3. Given this DNS record in a managed zone:
example.com. IN A 192.0.2.1
What happens when a user types example.com in their browser?

medium

A. The browser connects to the IP address 192.0.2.1

B. The browser shows an error because A records are invalid

C. The browser redirects to example.com.com

D. The browser connects to a random IP address

Solution

1. Step 1: Understand the A record function

   An A record maps a domain name to an IPv4 address, here 192.0.2.1.

2. Step 2: Predict browser behavior

   When typing example.com, the browser looks up the A record and connects to the specified IP address.

3. Final Answer:

   The browser connects to the IP address 192.0.2.1 -> Option A

4. Quick Check:

   A record maps domain to IP = B [OK]

Hint: A record points domain to IP address [OK]

Common Mistakes:

• Thinking A records cause errors
• Confusing A record with redirects
• Assuming random IP connections

4. You tried to add a CNAME record for your domain root (example.com) but it failed. What is the likely reason?

medium

A. The TTL value was too high

B. You must use an MX record instead

C. CNAME records are not allowed at the root domain

D. You need to delete all A records first

Solution

1. Step 1: Recall DNS rules for CNAME records

   CNAME records cannot be set at the root domain because it conflicts with other essential records like NS and SOA.

2. Step 2: Identify the cause of failure

   Trying to add a CNAME at the root domain violates DNS standards, causing the failure.

3. Final Answer:

   CNAME records are not allowed at the root domain -> Option C

4. Quick Check:

   CNAME not allowed at root domain = C [OK]

Hint: Root domain cannot have CNAME records [OK]

Common Mistakes:

• Confusing CNAME with MX record usage
• Blaming TTL values for record rejection
• Thinking A records must be deleted first

5. You want to set up email for your domain example.com using Cloud DNS. Which DNS record type should you add to direct emails to your mail server?

hard

A. TXT record with your mail server IP

B. MX record pointing to your mail server domain

C. CNAME record pointing to your mail server domain

D. A record pointing to your mail server IP

Solution

1. Step 1: Identify the DNS record for email routing

   MX records specify mail servers responsible for receiving email for the domain.

2. Step 2: Understand why other records are incorrect

   A records map domain to IP but don't direct email; CNAMEs alias names but don't specify mail routing; TXT records hold text data, not mail routing.

3. Final Answer:

   MX record pointing to your mail server domain -> Option B

4. Quick Check:

   Email routing uses MX records = D [OK]

Hint: Use MX records to route email to mail servers [OK]

Common Mistakes:

• Using A or CNAME records for email routing
• Confusing TXT records with mail routing
• Not specifying mail server domain in MX record