A network administrator plans a Prisma Access deployment with three service connections, each with a BGP peering to a CPE. The administrator needs to minimize the BGP configuration and management…

Question

Options

• Atarget service connection for traffic steering
• Bsummarized BGP routes before advertising
• Chot potato routing
• Ddefault routing

• A
  3% (1)
• B
  3% (1)
• D
  93% (27)

Explanation

Default routing minimizes CPE-side BGP overhead because each on-prem device only needs to receive (or advertise) a single default route (0.0.0.0/0) from Prisma Access, eliminating the need to manage, maintain, or troubleshoot dozens of specific prefix advertisements across three service connections. When Prisma Access advertises a default route to the CPE, the CPE's BGP configuration stays flat and simple regardless of how the cloud-side topology grows.

Why the distractors are wrong:

• A (target service connection) - Traffic steering via targeted service connections adds policy complexity on the CPE, the opposite of minimizing overhead.
• B (summarized routes) - Summarization reduces route count but still requires the admin to define, maintain, and troubleshoot summary prefixes on each CPE; it doesn't approach the simplicity of a single default.
• C (hot potato routing) - This describes an inter-AS path selection strategy (exit traffic at the nearest point), not a mechanism for reducing BGP config on CPE devices.

Memory tip: Think of it as the "one rule to rule them all" principle - a default route is the ultimate summarization (all destinations in one entry), so CPEs need zero knowledge of what's behind Prisma Access, keeping BGP configs minimal and stable.

No community discussion yet for this question.