Flow creation in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Postman Flow Execution Order

In Postman Flow, which block executes immediately after the Request block completes successfully?

A The <strong>Start</strong> block triggers the next block regardless of request success

B The <strong>Delay</strong> block placed anywhere in the flow

C The <strong>Condition</strong> block connected to the <strong>Request</strong> block

D The <strong>Request</strong> block itself runs again automatically

💡 Hint

Think about what controls the flow after a request finishes.

In Postman Flow, after a Request block finishes successfully, the connected Condition block executes next to decide the path.

❓ Predict Output

intermediate

Output of a Postman Flow with Delay and Request Blocks

Consider a Postman Flow with a Start block connected to a Delay block set to 2000 ms, which then connects to a Request block that returns status 200. What is the expected behavior?

Postman

Start -> Delay(2000ms) -> Request(status 200)

A The flow fails because Delay cannot be connected before Request

B The flow waits 2 seconds, then sends the request and receives status 200

C The request sends immediately without waiting, then the flow delays 2 seconds

D The flow sends the request twice, once before and once after the delay

💡 Hint

Think about how Delay blocks pause the flow before continuing.

The Delay block pauses the flow for the specified time before passing control to the Request block, which then executes and returns status 200.

❓ assertion

advanced

Correct Assertion for Response Status in Postman Flow

Which assertion correctly checks that a response status code is 201 in a Postman Flow Test block?

A pm.test('Status is 201', () => pm.response.to.have.status(201));

B pm.expect(pm.response.status).toBe(201);

C assert(pm.response.statusCode == 201);

D pm.response.statusCode === 201 ? pass() : fail();

💡 Hint

Use the official Postman assertion syntax.

Option A uses the correct Postman syntax with pm.test and pm.response.to.have.status() to assert the status code.

🔧 Debug

advanced

Debugging a Postman Flow with a Condition Block

A Postman Flow has a Condition block checking if response.status === 200. The flow always takes the false path even when the response status is 200. What is the most likely cause?

A The response object is undefined at the time of condition evaluation

B The condition uses a single equals sign (<code>=</code>) instead of triple equals (<code>===</code>)

C The condition block is not connected to the Request block

D The flow does not support boolean conditions

💡 Hint

Check if the response data is available when the condition runs.

If the response object is undefined, the condition response.status === 200 evaluates to false, causing the flow to take the false path.

❓ framework

expert

Best Practice for Reusing Request Blocks in Postman Flow

In a complex Postman Flow, you want to reuse the same Request block multiple times with different parameters. Which approach ensures maintainability and clarity?

A Use external scripts to call the API instead of Request blocks

B Duplicate the entire flow for each parameter set to avoid changing variables

C Create multiple identical Request blocks with hardcoded parameters for each use

D Use a single Request block with variables for parameters and update variables before each use

💡 Hint

Think about how variables help avoid repetition and ease updates.

Using a single Request block with variables allows changing parameters dynamically, making the flow easier to maintain and clearer.