Why monitoring ensures API health in Postman - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send a GET request to check API status.

Postman

pm.sendRequest({ url: '[1]', method: 'GET' }, function (err, res) { pm.expect(res).to.have.status(200); });

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

Ahttps://api.example.com/status

Bapi.example.com/status

Chttps://api.example.com

DGET https://api.example.com/status

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting https:// causes request failure

Using method name inside URL

The full URL with protocol is required to send a proper GET request in Postman scripts.

2fill in blank

medium

Complete the code to check if the API response time is less than 200ms.

Postman

pm.test('Response time is acceptable', function () { pm.expect(pm.response.responseTime).to.be.[1](200); });

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

Aequal

BgreaterThan

Cbelow

Dabove

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'above' checks for greater than

Using 'equal' checks for exact match

We want to ensure the response time is below 200 milliseconds for good API health.

3fill in blank

hard

Fix the error in the test that checks if the response body contains the key 'status'.

Postman

pm.test('Response has status key', function () { pm.expect(pm.response.json()).to.have.[1]('status'); });

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

AhaveKey

Binclude

Ccontain

Dproperty

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'contain' or 'include' works for strings or arrays, not object keys

Using 'haveKey' is not a valid Chai method

The correct Chai assertion to check for an object key is 'property'.

4fill in blank

hard

Fill both blanks to create a test that checks if the API response status is 200 and the response time is less than 300ms.

Postman

pm.test('API health check', function () { pm.expect(pm.response).to.have.status([1]); pm.expect(pm.response.responseTime).to.be.[2](300); });

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

A200

Babove

Cbelow

D404

Attempts:

3 left

💡 Hint

Common Mistakes

Using 404 status code means not found error

Using 'above' checks for longer response time

Status code 200 means success, and response time below 300ms means good performance.

5fill in blank

hard

Fill all three blanks to write a test that verifies the response JSON has a 'status' key with value 'ok' and response time less than 250ms.

Postman

pm.test('Complete API health check', function () { const jsonData = pm.response.json(); pm.expect(jsonData).to.have.[1]('status'); pm.expect(jsonData.status).to.eql([2]); pm.expect(pm.response.responseTime).to.be.[3](250); });

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

Aproperty

B'ok'

Cbelow

D'OK'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'OK' instead of 'ok' causes test failure

Using 'include' instead of 'property' for key check

Check the JSON has 'status' key, its value equals 'ok' (case sensitive), and response time is below 250ms.

Practice

1. Why is monitoring important for API health in Postman?

easy

A. It automatically runs tests to check if the API works correctly.

B. It changes the API code to fix errors.

C. It increases the API speed by optimizing servers.

D. It deletes old API data to save space.

Solution

1. Step 1: Understand monitoring purpose

   Monitoring runs tests automatically to check API functionality and performance.

2. Step 2: Identify correct monitoring action

   Only It automatically runs tests to check if the API works correctly. describes running tests to ensure API works correctly.

3. Final Answer:

   It automatically runs tests to check if the API works correctly. -> Option A

4. Quick Check:

   Monitoring runs tests = B [OK]

Hint: Monitoring means automatic checks, not code changes [OK]

Common Mistakes:

• Thinking monitoring changes API code
• Confusing monitoring with server optimization
• Assuming monitoring deletes data

2. Which Postman feature allows you to schedule automatic API tests?

easy

A. Environment

B. Runner

C. Collection

D. Monitor

Solution

1. Step 1: Recall Postman features

   Runner runs tests manually; Monitor schedules automatic tests.

2. Step 2: Match feature to scheduling

   Monitor is the feature designed for scheduled API testing.

3. Final Answer:

   Monitor -> Option D

4. Quick Check:

   Scheduled tests = Monitor [OK]

Hint: Schedule tests? Use Monitor, not Runner [OK]

Common Mistakes:

• Confusing Runner with Monitor
• Thinking Collection schedules tests
• Believing Environment controls scheduling

3. What will happen if a Postman monitor detects a slow API response time?

medium

A. An alert can be sent to notify the team.

B. The monitor will automatically fix the API code.

C. The API will stop working immediately.

D. The monitor will delete the slow response data.

Solution

1. Step 1: Understand monitor response to issues

   Monitors detect problems and send alerts; they do not fix code or delete data.

2. Step 2: Identify correct action on slow response

   Alerts notify the team quickly so they can fix the issue.

3. Final Answer:

   An alert can be sent to notify the team. -> Option A

4. Quick Check:

   Slow response triggers alert = A [OK]

Hint: Monitors alert, they don't fix or delete [OK]

Common Mistakes:

• Assuming monitor fixes API automatically
• Thinking API stops immediately on slow response
• Believing monitor deletes data

4. You set up a Postman monitor but never receive alerts even when the API is down. What is the likely problem?

medium

A. The monitor is not scheduled to run.

B. The API is too fast to trigger alerts.

C. Alerts are not configured properly.

D. The API automatically recovers without alerts.

Solution

1. Step 1: Check monitor scheduling

   If the monitor was not scheduled, tests wouldn't run at all.

2. Step 2: Consider alert configuration

   Not receiving alerts despite failures usually means alert settings are missing or incorrect.

3. Final Answer:

   Alerts are not configured properly. -> Option C

4. Quick Check:

   No alerts = alert config issue [OK]

Hint: No alerts? Check alert settings first [OK]

Common Mistakes:

• Assuming API speed affects alerts
• Thinking API auto-recovers silently
• Ignoring alert configuration

5. How can you use Postman monitoring to improve API reliability over time?

hard

A. By deleting old monitors to save space.

B. By scheduling tests to run regularly and reviewing alert reports to fix issues quickly.

C. By running tests once and ignoring future results.

D. By manually checking API status without automation.

Solution

1. Step 1: Understand monitoring benefits

   Regular tests catch problems early; alerts help fix them fast.

2. Step 2: Identify best practice for reliability

   Scheduling tests and reviewing alerts ensures ongoing API health improvements.

3. Final Answer:

   By scheduling tests to run regularly and reviewing alert reports to fix issues quickly. -> Option B

4. Quick Check:

   Regular tests + alerts = better reliability [OK]

Hint: Regular tests plus alerts improve API health [OK]

Common Mistakes:

• Ignoring continuous monitoring
• Thinking deleting monitors helps reliability
• Relying only on manual checks