Multiple site hosting in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

How does Firebase handle multiple site hosting within a single project?

You have a Firebase project and want to host two different websites under the same project. How does Firebase manage this?

A Firebase requires creating separate projects for each site; multiple sites in one project are not supported.

B Firebase uses different branches in Git to host multiple sites from the same project.

C Firebase merges all site files into one public directory and serves them under different URLs automatically.

D Firebase allows multiple sites by defining separate hosting targets in the firebase.json file, each with its own public directory.

💡 Hint

Think about how configuration files define hosting behavior.

Firebase supports multiple sites in one project by defining multiple hosting targets in the firebase.json file. Each target points to a different folder, allowing separate sites under one project.

❓ Configuration

intermediate

What is the correct firebase.json snippet to host two sites named 'main' and 'blog'?

Choose the firebase.json snippet that correctly configures hosting for two sites: 'main' and 'blog', each with its own folder.

A { "hosting": [ { "target": "main", "public": "main-site" }, { "target": "blog", "public": "blog-site" } ] }

B { "hosting": { "main": { "public": "main-site" }, "blog": { "public": "blog-site" } } }

C { "hosting": { "target": [ "main", "blog" ], "public": [ "main-site", "blog-site" ] } }

D { "hosting": [ { "site": "main", "public": "main-site" }, { "site": "blog", "public": "blog-site" } ] }

💡 Hint

Look for the correct use of 'target' and array structure.

The correct firebase.json uses an array under 'hosting' with objects specifying 'target' and 'public' keys for each site.

❓ service_behavior

advanced

What happens if you deploy multiple sites with overlapping public directories in Firebase?

You configure two hosting targets with the same public directory and deploy both. What is the expected behavior?

A Firebase throws an error during deployment and stops the process due to overlapping directories.

B Firebase deploys both sites successfully, but the last deployed site overwrites the files, causing conflicts.

C Firebase merges the files from both sites and serves a combined site without errors.

D Firebase ignores the second deployment and keeps the first site's files intact.

💡 Hint

Think about file system behavior when writing to the same folder twice.

Deploying multiple sites with the same public directory causes the last deployment to overwrite files, leading to conflicts and unexpected behavior.

❓ security

advanced

How can you restrict access to one of multiple Firebase hosted sites within the same project?

You have two sites hosted in one Firebase project. You want to restrict access to one site only to authenticated users. How can you achieve this?

A Use Firebase Hosting rewrite rules to redirect unauthenticated users to a login page for that site.

B Use Firebase Storage security rules to restrict access to the hosting files.

C Set up separate Firebase projects for each site to apply different security rules.

D Configure Google Cloud IAM roles to block access to the site URL.

💡 Hint

Think about how hosting can control routing and access based on user state.

Firebase Hosting can use rewrite rules combined with Firebase Authentication to restrict access by redirecting unauthenticated users to login pages.

✅ Best Practice

expert

What is the recommended approach to manage environment-specific configurations for multiple Firebase hosted sites in one project?

You have multiple sites hosted in one Firebase project for different environments (dev, staging, production). How should you manage environment-specific settings like API keys or feature flags?

A Use Firebase Remote Config to manage environment variables dynamically for all sites.

B Store all environment configs in one file and use client-side code to select the right config based on URL.

C Use separate hosting targets with different public folders containing environment-specific config files, and deploy accordingly.

D Manually edit the firebase.json file before each deployment to change environment variables.

💡 Hint

Consider how static files and deployment targets can separate environments.

Best practice is to use separate hosting targets with distinct public folders for each environment, each containing its own config files, ensuring clean separation and easy deployment.