Duplicating and moving requests in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the effect of duplicating a request in Postman

When you duplicate a request in Postman, what happens to the original request and the duplicated one?

A Both the original and duplicated requests exist independently; changes to one do not affect the other.

B Duplicating a request merges it with the existing one, combining their settings.

C The original request is deleted and replaced by the duplicate.

D The duplicate request is linked to the original; changes in one update the other automatically.

💡 Hint

Think about whether duplicating creates a copy or a linked reference.

Duplicating a request in Postman creates an independent copy. Both requests exist separately, so changing one does not affect the other.

❓ Predict Output

intermediate

Result of moving a request between collections

You have a request named GetUser in Collection A. You move it to Collection B in Postman. What is the state of GetUser in Collection A after the move?

A The <code>GetUser</code> request remains in Collection A and also appears in Collection B.

B The <code>GetUser</code> request is deleted from both collections.

C The <code>GetUser</code> request is removed from Collection A and appears only in Collection B.

D The <code>GetUser</code> request is duplicated in Collection B but remains linked to Collection A.

💡 Hint

Consider what 'move' means compared to 'copy'.

Moving a request transfers it from one collection to another, removing it from the original collection.

🔧 Debug

advanced

Why does duplicated request keep old environment variables?

You duplicated a request in Postman and moved it to a new collection. However, when running the duplicated request, it still uses environment variables from the original collection's environment. Why?

A Postman duplicates requests but does not duplicate or change the environment; the request uses the currently active environment globally.

B Duplicated requests automatically link to the original environment and cannot be changed.

C The duplicated request copies environment variables but they are hidden and not editable.

D Postman does not allow moving requests between collections with different environments.

💡 Hint

Think about how environments are selected and applied in Postman.

Environments in Postman are selected globally per workspace or window, not per request or collection. Duplicating or moving a request does not change the active environment.

❓ assertion

advanced

Assertion on request count after duplication and move

You start with 3 requests in Collection X. You duplicate one request and then move the duplicated request to Collection Y. How many requests remain in Collection X?

A 1 request

B 2 requests

C 4 requests

D 3 requests

💡 Hint

Remember the order: duplicate first, then move the duplicate.

Duplicating increases Collection X to 4 requests. Moving the duplicated request to Collection Y removes it from Collection X, leaving 3 requests.

❓ framework

expert

Automating duplication and move of requests in Postman via scripting

Which Postman feature or tool allows you to automate duplicating and moving requests between collections programmatically?

A Postman Monitor scheduling feature

B Postman API to programmatically update collections

C Postman Collection Runner with pre-request scripts

D Postman Console logging commands

💡 Hint

Think about how to change collection structure outside the UI.

The Postman API allows programmatic access to collections, enabling automation of duplicating and moving requests by updating collection JSON data.