Instructions and covered skills
Read each scenario carefully before selecting an answer. Focus on the stated Postman behavior, request context, and expected API result. Choose the response that best fits the scenario rather than relying on assumptions from a different tool. Keep notifications and unrelated browser tabs closed while working. Review variable scope and script timing when a question includes dynamic data. Work steadily and reserve time to verify your choices before submitting.
Key Areas
This test covers the practical skills used to build, validate, and maintain API checks in Postman. Candidates work with request methods, URL parameters, headers, request bodies, authorization settings, and response inspection. They should understand how to organize related endpoints into collections and folders, apply shared settings, and use request-level settings when an endpoint requires a deliberate override.
Script coverage includes writing Postman JavaScript with the pm API. Relevant tasks include checking response status codes, reading JSON payloads, validating headers, evaluating response times, and setting variables from returned data. The test also addresses pre-request scripting for values that must exist before a request is sent, such as timestamps, generated identifiers, or refreshed tokens.
Variable management is a central area. Candidates should distinguish local, data, environment, collection, and global values, recognize their precedence, and select an appropriate scope for configuration and test data. They should also understand how collection runs consume CSV or JSON data files, how request order can affect stateful workflows, and how saved examples and documentation support team use.
Automation topics include executing collections with the Collection Runner and Newman, passing environment files, supplying data files, reporting failures, and using exit codes in delivery pipelines. The assessment emphasizes assertions that are specific enough to detect defects while remaining stable when valid response details vary.
Recommended Preparation
Prepare by creating a Postman collection for a public or internal API. Configure an environment with a base URL and credentials, then build requests that create, retrieve, update, and remove test records. Add assertions for status codes, content types, required JSON fields, expected values, and response timing. Practice extracting an identifier or token from one response and reusing it in a later request.
Review the Postman Sandbox reference, especially pm.test, pm.expect, pm.response, pm.variables, and the environment and collection variable APIs. Run a collection with a CSV or JSON data file, then execute it through Newman and inspect the resulting output. Finally, practice diagnosing common failures such as unresolved variables, authorization inheritance issues, malformed JSON, and assertions that execute at the wrong stage of a request.