Postman Interview Questions and Practice Challenges

# CHAPTER 20

Postman Interview Questions and Practice Challenges #

1. Introduction #

---

2. General API & Protocol Interview Questions #

Q1. What is an API, and why is API testing important? *Answer:* An API (Application Programming Interface) allows different software systems to communicate. Testing is crucial to ensure the backend logic, data formatting, and security protocols function correctly independent of the frontend UI, preventing catastrophic failures in production.

Q2. Explain the difference between GET and POST methods. *Answer:* GET is used to retrieve data from a server and should not alter database state. Parameters are passed in the URL. POST is used to create new data on the server, and the payload is sent securely in the Request Body.

Q3. What is the difference between PUT and PATCH? *Answer:* Both are used for updating data. PUT typically replaces the entire resource (you must send the whole object). PATCH applies a partial update (you only send the fields that need to change).

Q4. Categorize HTTP Status Codes. *Answer:*

• 1xx: Informational

• 2xx: Success (e.g., 200 OK, 201 Created)

• 3xx: Redirection

• 4xx: Client Error (e.g., 400 Bad Request, 404 Not Found)

• 5xx: Server Error (e.g., 500 Internal Server Error)

---

3. Postman Feature Interview Questions #

Q5. What are Postman Environments and Variables? Why use them? *Answer:* Environments allow you to define key-value pairs (variables) like baseUrl or token. They allow testers to switch between Local, Staging, and Production servers instantly without manually rewriting hardcoded URLs.

Q6. Explain the concept of Request Chaining in Postman. *Answer:* Request Chaining is passing data from one response to the next request. You write a script in the "Tests" tab of Request A to extract a value (like an ID) from the JSON response and save it as an Environment Variable. Request B then uses that variable in its URL or Body.

Q7. What is the Collection Runner? *Answer:* A built-in Postman tool that allows you to execute an entire folder or collection of requests sequentially. It is used for automated testing, running workflows, and generating test reports.

Q8. What is Newman? *Answer:* Newman is Postman's command-line Collection Runner. It allows you to run Postman collections directly from the terminal, making it essential for integrating Postman tests into automated CI/CD pipelines (like Jenkins or GitHub Actions).

Q9. What is a Postman Mock Server? *Answer:* A feature that simulates a real API. By saving "Examples" of responses, Postman generates a live URL that returns that fake data, allowing frontend developers to build UIs before the backend is finished.

Q10. How does Collection-level Authorization work? *Answer:* Instead of adding tokens to 50 individual requests, you set the Authentication method on the parent Collection or Folder. You then set all child requests to "Inherit auth from parent", saving time and reducing errors.

---

4. Technical & Scripting Interview Questions #

Q11. How do you parse a JSON response in a Postman test script? *Answer:* By using the built-in function: const response = pm.response.json();

Q12. Write a basic assertion in Postman to check if the status code is 200. *Answer:*

pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
});

Q13. How do you stop a Collection Runner mid-execution if a critical test fails? *Answer:* You use the flow control command: postman.setNextRequest(null); inside your test script.

Q14. How do you safely share a Postman Collection with a team without leaking your personal API keys? *Answer:* Use a Team Workspace. Ensure that any sensitive Environment Variables are only stored in the "Current Value" column (which remains local) and leave the "Initial Value" column (which syncs to the cloud) blank.

---

5. Practice Challenges for Your Portfolio #

To prove your skills, complete these challenges. You can export these Collections and host them on your GitHub as proof of your API QA abilities.

Challenge 1: The Public API Explorer *Task:* Create a Postman Collection that interacts with the public Star Wars API (swapi.dev) or the Pokemon API (pokeapi.co). *Requirements:*

• At least 5 GET requests using Query Parameters for filtering.

• Extensive use of the {{baseUrl}} variable.

• Tests on every request asserting status code 200 and verifying specific data (e.g., "Verify Darth Vader is returned").

Challenge 2: The CRUD Master (JSONPlaceholder) *Task:* Build a complete CRUD workflow using jsonplaceholder.typicode.com. *Requirements:*

• A single folder containing POST, GET, PUT, and DELETE requests.

• Chaining: The POST request must extract the new id and save it to an environment variable. The subsequent requests must use that variable.

• Run the folder in the Collection Runner and verify 100% test passage.

Challenge 3: The Auth Simulator *Task:* Use Postman Mock Servers to simulate an authentication flow. *Requirements:*

• Create a Mock Server endpoint POST /login that returns a fake JSON Web Token.

• Create a second endpoint GET /dashboard.

• Write a test script in /login that saves the fake token.

• Pass the token in the Authorization Header of /dashboard.

Challenge 4: The Markdown Documenter *Task:* Take the Collection you built in Challenge 2. *Requirements:*

• Add detailed Markdown descriptions to the Collection and every Request.

• Save Examples for every request.

• Use the "Publish Docs" feature to generate a live web page. Add the URL to your resume!

---

6. Conclusion #