How to implement the relay mode? (Multiple Choice)

Question

Options

• ACross-scheduling is required
• BNo cross-scheduling required
• COn-board processing
• DCross-board processing

• A
  12% (5)
• B
  83% (35)
• D
  5% (2)

Explanation

Relay mode is implemented using no cross-scheduling and on-board processing because it is designed as a lightweight, self-contained forwarding mechanism. The relay node handles data locally (on-board) without needing to coordinate scheduling resources across separate scheduling domains, keeping the implementation simple and low-latency.

Why A is wrong: Cross-scheduling implies coordination between separate scheduling entities, which adds complexity that relay mode is specifically designed to avoid. Relay mode operates independently within its own scheduling domain.

Why D is wrong: Cross-board processing would mean distributing work across multiple hardware boards, which contradicts the on-board nature of relay - the node processes and forwards data using its own local resources only.

Memory tip: Think of relay mode as a self-sufficient runner in a relay race - they carry the baton (data) using their own legs (on-board processing) and don't need to coordinate with other runners mid-stride (no cross-scheduling). If they needed help from others, it wouldn't be a clean relay handoff.

No community discussion yet for this question.