What is the limitation of using a legacy proxy compared to Netskope's solution?

The correct answer is D. To enforce policies, traffic needs to traverse back through a customer's on-premises security. A limitation of using a legacy proxy compared to Netskope's solution is that to enforce policies, traffic needs to traverse back through a customer's on-premises security stack. This creates latency, bandwidth, and scalability issues for remote users and cloud applications…

Netskope Security Service Edge (SSE) Overview and Deployment

Question

Options

ANetskope architecture requires on-premises components.
BLegacy solutions offer higher performance and scalability for corporate and remote users.
CLegacy on-premises solutions fail to provide protection for traffic from on-premises users.
DTo enforce policies, traffic needs to traverse back through a customer's on-premises security

How the community answered

(23 responses)

A
4% (1)
B
13% (3)
C
9% (2)
D
74% (17)

Explanation

A limitation of using a legacy proxy compared to Netskope's solution is that to enforce policies, traffic needs to traverse back through a customer's on-premises security stack. This creates latency, bandwidth, and scalability issues for remote users and cloud applications. Netskope's solution, on the other hand, leverages a cloud-native architecture that provides high-performance and scalable inspection of traffic from any location and device.

Topics

#legacy proxy#traffic hairpinning#cloud architecture#SSE

Community Discussion

No community discussion yet for this question.

Full NSK101 Practice