Creating mock servers in Postman - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a mock server in Postman using the correct method.

Postman

pm.mockServer.[1]({ url: 'https://api.example.com', name: 'Test Mock' });

Drag options to blanks, or click blank then click option'

Acreate

Bdelete

Cupdate

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' instead of 'create' will try to remove a server.

Using 'fetch' is for getting data, not creating.

The create method is used to create a new mock server in Postman.

2fill in blank

medium

Complete the code to set the mock server's environment variable correctly.

Postman

pm.environment.set('[1]', 'mock_server_id');

Drag options to blanks, or click blank then click option'

AmockServerUrl

BmockUrl

CserverName

DmockServerId

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mockServerUrl' stores the URL, not the ID.

Using 'serverName' is not specific enough.

The environment variable mockServerId is commonly used to store the mock server's unique ID.

3fill in blank

hard

Fix the error in the code to correctly send a mock response with status 200.

Postman

pm.mockServer.sendResponse({ status: [1], body: { message: 'Success' } });

Drag options to blanks, or click blank then click option'

A'OK'

B'200'

C200

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using '200' as a string causes errors.

Using 'OK' is a status text, not a code.

The status code should be a number 200, not a string or other type.

4fill in blank

hard

Fill both blanks to create a mock server and assign its ID to an environment variable.

Postman

const mockServer = pm.mockServer.[1]({ url: 'https://api.test.com' });
pm.environment.set('[2]', mockServer.id);

Drag options to blanks, or click blank then click option'

Acreate

Bdelete

CmockServerId

DmockServerUrl

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' instead of 'create' will remove servers.

Storing the URL instead of the ID causes confusion.

Use create to make the mock server, and store its ID in mockServerId.

5fill in blank

hard

Fill all three blanks to define a mock response with status 201, a JSON body, and a header.

Postman

pm.mockServer.sendResponse({ status: [1], body: [2], headers: [3] });

Drag options to blanks, or click blank then click option'

A201

B{\"id\": 123, \"status\": \"created\"}

C[{ key: 'Content-Type', value: 'application/json' }]

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using status 200 instead of 201 for creation.

Not formatting headers as an array of objects.

Status 201 means resource created, the body is a JSON string, and headers include content type.

Practice

1. What is the main purpose of creating a mock server in Postman?

easy

A. To monitor live API traffic

B. To deploy the real API to production

C. To write code for the backend server

D. To simulate API responses without needing the actual backend

Solution

1. Step 1: Understand what a mock server does

   A mock server simulates API responses so developers can test without a real backend.

2. Step 2: Compare options with this purpose

   Only To simulate API responses without needing the actual backend describes simulating responses without the actual backend.

3. Final Answer:

   To simulate API responses without needing the actual backend -> Option D

4. Quick Check:

   Mock server purpose = simulate API responses [OK]

Hint: Mock servers simulate, not deploy or write backend code [OK]

Common Mistakes:

• Confusing mock servers with real backend deployment
• Thinking mock servers monitor live traffic
• Assuming mock servers generate backend code

2. Which of the following is the correct step to create a mock server in Postman?

easy

A. Select a collection, then click 'Mock Server' and configure settings

B. Write backend code and deploy it to Postman

C. Create a new environment and add variables

D. Run the collection in the runner without any setup

Solution

1. Step 1: Identify how to create a mock server

   In Postman, mock servers are created from collections by selecting 'Mock Server' option.

2. Step 2: Check which option matches this process

   Select a collection, then click 'Mock Server' and configure settings correctly describes selecting a collection and clicking 'Mock Server'.

3. Final Answer:

   Select a collection, then click 'Mock Server' and configure settings -> Option A

4. Quick Check:

   Create mock server = select collection + 'Mock Server' [OK]

Hint: Mock servers start from collections, not environments or code [OK]

Common Mistakes:

• Confusing environment setup with mock server creation
• Thinking mock servers require backend code
• Trying to run collections without mock server setup

3. Given this Postman mock server setup:

{
  "method": "GET",
  "url": "/user/123",
  "response": {
    "status": 200,
    "body": "{\"id\":123, \"name\": \"Alice\"}"
  }
}

What will the mock server return when a GET request is made to /user/123?

medium

A. HTTP 404 Not Found error

B. HTTP 200 with body {"id":123, "name": "Alice"}

C. HTTP 500 Internal Server Error

D. No response because URL is incorrect

Solution

1. Step 1: Analyze the mock server response setup

   The mock server is set to respond to GET /user/123 with status 200 and JSON body {"id":123, "name": "Alice"}.

2. Step 2: Match the request and response

   A GET request to /user/123 matches the mock setup, so it returns status 200 and the JSON body.

3. Final Answer:

   HTTP 200 with body {"id":123, "name": "Alice"} -> Option B

4. Quick Check:

   Matching URL + method = 200 + JSON body [OK]

Hint: Match method and URL exactly to get mock response [OK]

Common Mistakes:

• Assuming 404 if unsure about URL matching
• Confusing status codes for mock responses
• Ignoring the method type in mock setup

4. You created a mock server but when sending requests, you always get a 404 error. What is the most likely cause?

medium

A. The request method is POST but mock expects GET

B. The mock server is down due to network issues

C. The mock server URL does not match the request URL

D. The collection has no example responses defined

Solution

1. Step 1: Understand 404 in mock server context

   A 404 means the mock server did not find a matching request URL and method.

2. Step 2: Identify common causes for 404

   If the request URL does not exactly match the mock server URL, 404 occurs. This is the most common cause.

3. Final Answer:

   The mock server URL does not match the request URL -> Option C

4. Quick Check:

   404 error = URL mismatch [OK]

Hint: Check exact URL match to fix 404 errors on mock servers [OK]

Common Mistakes:

• Assuming network issues cause 404
• Forgetting to add example responses in collection
• Ignoring HTTP method mismatch

5. You want to create a mock server that returns different responses based on query parameters. Which approach should you use in Postman?

hard

A. Create multiple example requests in the collection with different query parameters and responses

B. Write JavaScript code in the mock server to handle query parameters

C. Use environment variables to change the mock server URL dynamically

D. Create separate mock servers for each query parameter value

Solution

1. Step 1: Understand how Postman mock servers handle query parameters

   Postman mock servers match requests to example requests including query parameters to return the correct response.

2. Step 2: Identify the best way to handle different query parameters

   Creating multiple example requests with different query parameters and responses allows the mock server to return varied responses.

3. Final Answer:

   Create multiple example requests in the collection with different query parameters and responses -> Option A

4. Quick Check:

   Multiple examples = varied responses by query [OK]

Hint: Use multiple examples with query params for varied mock responses [OK]

Common Mistakes:

• Thinking mock servers run custom code
• Trying to change mock URL with environment variables
• Creating many mock servers instead of examples