What are two ways service connections and remote network connections differ? (Choose two.)

Question

Options

• ARemote network connections provide secondary WAN options, but service connections use
• BRemote network connections enforce security policies, but service connections do not.
• CAn on-premises resource cannot originate a connection to the internet over a service connection.
• DService connections support both OSPF and BGP for routing protocols, but remote networks

• A
  71% (25)
• B
  14% (5)
• C
  6% (2)
• D
  9% (3)

Explanation

Option A is correct because remote network connections support secondary (backup) WAN links for redundancy at branch sites, whereas service connections - designed to connect headquarters or data centers to Prisma Access - do not offer this secondary WAN failover option. This reflects their different design purposes: remote networks serve distributed branch offices needing resilience, while service connections assume more reliable, enterprise-grade HQ connectivity.

Why the distractors are wrong:

• B is incorrect because both connection types route traffic through Prisma Access and are subject to its security policy enforcement - service connections are not a policy-free path.
• C is incorrect because on-premises resources can originate internet-bound traffic over a service connection; directing HQ internet traffic through Prisma Access is actually a common use case for service connections.
• D is cut off in the text, but in Prisma Access, remote network connections support BGP (and static routes), while service connections use BGP - the routing protocol story doesn't cleanly favor service connections having more options.

Memory tip: Think of Remote = Redundant (branch offices get backup WAN links because they're more vulnerable to single-ISP failures), while Service = Stable single path to your trusted HQ. The word "remote" hints at the need for resilience in less-controlled environments.

No community discussion yet for this question.