A service provider needs to ensure that the NOC is notified proactively in the event that an Edge interface loses connectivity to its WAN provider. Which three methods are available for generating…

Question

Options

• ASlack notification
• BText/SMS
• CPush notification via the VMware SD WAN mobile app
• DSNMP Trap
• EWebhook
• FDyinq Gasp

• A
  2% (1)
• B
  89% (39)
• D
  2% (1)
• E
  7% (3)

Explanation

Text/SMS (B), Push notifications via the VMware SD-WAN mobile app (C), and Dying Gasp (F) are the three native proactive alert methods built into VMware SD-WAN Orchestrator for WAN edge connectivity loss. SMS delivers alerts directly to NOC personnel's phones, the mobile app provides real-time push notifications to operators who have it installed, and Dying Gasp is a VMware SD-WAN-specific mechanism where an Edge device sends a final alert packet to the Orchestrator the moment it detects WAN link failure - before it fully goes offline - making it uniquely proactive.

Why the distractors are wrong:

• A (Slack): Slack is not a native notification channel in VMware SD-WAN Orchestrator; it would require a custom integration (e.g., via API or webhook).
• D (SNMP Trap): While SD-WAN supports SNMP for monitoring/polling, SNMP Traps are not one of the Orchestrator's built-in alert delivery methods for WAN connectivity events.
• E (Webhook): Webhooks are a common integration pattern but are not a native outbound alert mechanism in VMware SD-WAN Orchestrator's alerting configuration.

Memory tip: Think "BSF" - Buzz your phone (SMS), See it on your app (push notification), Final gasp from the dying Edge. The distractor trap is SNMP - it monitors but doesn't alert natively here.

No community discussion yet for this question.