Mock server limitations in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Mock Server Response Delays

Which of the following is a true limitation of Postman mock servers regarding response delays?

A Mock servers can simulate delays but only up to a maximum of 10 seconds per response.

B Mock servers can simulate any response delay precisely as configured in the mock settings.

C Mock servers always respond instantly and cannot simulate network latency or delays.

D Mock servers simulate delays randomly without any configuration option.

💡 Hint

Think about whether Postman mock servers can mimic slow network responses by default.

Postman mock servers respond immediately and do not support simulating network latency or response delays. This is a limitation when testing timeout or slow response scenarios.

🧠 Conceptual

intermediate

Mock Server Data Persistence

What is a key limitation of Postman mock servers related to data persistence?

A Mock servers store all request data permanently and can be queried later for history.

B Mock servers do not store any request or response data; each request is stateless and independent.

C Mock servers store request data only for 24 hours before automatic deletion.

D Mock servers store request data but only for requests with specific headers.

💡 Hint

Consider if mock servers keep track of previous requests or responses.

Postman mock servers are stateless and do not persist request or response data. Each request is handled independently without memory of previous calls.

❓ Predict Output

advanced

Mock Server Response Matching Behavior

Given these two mock responses configured in Postman for the same endpoint but different query parameters, what response will the mock server return when called with ?type=admin?

Postman

1. Response A: matches requests with query param type=admin, returns status 200 with body {"role": "admin"}
2. Response B: matches requests with query param type=user, returns status 200 with body {"role": "user"}

A Returns status 200 with body {"role": "admin"}

B Returns status 200 with body {"role": "user"}

C Returns status 404 Not Found because query param type=admin is not supported

D Returns status 500 Internal Server Error due to ambiguous matching

💡 Hint

Think about how Postman mock servers match requests to responses based on query parameters.

Postman mock servers match the request query parameters exactly to the configured mock response. Since the request has type=admin, it matches Response A and returns its body.

❓ assertion

advanced

Assertion on Mock Server Response Headers

You want to write a test in Postman to assert that the mock server response includes the header Content-Type: application/json. Which assertion code snippet is correct?

Postman

pm.test("Content-Type is application/json", () => {
    // Your assertion here
});

A pm.expect(pm.response.headers.contentType).to.eql('application/json');

B pm.expect(pm.response.headers['Content-Type']).to.equal('application/json');

C pm.expect(pm.response.headers.getContentType()).to.equal('application/json');

D pm.expect(pm.response.headers.get('Content-Type')).to.eql('application/json');

💡 Hint

Check the Postman API for how to get header values from the response.

The correct way to get a header value in Postman tests is using pm.response.headers.get('Header-Name'). Option D uses this correctly.

❓ framework

expert

Limitations of Mock Server for Testing Authentication Flows

Which statement best describes a limitation of Postman mock servers when testing authentication flows that require dynamic token generation and validation?

A Mock servers cannot execute server-side logic like token generation or validation; they only return static responses.

B Mock servers can dynamically generate and validate tokens using pre-request scripts and environment variables.

C Mock servers support OAuth2 token validation automatically without additional configuration.

D Mock servers can simulate token expiration by setting response delays and status codes dynamically.

💡 Hint

Consider whether mock servers can run code or logic on the server side.

Postman mock servers only return predefined static responses. They do not run server-side code or logic, so they cannot generate or validate tokens dynamically.