A company performs scheduled database maintenance every Sunday from 02:00 to 04:00 UTC. During these windows, expected performance degradation causes dozens of Instana alerts to fire, overwhelming the on-call team with noise. What is the correct Instana approach to suppress alert notifications specifically during these recurring maintenance periods?

Instana's maintenance window feature allows administrators to define scheduled periods during which alert notifications are suppressed for specified entities, tags, or the entire infrastructure. Maintenance windows can be configured as recurring on a weekly schedule and scoped specifically to the affected database infrastructure. This prevents alert fatigue during planned maintenance without disrupting monitoring for unrelated systems or requiring manual intervention each week. The correct answer is 'Configure a recurring maintenance window in Instana scoped to the database entities and scheduled for Sunday 02:00-04:00 UTC'. The incorrect options — 'Temporarily delete the database alert channels before maintenance begins and recreate them afterward', 'Set all relevant Custom Events to Warning severity before maintenance so they do not trigger on-call pages', 'Disable the monitoring profile for database entities for the duration of each maintenance window' — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 2: Configuration domain of the IBM Instana Observability certification.