process.env for environment variables in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Node.js code using process.env?

Consider this code snippet that reads environment variables using process.env. What will it print?

Node.js

process.env.TEST_VAR = 'hello';
console.log(process.env.TEST_VAR);

A null

B Throws ReferenceError

C undefined

D "hello"

💡 Hint

Remember that process.env stores environment variables as strings.

The code sets process.env.TEST_VAR to the string "hello" and then logs it. So it prints "hello".

❓ Predict Output

intermediate

What happens if you try to access a non-existent environment variable?

What will this code print if process.env.MY_VAR was never set?

Node.js

console.log(process.env.MY_VAR);

A "" (empty string)

B undefined

C null

D Throws ReferenceError

💡 Hint

Think about what process.env returns for missing keys.

If an environment variable is not set, process.env returns undefined.

❓ component_behavior

advanced

How does changing process.env affect running Node.js code?

If you set process.env.NEW_VAR = '123' inside your Node.js program, what happens to this variable?

A It is available only in the current process and can be accessed anywhere in the code.

B It updates the system environment variables permanently.

C It throws an error because environment variables are read-only.

D It is only available inside the function where it was set.

💡 Hint

Think about the scope of process.env in a running Node.js process.

Setting process.env.NEW_VAR changes the environment variable only for the current Node.js process. It is accessible anywhere in that process but does not affect the system environment.

📝 Syntax

advanced

Which option correctly sets an environment variable in Node.js code?

Choose the correct way to set an environment variable named API_KEY to abc123 inside a Node.js script.

A process.env.API_KEY = 'abc123';

B process.env['API_KEY'] = abc123;

C process.env.API_KEY := 'abc123';

D set process.env.API_KEY = 'abc123';

💡 Hint

Remember how to assign values to object properties in JavaScript.

Option A uses correct JavaScript syntax to assign a string value to process.env.API_KEY. Option A misses quotes around the string, C uses invalid operator, and D uses invalid syntax.

🔧 Debug

expert

Why does this code not print the updated environment variable?

Given this code snippet, why does console.log print undefined instead of the expected value?

Node.js

console.log(process.env.MY_VAR);
process.env.MY_VAR = 'test';

A Because process.env is immutable and throws an error when assigned.

B Because environment variables cannot be changed at runtime.

C Because the environment variable is logged before it is set.

D Because the variable name is case-sensitive and should be lowercase.

💡 Hint

Look at the order of the statements.

The code logs process.env.MY_VAR before it is assigned a value, so it prints undefined. The assignment happens after the log.

Practice

1. What does process.env in Node.js primarily provide access to?

easy

A. File system paths

B. User input from the console

C. Network socket information

D. Environment variables as strings

Solution

1. Step 1: Understand what process.env represents

   process.env is a special object in Node.js that holds environment variables as strings.

2. Step 2: Identify the correct usage context

   It is used to access configuration values or secrets set outside the code, not file paths or user input.

3. Final Answer:

   Environment variables as strings -> Option D

4. Quick Check:

   process.env = environment variables [OK]

Hint: Remember: process.env holds environment variables as strings [OK]

Common Mistakes:

• Thinking process.env reads user input
• Confusing process.env with file system APIs
• Assuming process.env contains numbers or objects

2. Which of the following is the correct way to access an environment variable named API_KEY in Node.js?

easy

A. process.env.API_KEY()

B. process.env['API_KEY']()

C. process.env.API_KEY

D. process.env.get('API_KEY')

Solution

1. Step 1: Recall the syntax for accessing environment variables

   Environment variables in process.env are accessed like object properties, either with dot notation or bracket notation without parentheses.

2. Step 2: Identify the correct syntax

   Using process.env.API_KEY correctly accesses the variable as a string. The other options incorrectly use function call syntax.

3. Final Answer:

   process.env.API_KEY -> Option C

4. Quick Check:

   Access env vars as properties, no parentheses [OK]

Hint: Use dot or bracket notation without () to access env vars [OK]

Common Mistakes:

• Adding parentheses as if env vars are functions
• Using .get() method which doesn't exist
• Confusing bracket notation with function call

3. Consider this Node.js code snippet:

console.log(process.env.PORT || 3000);

If the environment variable PORT is set to 8080, what will be printed?

medium

A. 8080

B. undefined

C. 3000

D. null

Solution

1. Step 1: Understand the logical OR operator usage

   The expression process.env.PORT || 3000 means if process.env.PORT is truthy, use it; otherwise, use 3000.

2. Step 2: Evaluate the value of process.env.PORT

   Since PORT is set to string "8080" (a truthy value), the expression evaluates to "8080".

3. Final Answer:

   8080 -> Option A

4. Quick Check:

   Env var set? Use it; else default [OK]

Hint: If env var exists and is truthy, || returns it [OK]

Common Mistakes:

• Assuming PORT is a number, not a string
• Expecting default 3000 even when PORT is set
• Confusing undefined with null

4. What is the main issue with this code snippet?

const secret = process.env.SECRET_KEY;
console.log(secret.length);

Assuming SECRET_KEY is not set in the environment.

medium

A. It will throw a TypeError

B. It will print undefined

C. It will print 0

D. It will print null

Solution

1. Step 1: Check the value of process.env.SECRET_KEY when unset

   If SECRET_KEY is not set, process.env.SECRET_KEY is undefined.

2. Step 2: Understand what happens calling .length on undefined

   Trying to access length property on undefined causes a TypeError because undefined has no properties.

3. Final Answer:

   It will throw a TypeError -> Option A

4. Quick Check:

   Accessing property on undefined throws TypeError [OK]

Hint: Check if env var exists before accessing properties [OK]

Common Mistakes:

• Assuming undefined has length 0
• Expecting undefined to print as string
• Not handling missing env vars safely

5. You want to safely read an environment variable DB_PASSWORD and provide a default of "defaultPass" if it is missing or empty. Which code snippet correctly does this?

hard

A. const password = process.env.DB_PASSWORD ?? "defaultPass";

B. const password = process.env.DB_PASSWORD ? process.env.DB_PASSWORD : "defaultPass";

C. const password = process.env.DB_PASSWORD ? "defaultPass" : process.env.DB_PASSWORD;

D. const password = process.env.DB_PASSWORD && "defaultPass";

Solution

1. Step 1: Understand the conditional operators for empty strings

   The ?? operator only defaults null/undefined, keeping empty strings. Ternary checks truthiness, defaulting falsy values like empty strings.

2. Step 2: Choose the correct conditional to handle missing or empty strings

   The ternary operator process.env.DB_PASSWORD ? process.env.DB_PASSWORD : "defaultPass" returns the env var if it is a non-empty string (truthy), else the default. This safely handles missing or empty values.

3. Final Answer:

   const password = process.env.DB_PASSWORD ? process.env.DB_PASSWORD : "defaultPass"; -> Option B

4. Quick Check:

   Use ternary to handle empty or missing env vars [OK]

Hint: Use ternary to check for empty or missing env vars [OK]

Common Mistakes:

• Using ?? which allows empty strings through
• Using && which returns wrong value
• Swapping the ternary branches