You must design a low latency WAN link for a new emergency backup site. The traffic contains propriety company information and must be protected. To save computing resources, you cannot encrypt the…

Question

Options

• Apublic
• Bprivate
• Csatellite
• Dwireless

• A
  12% (5)
• B
  77% (33)
• C
  5% (2)
• D
  7% (3)

Explanation

A private WAN (such as MPLS or a leased line) is correct because the physical or logically dedicated infrastructure belongs exclusively to the organization - traffic never traverses the public internet, so it is inherently protected without requiring encryption. This satisfies both the security requirement and the no-encryption constraint simultaneously.

Why the distractors are wrong:

• A (public): A public WAN routes traffic over the shared internet, where unencrypted proprietary data would be fully exposed to interception - directly violating the protection requirement.
• C (satellite): Satellite links introduce high latency (often 500–700 ms round-trip for geostationary), which directly contradicts the low-latency requirement for an emergency backup site.
• D (wireless): Wireless WAN solutions (e.g., cellular/LTE) use shared radio spectrum, so unencrypted traffic can be intercepted; they also lack the reliability guarantees needed for a dedicated backup link.

Memory tip: Think of it as "private = protected by default." Just like a private road doesn't need a fence because strangers can't access it, a private WAN doesn't need encryption because outside parties can't reach the wire.

No community discussion yet for this question.