What is one challenge distributed enterprises face with traditional branch architecture?

Question

Options

• AA traditional branch architecture unifies security policies centrally, which frustrates local IT staff
• BA traditional branch architecture does not support a WAN established over MPLS, which is the
• CTraditional branches do not have enough separate hardware devices for customers to meet
• DIn a traditional architecture, all branch traffic has to be routed through the datacenter to get the

• A
  7% (2)
• B
  17% (5)
• C
  3% (1)
• D
  72% (21)

Explanation

Option D is correct because in traditional branch architectures, all traffic - including internet-bound traffic - is backhauled through the central datacenter for security inspection and policy enforcement before being sent to its destination. This creates latency, inefficiency, and bottlenecks, especially as cloud application usage grows and branches need direct internet access.

Why the distractors are wrong:

• A is false because traditional architectures typically struggle with inconsistent security policies across branches, not centralized ones frustrating local staff - centralized policy is actually a goal.
• B is false because MPLS is one of the most common WAN technologies used with traditional branch architectures; lack of MPLS support is not a recognized challenge.
• C is fabricated - traditional branches often have too many separate hardware devices (firewalls, routers, WAN optimizers), which is actually a cost/complexity complaint, not a shortage.

Memory tip: Think of the datacenter as a mandatory highway toll booth - every branch car (packet) must detour through it before reaching its destination, even if the destination is just across the street (the internet). This "tromboning" effect is the classic pain point that SD-WAN and SASE architectures were designed to solve.

No community discussion yet for this question.