Collection variables in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Collection Variable Scope

In Postman, you have a collection variable named api_key set to 12345. You also have an environment variable with the same name api_key set to abcde. When you run a request inside this collection, which api_key value will Postman use?

A The environment variable value <code>abcde</code> will be used because environment variables have higher priority than collection variables.

B Postman will randomly pick either <code>12345</code> or <code>abcde</code> each time the request runs.

C Postman will throw an error because variables with the same name cannot exist in collection and environment scopes.

D The collection variable value <code>12345</code> will be used because collection variables override environment variables.

💡 Hint

Remember that Postman uses a specific order to resolve variables, and environment variables have a higher priority than collection variables.

Postman resolves variables by checking environment variables before collection variables. So if a variable exists in both scopes, the environment variable value is used.

❓ query_result

intermediate

Output of Variable Resolution in Pre-request Script

Given the following pre-request script in a Postman collection:

pm.collectionVariables.set('token', 'xyz123');
const tokenValue = pm.variables.get('token');
console.log(tokenValue);

What will be printed in the Postman console when this script runs?

A null

B undefined

C xyz123

D An error is thrown because <code>pm.variables.get</code> cannot access collection variables.

💡 Hint

Check how pm.variables.get resolves variables from different scopes.

pm.variables.get looks through all variable scopes including collection variables, so it finds the token set in collection variables and returns xyz123.

📝 Syntax

advanced

Correct Syntax to Set a Collection Variable

Which of the following Postman scripts correctly sets a collection variable named userId to the value 789?

A pm.collectionVariables['userId'] = 789;

B pm.collectionVariables.set(userId, '789');

C pm.collectionVariables.set('userId' = '789');

D pm.collectionVariables.set('userId', 789);

💡 Hint

Remember the method signature for setting collection variables requires a string key and a value.

The correct syntax uses pm.collectionVariables.set('key', value). Option D follows this exactly.

❓ optimization

advanced

Efficiently Updating Multiple Collection Variables

You want to update three collection variables var1, var2, and var3 with new values 10, 20, and 30 respectively in a pre-request script. Which approach is the most efficient and correct?

A Create an object with all variables and use a loop to set each variable with <code>pm.collectionVariables.set</code>.

B Set variables directly on <code>pm.collectionVariables</code> like properties, e.g., <code>pm.collectionVariables.var1 = 10</code>.

C Use <code>pm.collectionVariables.set</code> once with all variables as an object argument.

D Call <code>pm.collectionVariables.set</code> three times, once for each variable.

💡 Hint

Consider code readability and maintainability when updating multiple variables.

Option A is efficient and clean: it uses a loop to set multiple variables, avoiding repetitive code and ensuring correctness.

🔧 Debug

expert

Debugging Collection Variable Persistence Issue

You set a collection variable sessionId in a test script using pm.collectionVariables.set('sessionId', 'abc123');. However, after the request finishes, the variable sessionId is not saved and disappears. What is the most likely reason?

A The collection variable name <code>sessionId</code> is reserved and cannot be used.

B Collection variables set in test scripts are not saved persistently unless you explicitly save the collection.

C You must use <code>pm.variables.set</code> instead of <code>pm.collectionVariables.set</code> to persist variables.

D Collection variables set in scripts are saved only if the Postman app is running in offline mode.

💡 Hint

Think about how Postman handles variable persistence and saving collections.

Collection variables set during runtime are saved in memory but not persisted to disk unless you save the collection manually. This is why the variable disappears after the request.