During a VMware SD-WAN design session for a core business application, a customer expressed the following requirements: - Allow business abstraction so that similar policies can be applied across…

Question

Options

• ASelect WAN Link, and then define the DSCP tagging
• BSelect Error Correct Before Steering with % definition
• CSelect Transport Group, and then select Preferred option.
• DDeselect Error Correct before Steering Defaults.

• A
  75% (24)
• B
  16% (5)
• C
  3% (1)
• D
  6% (2)

Explanation

Selecting WAN Link with DSCP tagging (A) satisfies all three requirements because DSCP is a protocol-level, hardware-agnostic traffic classification standard - it works identically across different physical hardware and WAN carriers, providing the business abstraction needed without requiring the operations team to understand the underlying connectivity. DSCP is also the industry standard for QoS enforcement, which directly maintains SLA for real-time traffic like voice and video.

Why the distractors are wrong:

• C (Transport Group + Preferred) is the most tempting distractor, but "Preferred" is a best-effort preference, not a guaranteed enforcement mechanism - it fails the SLA requirement for real-time applications.
• B (Error Correct Before Steering) addresses Forward Error Correction (FEC) for packet loss, not traffic classification or business abstraction policy.
• D (Deselect Error Correct Before Steering Defaults) would remove a reliability mechanism, which works directly against maintaining SLA for real-time traffic.

Memory tip: Think "DSCP = application passport" - just like a passport identifies a traveler regardless of which airline or airport they use, DSCP tags identify traffic by application type regardless of the underlying hardware or carrier. If the requirement mentions abstraction + SLA, reach for DSCP.

No community discussion yet for this question.