NSK300 practice question 10 of 15

You are building an architecture plan to roll out Netskope for on-premises devices. You determine that tunnels are the best way to achieve this task…

Full set: 60 questions
You are building an architecture plan to roll out Netskope for on-premises devices. You determine that tunnels are the best way to achieve this task due to a lack of support for explicit proxy in some instances and IPsec is the right type of tunnel to achieve the desired security and steering. What are three valid elements that you must consider when using IPsec tunnels in this scenario? (Choose three.)
Answer options
A: cipher support on tunnel-initiating devices Correct answer
B: bandwidth considerations Correct answer
C: the categories to be blocked
D: the impact of threat scanning performance
E: Netskope Client behavior when on-premises Correct answer
Correct Answer:
A. cipher support on tunnel-initiating devices; B. bandwidth considerations; E. Netskope Client behavior when on-premises
Explanation

When creating an architecture plan for steering on-premises traffic to Netskope via IPsec tunnels, several core infrastructure and configuration elements must be considered.
1. Cipher Support (A): IPsec tunnels rely on a negotiated set of cryptographic algorithms (ciphers) for security. The on-premises device initiating the tunnel (e.g., firewall, router) must support ciphers compatible with the Netskope NewEdge network to establish a connection.
2. Bandwidth Considerations (B): The IPsec tunnel will carry all steered traffic. The architecture plan must account for the total bandwidth required to avoid performance bottlenecks on the local internet egress and ensure the tunnel's capacity is sufficient for the user load.
3. Netskope Client Behavior (E): In environments where the Netskope Client is also deployed, its behavior on the corporate network is a critical architectural consideration. The client must be configured with on-premises detection to disable its own steering and prevent conflicts with the network-level IPsec tunnel.

Why Incorrect

C. the categories to be blocked: This is a security policy decision that is configured in Netskope after traffic is successfully steered; it does not affect the tunnel's architectural setup.
D. the impact of threat scanning performance: This relates to the performance of the Netskope cloud service itself, not a direct architectural element of establishing the IPsec tunnel that transports the traffic.

References

1. Cipher Support: Official Netskope documentation specifies the required IKEv1 and IKEv2 parameters, including supported encryption and integrity algorithms. A mismatch prevents tunnel establishment.

Source: Netskope Technical Documentation, "IPsec". The section "IKEv1 Parameters" and "IKEv2 Parameters" lists the specific supported ciphers (e.g., AES-256-GCM, SHA256) that the on-premises device must support.

2. Bandwidth Considerations: Netskope documentation highlights throughput limits and sizing considerations for tunnels.

Source: Netskope Technical Documentation, "GRE and IPsec Tunnels". It states, "Each GRE or IPsec tunnel has a soft limit of 1 Gbps of throughput," making bandwidth a critical planning factor.

3. Netskope Client Behavior: Netskope documentation details the need for on-premises detection to manage how the client steers traffic when on a network that is already being steered by a tunnel.

Source: Netskope Technical Documentation, "Netskope Client Traffic Steering Preferences". The section on "On-Premises Detection" explains how to configure the client to recognize the corporate network and disable its own tunnel, deferring to the site-level steering mechanism.

Scroll to Top