200-901 Understanding and Using APIs Practice Question

In Postman, what feature allows you to reuse a value like a base URL or token across multiple requests?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Environments

Environments store variables that can be referenced across requests.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Mock Servers
Why it's wrong here
Mock Servers simulate API responses for testing without a live backend; they store no reusable variables. It is tempting because mocks are configured per collection, and would be correct when front-end teams need fake endpoints before the real API exists.
✗
Workspaces
Why it's wrong here
Workspaces are collaboration containers holding collections, environments and members; they do not themselves define reusable variable values. It is tempting because workspaces do share assets across a team, and would be correct for separating team projects or personal work.
✓
Environments
Why this is correct
Environments store key-value variables, such as a base URL or bearer token, that Postman substitutes into requests via {{variable}} syntax. Switching environments swaps values without editing each request, satisfying the requirement to reuse a value across multiple requests.
✗
Collections
Why it's wrong here
Collections group saved requests and folders, but variable scoping and reuse come from environments, not the collection itself. It is tempting because collections do hold shared request definitions, and would be correct for organising and running related requests together.

Go deeper