Which xAPI access mechanism requires separate connections for commands and notifications?

Question

Options

• ASerial
• BWebSocket
• CHTTP/HTTPS
• DSSH

• A
  11% (3)
• B
  7% (2)
• C
  4% (1)
• D
  78% (21)

Explanation

SSH requires two separate connections when using Cisco's xAPI: one connection handles commands (xCommands and xConfigurations), while a second, independent connection is needed to receive asynchronous notifications and feedback (xFeedback subscriptions). This split-connection architecture is a defining characteristic of SSH-based xAPI access.

Why the distractors are wrong:

• WebSocket (B) uses a single persistent, full-duplex connection that handles both commands and real-time notifications simultaneously - no second connection needed.
• HTTP/HTTPS (C) is a request-response protocol where you poll for status or use webhooks; it doesn't have a dedicated separate notification channel in the same architectural sense.
• Serial (A) provides a single bidirectional channel over a direct physical link, handling both directions on one connection.

Memory tip: Think of SSH as "Separate Handling Shell" - it separates command input from notification output into two distinct connections, unlike WebSocket which keeps everything on one wire.

No community discussion yet for this question.