Cloud DNS for domain management in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Cloud DNS handle DNS record updates?

You update a DNS record in Cloud DNS. What happens immediately after the update?

A The update is applied only after the DNS zone is manually reloaded.

B The update propagates gradually based on the TTL of the DNS record.

C The update requires restarting the Cloud DNS service to take effect.

D The update is instantly visible worldwide with zero delay.

💡 Hint

Think about how DNS caching works globally.

DNS updates in Cloud DNS propagate based on the TTL (Time To Live) value of the DNS record. This means changes are not instant worldwide but gradually visible as caches expire.

❓ Architecture

intermediate

Choosing DNS zone type for domain management

You want to manage DNS records for your public website domain using Cloud DNS. Which DNS zone type should you create?

A Forwarding DNS zone to forward queries to another DNS server.

B Private DNS zone to restrict DNS resolution to your internal network.

C Reverse DNS zone to map IP addresses back to domain names.

D Public DNS zone to allow global DNS resolution for your domain.

💡 Hint

Consider if your domain should be visible on the internet.

Public DNS zones are used to manage DNS records for domains accessible globally on the internet. Private zones are for internal networks only.

❓ security

advanced

Securing DNS updates in Cloud DNS

Which method provides the best security to prevent unauthorized DNS record changes in Cloud DNS?

A Use a VPN to connect to Cloud DNS for updates.

B Enable DNSSEC to encrypt DNS record updates.

C Use IAM roles to restrict who can update DNS zones.

D Disable all DNS updates except during business hours.

💡 Hint

Think about controlling access permissions.

IAM roles allow fine-grained control over who can update DNS zones, preventing unauthorized changes. DNSSEC protects DNS data integrity but does not control update permissions.

❓ Configuration

advanced

Configuring a DNS A record for a VM instance

You want to create a DNS A record in Cloud DNS that points app.example.com to the external IP of your VM instance. Which configuration is correct?

A Name: app.example.com., Type: A, TTL: 300, Data: 35.192.0.1

B Name: app, Type: A, TTL: 300, Data: 35.192.0.1

C Name: app.example.com, Type: CNAME, TTL: 300, Data: 35.192.0.1

D Name: app.example.com., Type: A, TTL: 300, Data: app.example.com

💡 Hint

Remember the correct record type and format for IP addresses.

An A record maps a domain name to an IPv4 address. The name must be fully qualified with a trailing dot. CNAME cannot point directly to an IP address.

✅ Best Practice

expert

Designing DNS for high availability and low latency

You want to design Cloud DNS for a global application to ensure high availability and low latency DNS resolution. Which approach is best?

A Use a single public DNS zone and rely on Cloud DNS global anycast infrastructure.

B Create private DNS zones in each region and forward queries to them.

C Manually update DNS records with different IPs based on user location.

D Create multiple public DNS zones with the same domain name in different regions.

💡 Hint

Think about how Cloud DNS handles global traffic.

Cloud DNS uses a global anycast network to serve DNS queries from the nearest location automatically, providing high availability and low latency with a single public DNS zone.

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