You support a retail SD-WAN fabric with 80 WAN Edge routers managed by SD-WAN Manager. Leadership wants an emailed weekly availability summary without manual logins, while the NOC needs immediate notice of tunnel and BFD failures during business hours. Which monitoring and reporting design satisfies both periodic and real-time visibility needs?
Select an answer to reveal the explanation.
Short Explanation
You’re separating the weekly summary from live fault monitoring, so each need gets the right tool. Like a bank statement plus fraud alerts, scheduled reports cover the week while dashboards and alarms surface tunnel faults as they happen.
Full Explanation
The design with scheduled weekly availability reports in SD-WAN Manager and live health dashboards and tunnel fault alarms fits both needs: leadership gets an emailed uptime summary without manual logins, and the NOC can see tunnel and BFD failures during business hours. The weekly inventory-report design fails by report-function concept: inventory covers platform counts, models, and versions, not reachability over time, so it does not provide the requested availability summary. The weekly availability-report design paired with SLA-latency alarms fails by monitoring-domain concept: latency violations indicate performance quality and optimization concerns, not the tunnel and BFD down events the NOC needs to catch. The monthly availability-report design with tunnel and BFD alarms fails by cadence concept: monthly delivery does not meet the explicit weekly reporting requirement, even though the live alarm scope is appropriate. Exam caveat: check report type, delivery method, cadence, and alarm scope as independent requirements; a design can satisfy most of them and still miss the goal. Practical check: confirm SMTP settings, weekly schedule and recipients, and enabled tunnel and BFD alarm rules with business-hours notification, then verify delivery with a test email and a controlled tunnel flap.