Seed data management in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Supabase handle seed data execution order?

When running multiple seed files in Supabase, how does the system determine the order in which they execute?

A Supabase runs seed files based on the timestamp inside each file.

B Supabase runs seed files alphabetically by filename.

C Supabase runs seed files in parallel without guaranteed order.

D Supabase runs seed files in the order they were created in the file system.

💡 Hint

Think about how files are usually sorted when listed.

Supabase executes seed files alphabetically by their filename to ensure a predictable order.

❓ Configuration

intermediate

Which command seeds data into a Supabase project?

You want to load seed data into your Supabase database. Which CLI command should you use?

A supabase seed apply

B supabase db seed

C supabase db push

D supabase seed run

💡 Hint

Look for the command that explicitly mentions running seeds.

The correct command to run seed files in Supabase is supabase seed run.

❓ Architecture

advanced

What is the best practice for managing seed data in a team using Supabase?

Your team collaborates on a Supabase project. What is the best way to manage seed data to avoid conflicts and ensure consistency?

A Store seed files in the project repository and run them via CI/CD pipelines.

B Each developer runs their own local seed files independently without sharing.

C Manually insert seed data directly into the production database.

D Use separate seed files for each developer and merge results manually.

💡 Hint

Think about collaboration and automation.

Storing seed files in the repository and running them through CI/CD ensures everyone uses the same data and reduces errors.

❓ security

advanced

What security risk should you avoid when managing seed data in Supabase?

When adding seed data to your Supabase project, which practice can lead to a security risk?

A Using environment variables to store database connection info.

B Encrypting sensitive data before adding it to seed files.

C Including sensitive user credentials or API keys in seed files.

D Limiting seed data to non-sensitive sample records.

💡 Hint

Think about what data should never be in code files.

Seed files should never contain sensitive credentials or keys because they are often stored in version control and accessible to many.

🧠 Conceptual

expert

What happens if a seed file in Supabase contains a SQL error during execution?

You run supabase seed run but one seed file has a syntax error in its SQL. What is the expected behavior?

A The seed process stops immediately and reports the error; no further seed files run.

B The seed process skips the faulty file and continues with the next seed files.

C The seed process ignores errors and completes all seed files regardless.

D The seed process rolls back all previously applied seed files and stops.

💡 Hint

Consider how errors usually affect batch operations.

Supabase stops the seed process on the first error to prevent partial or inconsistent data loading.