Environment management in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Environment Variables in Supabase

Which of the following best describes the purpose of environment variables in a Supabase project?

A They store sensitive information like API keys and database URLs securely outside the codebase.

B They are used to write SQL queries directly inside the Supabase dashboard.

C They automatically scale the database storage based on usage.

D They provide a graphical interface to manage user authentication.

💡 Hint

Think about how you keep secrets safe when sharing your project.

Environment variables hold sensitive data such as API keys and database URLs outside the code, keeping them secure and flexible across different environments.

❓ Configuration

intermediate

Configuring Environment Variables for Local Development

You want to run your Supabase project locally with different database credentials than production. Which file should you create or modify to set these environment variables?

A .env.local

B supabase.env

C config.json

D variables.yaml

💡 Hint

Look for the standard file used by many Node.js and frontend projects for local environment variables.

The .env.local file is commonly used to set environment variables for local development, overriding defaults safely.

❓ Architecture

advanced

Managing Multiple Environments in Supabase

You have three environments: development, staging, and production. Which approach best ensures that environment variables do not leak between these environments?

A Store all environment variables in a single project and prefix keys with environment names.

B Use one Supabase project and switch environment variables manually before deployment.

C Use a shared database and rely on user roles to separate data.

D Use separate Supabase projects for each environment, each with its own environment variables.

💡 Hint

Think about isolation and risk of accidental data exposure.

Using separate Supabase projects for each environment isolates environment variables and data, preventing leaks and accidental overwrites.

❓ security

advanced

Protecting Environment Variables in Supabase

Which practice best protects environment variables containing API keys in a Supabase project?

A Share environment variable files via email to team members.

B Never commit environment variable files to version control and use a secrets manager for production.

C Store environment variables directly in the frontend code for easy access.

D Commit environment variable files but encrypt them with a password in the repo.

💡 Hint

Consider how to keep secrets safe from public access and accidental leaks.

Not committing environment files and using a secrets manager keeps sensitive data secure and reduces risk of exposure.

❓ service_behavior

expert

Effect of Changing Environment Variables on Supabase Services

After updating environment variables in the Supabase dashboard for your production project, what is the expected behavior regarding service availability?

A Environment variables cannot be changed once the project is created.

B You must manually restart services to apply the new environment variables, causing downtime.

C Supabase services automatically reload the new environment variables without downtime.

D Environment variable changes only apply after redeploying your frontend application.

💡 Hint

Think about how cloud services handle configuration updates smoothly.

Supabase reloads environment variables automatically to avoid downtime and keep services running smoothly.