Storage bucket structure in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Firebase Storage Bucket Paths

In Firebase Storage, which of the following paths correctly represents a file stored inside a user's folder named 'user123' under a folder 'images'?

A images//user123//profile.png

B user123/images/profile.png

C /images/user123/profile.png

D images/user123/profile.png

💡 Hint

Think about the typical folder structure and how slashes separate folders and files.

Option D correctly shows the path with 'images' as the main folder, then 'user123' as a subfolder, and 'profile.png' as the file. Option D reverses the folder order. Option D has an extra leading slash which is invalid. Option D has double slashes which are not valid in Firebase Storage paths.

❓ Architecture

intermediate

Best Practice for Organizing User Files in Firebase Storage

You want to store profile pictures and documents for each user in Firebase Storage. Which bucket folder structure below is best for easy management and security rules?

A users/{userId}/profile_pictures/ and users/{userId}/documents/

B profile_pictures/{userId}/ and documents/{userId}/

C {userId}/profile_pictures/ and {userId}/documents/

D profile_pictures_and_documents/{userId}/

💡 Hint

Consider how security rules can be applied per user and per file type.

Option A clearly separates user data under 'users/{userId}' with subfolders for file types, making it easy to write security rules per user and file type. Option A splits by file type first, which can complicate user-based rules. Option A uses userId as top folder but lacks a parent folder grouping users. Option A mixes file types in one folder, making management harder.

❓ security

advanced

Firebase Storage Security Rule for User Folder Access

Given the bucket structure 'users/{userId}/files/', which Firebase Storage security rule snippet correctly allows only the authenticated user to read and write their own files?

Firebase

service firebase.storage {
  match /b/{bucket}/o {
    match /users/{userId}/files/{fileId} {
      allow read, write: if ... ;
    }
  }
}

A true

B request.auth == null

C request.auth != null && request.auth.uid == userId

D request.auth.uid != null && request.auth.uid != userId

💡 Hint

Check how to compare the authenticated user's ID with the folder userId.

Option C correctly checks that the user is authenticated and their UID matches the userId in the path, allowing access only to their own files. Option C denies access because it checks for inequality. Option C allows unauthenticated access which is insecure. Option C allows everyone access, which is insecure.

❓ service_behavior

advanced

Effect of Folder Naming on Firebase Storage Performance

Which statement best describes how naming many files directly under the root bucket folder affects Firebase Storage performance?

A Storing many files directly under root can slow down listing operations due to large flat namespace.

B Firebase Storage automatically indexes all files, so performance is unaffected by folder structure.

C Files must be stored in nested folders; root folder cannot contain files.

D Performance improves when all files are in the root folder because no folder traversal is needed.

💡 Hint

Think about how many files in one folder affect listing speed.

Option A is correct because having many files in one folder can slow down listing operations. Firebase Storage uses a flat namespace but simulates folders with prefixes. Option A is incorrect because indexing does not eliminate performance impact. Option A is false; files can be stored at root. Option A is false; large flat namespaces can degrade performance.

✅ Best Practice

expert

Optimal Bucket Structure for Multi-Region Firebase Storage Access

You have users worldwide and want to optimize Firebase Storage bucket structure for low latency and compliance. Which approach is best?

A Use a single global bucket and rely on Firebase CDN to cache files worldwide.

B Create separate buckets per region (e.g., us-central1, europe-west1) and route users to nearest bucket.

C Store all files in one bucket but prefix folders by region (e.g., us-central1/, europe-west1/).

D Create buckets per user regardless of region to isolate data.

💡 Hint

Consider latency and data residency requirements.

Option B is best because separate buckets per region reduce latency by storing data physically closer to users and help meet compliance rules. Option B relies on CDN but may not satisfy data residency. Option B prefixes folders but data is still stored in one region, so latency and compliance issues remain. Option B creates too many buckets, increasing complexity and cost.