In which two instances should you use Postman as part of network automation? (Choose two.)

Question

Options

• Ato connect network infrastructure with cloud applications
• Bto write custom scripts in the Python programming language
• Cto receive real-time updates from a device without polling
• Dto perform prototyping of API requests

• A
  70% (23)
• B
  18% (6)
• C
  12% (4)

Explanation

Postman is a GUI-based API testing and development tool, making it ideal for connecting network infrastructure with cloud applications (A) by sending API calls to cloud platforms and network devices, and for prototyping API requests (D) - letting engineers quickly test REST/SOAP calls, inspect responses, and validate payloads before writing any code.

Why the distractors are wrong:

• B (Python scripting): Postman doesn't write Python; it has its own scripting via JavaScript in its test/pre-request tabs. Python automation belongs to tools like requests, Netmiko, or Nornir.
• C (real-time updates without polling): That describes webhooks or WebSockets. Postman is primarily request-driven (you initiate the call); it doesn't natively receive unsolicited push events from devices.

Memory tip: Think of Postman as a "point-and-click API lab bench" - it's for building and testing API interactions (prototyping) and bridging systems together (cloud + network). Anything involving ongoing scripts, code generation, or event-driven updates falls outside its lane.

No community discussion yet for this question.