Refer to the exhibit. An MSP is designing a solution for a merger of Customer A and Customer B to Customer A's enterprise. Due to overlapping IP addresses and security requirements, the segments…

Question

Exhibit

Options

• A4 segments
• B2 segments
• C6 segments
• D5 segments

• B
  7% (1)
• C
  13% (2)
• D
  80% (12)

Explanation

D is correct because when Customer B is merged into Customer A's enterprise, all of Customer B's segments must be recreated as new segments in the Orchestrator - but the Global Segment already exists by default in Customer A, so it is not counted as "new." If Customer B has 6 total segments (including the Global Segment), then 5 new segments must be configured, covering all of Customer B's non-Global segments that cannot be merged due to IP overlap and security policy conflicts.

Why the distractors fail:

• C (6) is tempting but wrong - it incorrectly counts the Global Segment as a new segment, when it already exists in every VMware SD-WAN enterprise by default.
• A (4) undercounts, likely from misreading the exhibit and missing one segment that must remain isolated.
• B (2) drastically undercounts, perhaps confusing "overlapping-named segments" with the full set that requires new configuration.

Memory tip: "Global is free - subtract one." In VMware SD-WAN MSP merger scenarios, always identify the total segments from the incoming customer, then subtract the Global Segment (it's pre-existing). Whatever remains is your new segment count.

No community discussion yet for this question.