Creating storage buckets in Supabase - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new storage bucket named 'photos'.

Supabase

const { data, error } = await supabase.storage.[1]('photos');

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

AdeleteBucket

BcreateBucket

ClistBuckets

DgetBucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using deleteBucket instead of createBucket.

Using listBuckets which only lists existing buckets.

The createBucket method is used to create a new storage bucket in Supabase.

2fill in blank

medium

Complete the code to make the new bucket public.

Supabase

const { data, error } = await supabase.storage.createBucket('photos', { [1]: true });

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

Apublic

Breadonly

Csecure

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'private' which restricts access.

Using 'readonly' which is not a valid option here.

Setting public to true makes the bucket accessible publicly.

3fill in blank

hard

Fix the error in the code to list all storage buckets.

Supabase

const { data, error } = await supabase.storage.[1]();

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

AlistBuckets

BgetBucket

CcreateBucket

DdeleteBucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using createBucket which creates a bucket instead of listing.

Using getBucket which requires a bucket name.

The listBuckets method returns all storage buckets.

4fill in blank

hard

Fill both blanks to delete a bucket named 'archive'.

Supabase

const { data, error } = await supabase.storage.[1]('[2]');

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

AdeleteBucket

BcreateBucket

Carchive

Dphotos

Attempts:

3 left

💡 Hint

Common Mistakes

Using createBucket instead of deleteBucket.

Using the wrong bucket name.

Use deleteBucket to remove a bucket. The bucket name here is 'archive'.

5fill in blank

hard

Fill all three blanks to update a bucket named 'documents' to be private.

Supabase

const { data, error } = await supabase.storage.[1]('[2]', { [3]: false });

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

AupdateBucket

Bdocuments

Cpublic

DcreateBucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using createBucket instead of updateBucket.

Setting 'public' to true instead of false.

The updateBucket method changes bucket settings. Setting public to false makes it private.

Practice

1. What is the main purpose of creating a storage bucket in Supabase?

easy

A. To send emails automatically

B. To run server-side code

C. To create a database table

D. To organize and protect files in the cloud

Solution

1. Step 1: Understand storage bucket purpose

   A storage bucket is used to hold and organize files securely in the cloud.

2. Step 2: Compare options

   Options B, C, and D describe other services not related to file storage.

3. Final Answer:

   To organize and protect files in the cloud -> Option D

4. Quick Check:

   Storage bucket = organize and protect files [OK]

Hint: Buckets store files safely in the cloud [OK]

Common Mistakes:

• Confusing buckets with databases
• Thinking buckets run code
• Assuming buckets send emails

2. Which is the correct way to create a private storage bucket named photos in Supabase?

easy

A. supabase.storage.createBucket('photos', { access: 'private' })

B. supabase.storage.createBucket('photos', { public: false })

C. supabase.storage.createBucket('photos', { private: true })

D. supabase.storage.createBucket('photos', { isPublic: true })

Solution

1. Step 1: Recall correct method signature

   The method createBucket takes the bucket name and an options object with a public boolean.

2. Step 2: Identify correct privacy option

   Setting public: false makes the bucket private. Other options use incorrect keys.

3. Final Answer:

   supabase.storage.createBucket('photos', { public: false }) -> Option B

4. Quick Check:

   Use public: false for private bucket [OK]

Hint: Use public: false to make bucket private [OK]

Common Mistakes:

• Using wrong option keys like isPublic or private
• Setting public: true for private buckets
• Confusing access property with public

3. What will be the result of this code snippet?

const { data, error } = await supabase.storage.createBucket('docs', { public: true });
console.log(data);

medium

A. An error because 'public' is not a valid option

B. Undefined because createBucket returns nothing

C. An object with bucket details including name 'docs' and public true

D. A boolean true indicating success

Solution

1. Step 1: Understand createBucket return value

   The method returns an object with bucket info if successful, including name and public status.

2. Step 2: Analyze the code output

   Since public: true is valid, data will contain bucket details, not an error or boolean.

3. Final Answer:

   An object with bucket details including name 'docs' and public true -> Option C

4. Quick Check:

   createBucket returns bucket info object [OK]

Hint: createBucket returns bucket info object on success [OK]

Common Mistakes:

• Thinking it returns only true/false
• Assuming it throws error for public option
• Expecting no return value

4. You wrote this code but get an error:

await supabase.storage.createBucket('files', { public: 'no' });

What is the likely cause?

medium

A. The 'public' option must be a boolean, not a string

B. Bucket name 'files' is invalid

C. createBucket requires a callback function

D. Missing await keyword before createBucket

Solution

1. Step 1: Check option types

   The public option expects a boolean true or false, not a string.

2. Step 2: Identify error cause

   Passing 'no' as a string causes a type error. Bucket name and await usage are correct.

3. Final Answer:

   The 'public' option must be a boolean, not a string -> Option A

4. Quick Check:

   public option = boolean, not string [OK]

Hint: Use true/false for public, not strings [OK]

Common Mistakes:

• Passing 'yes' or 'no' as strings
• Ignoring await keyword
• Using invalid bucket names

5. You want to create two buckets: one public named images and one private named backups. Which code correctly does this?

hard

A. await supabase.storage.createBucket('images', { public: true }); await supabase.storage.createBucket('backups', { public: false });

B. await supabase.storage.createBucket('images', { public: false }); await supabase.storage.createBucket('backups', { public: true });

C. await supabase.storage.createBucket('images'); await supabase.storage.createBucket('backups');

D. await supabase.storage.createBucket('images', { access: 'public' }); await supabase.storage.createBucket('backups', { access: 'private' });

Solution

1. Step 1: Set correct privacy flags

   Public bucket needs public: true, private bucket needs public: false.

2. Step 2: Verify method calls

   await supabase.storage.createBucket('images', { public: true }); await supabase.storage.createBucket('backups', { public: false }); correctly sets these flags. await supabase.storage.createBucket('images', { public: false }); await supabase.storage.createBucket('backups', { public: true }); reverses them. await supabase.storage.createBucket('images'); await supabase.storage.createBucket('backups'); omits privacy, defaulting to private. await supabase.storage.createBucket('images', { access: 'public' }); await supabase.storage.createBucket('backups', { access: 'private' }); uses invalid keys.

3. Final Answer:

   await supabase.storage.createBucket('images', { public: true }); await supabase.storage.createBucket('backups', { public: false }); -> Option A

4. Quick Check:

   Public = true, Private = false [OK]

Hint: Public bucket: public true; Private bucket: public false [OK]

Common Mistakes:

• Mixing up public true/false
• Omitting privacy option
• Using wrong option keys like access