Custom domains in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a custom domain in cloud services?

A custom domain is a personalized web address you own, like example.com, that you can link to your cloud-hosted website or service instead of using a default cloud provider URL.

beginner

Why use a custom domain instead of a default cloud URL?

Using a custom domain makes your site easier to remember, builds brand trust, and allows you to control your web address instead of relying on the cloud provider's default URL.

intermediate

What DNS record type is commonly used to point a custom domain to a cloud service?

A CNAME record is often used to point a custom domain or subdomain to a cloud service's URL, while an A record points directly to an IP address.

intermediate

What is SSL and why is it important for custom domains?

SSL (Secure Sockets Layer) encrypts data between users and your site, making it safe. For custom domains, enabling SSL ensures visitors see a secure padlock icon and protects data privacy.

intermediate

How do you verify domain ownership when setting up a custom domain in GCP?

You verify ownership by adding a special TXT record to your domain's DNS settings or uploading a verification file to your website, proving you control the domain.

Which DNS record type is typically used to link a subdomain to a cloud service URL?

A CNAME

B MX

C TXT

D NS

CNAME records map a subdomain to another domain name, commonly used to point to cloud service URLs.

What is the main benefit of using a custom domain for your cloud-hosted website?

A Free SSL certificates

B Faster website loading speed

C Automatic backups

D Easier to remember and brand your site

Custom domains help users remember your site and build your brand identity.

In GCP, how do you prove you own a domain before linking it to your service?

A Add a TXT record to your domain's DNS

B Send an email to Google support

C Create a new VM instance

D Change your domain registrar

Adding a TXT record is a common way to verify domain ownership in GCP.

What does SSL provide for a custom domain website?

A Faster DNS resolution

B Data encryption and security

C Lower hosting costs

D More storage space

SSL encrypts data between the user and website, protecting privacy and security.

Which GCP service helps you manage custom domains for App Engine apps?

A Cloud Functions

B Cloud Storage

C App Engine Custom Domains

D BigQuery

App Engine Custom Domains feature allows you to link your domain to your app.

Explain the steps to set up a custom domain for a website hosted on Google Cloud Platform.

Think about proving you own the domain, then connecting it to your cloud site.

Why is it important to enable SSL when using a custom domain on cloud services?

Consider what happens when data travels over the internet.

Practice

1. What is the primary purpose of setting up a custom domain in Google Cloud Platform (GCP)?

easy

A. To use your own website address instead of a default GCP URL

B. To increase the storage capacity of your GCP project

C. To enable automatic backups for your cloud resources

D. To create virtual machines with custom names

Solution

1. Step 1: Understand what a custom domain is

   A custom domain lets you use your own website address instead of a generic cloud URL.

2. Step 2: Identify the purpose in GCP context

   In GCP, custom domains help users access services with familiar URLs, improving branding and trust.

3. Final Answer:

   To use your own website address instead of a default GCP URL -> Option A

4. Quick Check:

   Custom domain = personal website address [OK]

Hint: Custom domain means your own website address, not default URL [OK]

Common Mistakes:

• Confusing custom domain with storage or VM settings
• Thinking it changes backup or machine names
• Assuming it increases resource limits

2. Which DNS record type must you configure to point your custom domain to a Google App Engine service?

easy

A. MX record

B. TXT record

C. SRV record

D. CNAME record

Solution

1. Step 1: Identify DNS record types for domain pointing

   CNAME records map a domain or subdomain to another domain name, commonly used for pointing to cloud services.

2. Step 2: Match with Google App Engine requirements

   Google App Engine custom domains require CNAME records to link your domain to their service address.

3. Final Answer:

   CNAME record -> Option D

4. Quick Check:

   Point domain to service = CNAME record [OK]

Hint: Use CNAME to point domain to cloud service address [OK]

Common Mistakes:

• Using MX records which are for email routing
• Using TXT records meant for verification
• Confusing SRV records which are for service location

3. Given this snippet configuring a custom domain in GCP App Engine, what will happen if the DNS is not properly set?

gcloud app domain-mappings create example.com --certificate-management=automatic

medium

A. The command will fail with a syntax error

B. The domain will be mapped but users cannot access the app via example.com

C. The app will be accessible immediately without DNS changes

D. The SSL certificate will not be issued

Solution

1. Step 1: Understand domain mapping command effect

   The command creates a domain mapping and requests SSL certificate automatically.

2. Step 2: Consider DNS role in accessibility

   If DNS records do not point to GCP, users cannot reach the app via the custom domain despite mapping.

3. Final Answer:

   The domain will be mapped but users cannot access the app via example.com -> Option B

4. Quick Check:

   Mapping without DNS update = no access [OK]

Hint: Mapping alone doesn't work without DNS pointing [OK]

Common Mistakes:

• Assuming command fails without DNS
• Thinking app is accessible immediately
• Believing SSL won't issue without DNS

4. You tried to add a custom domain to your GCP App Engine app but received an error: "Domain ownership verification failed." What is the most likely cause?

medium

A. You did not add the required TXT record to your domain's DNS

B. You used an incorrect CNAME record type

C. Your App Engine app is not deployed

D. You forgot to enable billing on your GCP project

Solution

1. Step 1: Understand domain ownership verification process

   GCP requires you to prove you own the domain by adding a TXT record to DNS.

2. Step 2: Identify cause of verification failure

   If the TXT record is missing or incorrect, verification fails and domain cannot be added.

3. Final Answer:

   You did not add the required TXT record to your domain's DNS -> Option A

4. Quick Check:

   Missing TXT record = ownership verification fail [OK]

Hint: Verify domain by adding TXT record in DNS [OK]

Common Mistakes:

• Confusing CNAME with TXT for verification
• Assuming app deployment affects verification
• Thinking billing status causes verification error

5. You want to serve your website on both example.com and www.example.com using GCP App Engine with HTTPS. Which setup correctly achieves this with minimal manual DNS management?

hard

A. Map both domains; create TXT records for SSL; manually upload certificates

B. Map only example.com in App Engine; create A record for www pointing to example.com IP; manually manage SSL

C. Map both domains separately in App Engine and create CNAME for www pointing to ghs.googlehosted.com; use automatic SSL

D. Map www.example.com only; create CNAME for example.com pointing to www; disable SSL

Solution

1. Step 1: Understand domain mapping for root and www

   Both example.com and www.example.com need mapping to serve content on both URLs.

2. Step 2: Use recommended DNS and SSL setup

   Google recommends CNAME for www to ghs.googlehosted.com and automatic SSL management for ease and security.

3. Final Answer:

   Map both domains separately in App Engine and create CNAME for www pointing to ghs.googlehosted.com; use automatic SSL -> Option C

4. Quick Check:

   Separate mapping + CNAME + auto SSL = best practice [OK]

Hint: Map both domains and use CNAME for www with auto SSL [OK]

Common Mistakes:

• Using A record for www which is not recommended
• Mapping only one domain and missing the other
• Disabling SSL or managing certificates manually unnecessarily