Custom domain configuration in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a custom domain to your Firebase project.

Firebase

firebase hosting:sites:create [1]

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

Adefault

Bfirebase

Cmy-custom-site

Dproject123

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'firebase' or 'default' as site name

Leaving the site name blank

You need to specify your custom site name when creating a hosting site.

2fill in blank

medium

Complete the command to add a custom domain to your Firebase hosting site.

Firebase

firebase hosting:sites:domain:add [1] example.com

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

Afirebase

Bdefault

Cproject123

Dmy-custom-site

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' instead of the actual site name

Omitting the site name

You must specify the hosting site name where you want to add the custom domain.

3fill in blank

hard

Fix the error in the DNS verification command for Firebase custom domain.

Firebase

firebase hosting:sites:domain:verify [1] example.com

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

Adefault

Bmy-custom-site

Cexample

Dfirebase

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default' or 'firebase' instead of the correct site name

Using the domain name as site name

The verification command requires the exact hosting site name where the domain was added.

4fill in blank

hard

Fill both blanks to configure the DNS records for your custom domain.

Firebase

Add a [1] record pointing to [2] to your domain's DNS settings.

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

AA

BCNAME

Cfirebasehosting.googleapis.com

D199.36.158.100

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME instead of A record

Pointing to the wrong IP or hostname

Firebase requires an A record pointing to the IP address 199.36.158.100 for custom domains.

5fill in blank

hard

Fill all three blanks to complete the Firebase hosting configuration file for your custom domain.

Firebase

{
  "hosting": {
    "site": "[1]",
    "public": "[2]",
    "ignore": ["[3]"]
  }
}

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

Amy-custom-site

Bpublic

Cfirebase.json

Dnode_modules

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong site name

Setting 'public' to wrong folder

Ignoring wrong files

The 'site' is your Firebase hosting site name, 'public' is the folder with your files, and 'ignore' excludes files like 'node_modules'.

Practice

1. What is the main purpose of configuring a custom domain in Firebase Hosting?

easy

A. To enable Firebase Authentication for your app

B. To increase the storage capacity of your Firebase project

C. To create a new Firebase project automatically

D. To use your own website address instead of the default Firebase URL

Solution

1. Step 1: Understand Firebase Hosting default URLs

   Firebase Hosting provides a default URL, but it is not personalized.

2. Step 2: Purpose of custom domain

   Configuring a custom domain lets you use your own website address, making it easier for users to find your site.

3. Final Answer:

   To use your own website address instead of the default Firebase URL -> Option D

4. Quick Check:

   Custom domain = personal website address [OK]

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

Common Mistakes:

• Confusing custom domain with Firebase project storage
• Thinking it enables authentication automatically
• Assuming it creates a new Firebase project

2. Which DNS record type is commonly required to verify domain ownership when setting up a custom domain in Firebase Hosting?

easy

A. CNAME record

B. MX record

C. TXT record

D. A record

Solution

1. Step 1: Identify verification method

   Firebase asks you to add a DNS record to prove you own the domain.

2. Step 2: Common DNS record for verification

   TXT records are used to store text data for verification purposes.

3. Final Answer:

   TXT record -> Option C

4. Quick Check:

   Domain verification uses TXT record [OK]

Hint: Verification usually needs a TXT DNS record [OK]

Common Mistakes:

• Using MX record which is for email routing
• Confusing CNAME with verification record
• Using A record which points IP address

3. You added a CNAME record pointing www.example.com to ghs.googlehosted.com as Firebase instructed. What will happen when users visit www.example.com after DNS propagation?

medium

A. Users will get a DNS error and cannot reach the site

B. Users will see your Firebase hosted website at www.example.com

C. Users will be redirected to Firebase console login page

D. Users will see a default Firebase project page

Solution

1. Step 1: Understand CNAME record purpose

   CNAME points your domain to Firebase Hosting's server address.

2. Step 2: Effect after DNS propagation

   Once DNS updates, visiting www.example.com loads your Firebase hosted site.

3. Final Answer:

   Users will see your Firebase hosted website at www.example.com -> Option B

4. Quick Check:

   CNAME to Firebase = site loads correctly [OK]

Hint: CNAME to Firebase host means your site shows on your domain [OK]

Common Mistakes:

• Expecting DNS error after correct CNAME setup
• Thinking users get Firebase console page
• Assuming default Firebase page shows instead

4. You configured your custom domain but users report your site is not loading. Which of these is the most likely cause?

medium

A. You forgot to verify domain ownership by adding the required DNS record

B. You used an A record instead of a TXT record for verification

C. You deployed your Firebase project without enabling billing

D. You did not enable Firebase Authentication

Solution

1. Step 1: Check domain verification requirement

   Firebase requires domain ownership verification before serving your site.

2. Step 2: Effect of missing verification

   If verification is missing, Firebase will not serve your site on the custom domain.

3. Final Answer:

   You forgot to verify domain ownership by adding the required DNS record -> Option A

4. Quick Check:

   Missing verification = site won't load [OK]

Hint: Always verify domain ownership to activate custom domain [OK]

Common Mistakes:

• Confusing billing with domain verification
• Thinking authentication affects domain setup
• Using wrong DNS record type for verification

5. You want to configure both example.com and www.example.com to serve your Firebase hosted site securely. Which is the best approach?

hard

A. Add both domains in Firebase Hosting, verify ownership for both, and set DNS records accordingly

B. Only add www.example.com in Firebase and redirect example.com to it without verification

C. Add example.com only and rely on Firebase to automatically serve www.example.com

D. Use only example.com and set a CNAME record for www.example.com pointing to example.com

Solution

1. Step 1: Add both domains in Firebase Hosting

   Firebase requires each domain to be added and verified separately.

2. Step 2: Verify ownership and set DNS for both

   You must verify both domains and configure DNS records to point to Firebase Hosting.

3. Step 3: Ensure HTTPS works on both domains

   Firebase provisions SSL certificates for each verified domain to serve securely.

4. Final Answer:

   Add both domains in Firebase Hosting, verify ownership for both, and set DNS records accordingly -> Option A

5. Quick Check:

   Both domains added and verified = secure site on both [OK]

Hint: Add and verify each domain separately for full coverage [OK]

Common Mistakes:

• Assuming Firebase auto-serves unadded domains
• Skipping verification for one domain
• Using CNAME incorrectly for apex domain