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.

Practice

1. What is the main benefit of duplicating a request in Postman?

easy

A. It exports the request to a file.

B. It saves time by reusing an existing request setup.

C. It merges two requests into one.

D. It deletes the original request automatically.

Solution

1. Step 1: Understand duplicating requests

   Duplicating means making a copy of an existing request to reuse its setup.

2. Step 2: Identify the benefit

   Reusing saves time because you don't have to create the request from scratch.

3. Final Answer:

   It saves time by reusing an existing request setup. -> Option B

4. Quick Check:

   Duplicating = Reuse setup [OK]

Hint: Duplicating means copying to reuse quickly [OK]

Common Mistakes:

• Thinking it deletes the original request
• Confusing duplication with merging requests
• Assuming it exports the request

2. Which of the following is the correct way to duplicate a request in Postman?

easy

A. Rename the request with a new name.

B. Drag the request to the trash bin.

C. Click 'Send' button twice quickly.

D. Right-click the request and select 'Duplicate'.

Solution

1. Step 1: Locate duplication method

   In Postman, duplicating is done by right-clicking the request and choosing 'Duplicate'.

2. Step 2: Eliminate wrong options

   Dragging to trash deletes, clicking send sends request, renaming changes name only.

3. Final Answer:

   Right-click the request and select 'Duplicate'. -> Option D

4. Quick Check:

   Duplicate = Right-click + Duplicate [OK]

Hint: Right-click request to duplicate it [OK]

Common Mistakes:

• Trying to duplicate by clicking send
• Dragging request to trash instead of duplicating
• Thinking renaming duplicates the request

3. Given a collection with requests A, B, and C, you duplicate request B and move the duplicate to a new folder named 'Tests'. What will be the order of requests in the original collection and the new folder?

medium

A. Original collection: A, B, C; New folder: B (duplicate)

B. Original collection: A, C; New folder: B (original and duplicate)

C. Original collection: A, B, C; New folder: empty

D. Original collection: A, B; New folder: C, B (duplicate)

Solution

1. Step 1: Understand duplication effect

   Duplicating request B creates a copy but does not remove the original from the collection.

2. Step 2: Understand moving the duplicate

   Moving the duplicate to 'Tests' folder places only the copy there; original stays in the main collection.

3. Final Answer:

   Original collection: A, B, C; New folder: B (duplicate) -> Option A

4. Quick Check:

   Duplicate copy moved; original stays [OK]

Hint: Duplicate copies; moving affects only the copy [OK]

Common Mistakes:

• Assuming original is removed when duplicate is moved
• Thinking duplicate appears in both places
• Confusing original and duplicate requests

4. You tried to move a request to another folder in Postman but it did not move. What is the most likely reason?

medium

A. You dragged the request outside any folder accidentally.

B. The request is locked and cannot be moved.

C. You duplicated the request instead of moving it.

D. Postman does not support moving requests between folders.

Solution

1. Step 1: Check Postman folder behavior

   Postman allows moving requests by dragging them into folders.

2. Step 2: Identify common mistake

   Dragging outside any folder leaves the request in the original place, so it appears not moved.

3. Final Answer:

   You dragged the request outside any folder accidentally. -> Option A

4. Quick Check:

   Drag inside folder to move [OK]

Hint: Drag request carefully inside target folder [OK]

Common Mistakes:

• Confusing duplication with moving
• Assuming requests can be locked
• Believing Postman disallows moving requests

5. You have a collection with 5 requests. You want to create a new folder and move 3 specific requests into it, but also keep duplicates of those 3 requests in the original collection. What is the correct sequence of actions in Postman?

hard

A. Delete the 3 requests, then create new ones in the folder.

B. Move the 3 requests into the new folder, then duplicate them back to the original collection.

C. Duplicate the 3 requests, then move the duplicates into the new folder.

D. Rename the 3 requests and drag them into the new folder.

Solution

1. Step 1: Understand requirement

   You want duplicates in the new folder and originals to remain in place.

2. Step 2: Choose correct order

   Duplicating first creates copies; moving duplicates places them in the folder without removing originals.

3. Step 3: Eliminate wrong options

   Moving first removes originals from collection; deleting loses data; renaming doesn't duplicate.

4. Final Answer:

   Duplicate the 3 requests, then move the duplicates into the new folder. -> Option C

5. Quick Check:

   Duplicate first, then move duplicates [OK]

Hint: Duplicate first, then move copies to folder [OK]

Common Mistakes:

• Moving first removes originals
• Deleting requests instead of duplicating
• Thinking renaming duplicates requests