Monitor scheduling in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Monitor Scheduling Frequency

In Postman Monitor scheduling, what does setting the frequency to every 12 hours mean?

A The monitor runs once a day at 12 PM.

B The monitor runs every 12 minutes.

C The monitor runs twice a day, once every 12 hours.

D The monitor runs every 24 hours twice.

💡 Hint

Think about how many times 12 hours fits into a day.

Setting the frequency to every 12 hours means the monitor runs two times per day, spaced 12 hours apart.

❓ Predict Output

intermediate

Output of Monitor Schedule Setup Code

What will be the result of this Postman Monitor scheduling setup code snippet?

Postman

pm.monitor.schedule({
  interval: 'PT1H',
  timezone: 'UTC'
});
pm.test('Schedule interval test', () => {
  pm.expect(pm.monitor.schedule().interval).to.eql('PT1H');
});

A Test passes because interval is set to 1 hour.

B Test fails because interval is missing.

C Syntax error due to wrong method usage.

D Test fails because timezone is not validated.

💡 Hint

Check if the interval is correctly set and retrieved.

The code sets the monitor schedule interval to 1 hour (PT1H) and the test confirms this value, so the test passes.

❓ assertion

advanced

Correct Assertion for Monitor Next Run Time

Which assertion correctly verifies that the next scheduled run time of a Postman Monitor is in the future?

A pm.expect(new Date(pm.monitor.nextRun)).to.be.below(new Date());

B pm.expect(new Date(pm.monitor.nextRun)).to.be.above(new Date());

C pm.expect(pm.monitor.nextRun).to.eql(new Date());

D pm.expect(pm.monitor.nextRun).to.be.null;

💡 Hint

Think about comparing dates to check if nextRun is after now.

The assertion checks that the nextRun date is greater (in the future) than the current date, which is correct.

🔧 Debug

advanced

Identify the Bug in Monitor Scheduling Script

What is the bug in this Postman Monitor scheduling script?

Postman

pm.monitor.schedule({
  interval: 'PT24H',
  timezone: 'UTC'
});

if(pm.monitor.schedule().interval === 'PT12H') {
  console.log('Monitor runs every 12 hours');
}

A pm.monitor.schedule() cannot be called twice.

B The interval value 'PT24H' is invalid format.

C The timezone 'UTC' is not supported.

D The if condition uses assignment (=) instead of comparison (== or ===).

💡 Hint

Look carefully at the if statement condition.

The if condition mistakenly uses assignment (=) instead of comparison (== or ===), causing a logic error.

❓ framework

expert

Best Practice for Scheduling Monitors in Postman CI/CD Pipeline

In a CI/CD pipeline using Postman Monitors, which scheduling approach ensures tests run only after successful code deployment?

A Trigger the monitor run manually after deployment completes.

B Set the monitor to run daily at midnight.

C Use a fixed schedule and ignore deployment events.

D Schedule the monitor to run every hour regardless of deployment status.

💡 Hint

Consider how to align monitor runs with deployment success.

Triggering the monitor manually after deployment ensures tests run only when new code is deployed, avoiding false failures.