What is the recommended approach to scheduling maintenance windows in NPM?

• A. Maintenance windows are optional and require no setup.
• B. Create maintenance windows with durations, applicable devices/groups, and alert suppression rules; plan around changes and inform stakeholders.
• C. Maintenance windows should be avoided at all costs.
• D. Maintenance windows automatically apply to all devices without defining scope.

Answer: (B)

Scheduling maintenance windows in NPM is about controlling alerting during planned changes. The best approach is to create windows with a defined duration, specify the devices or groups affected, and apply alert suppression rules so alerts don’t interrupt work or create noise while maintenance is in progress. This targeted scope lets you coordinate with change plans, allocate time for tasks, and keep stakeholders informed about when changes occur and what to expect. With a defined window and suppression in place, you reduce alert floods and avoid misinterpretation of status, while still preserving visibility for out-of-scope devices or urgent issues. Opting not to set up windows, or making them blanket or automatic for all devices, either creates unnecessary noise or fails to protect the intended scope and communication around the maintenance activity.