Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Netskope Exam NSK101 Topic 4 Question 20 Discussion

Actual exam question for Netskope's NSK101 exam
Question #: 20
Topic #: 4
[All NSK101 Questions]

You just deployed the Netskope client in Web mode and several users mention that their messenger application is no longer working. Although you have a specific real-time policy that allows this application, upon further investigation you discover that it is using proprietary encryption. You need to permit access to all the users and maintain some visibility.

In this scenario, which configuration change would accomplish this task?

Show Suggested Answer Hide Answer
Suggested Answer: A

When designing an architecture with Netskope Private Access, the Netskope Publisher is the element that guarantees connectivity between the Netskope cloud and the private application. The Publisher acts as a gateway, securely connecting users to private applications hosted on-premises or in data centers.

Netskope Publisher: This component facilitates secure access to private applications by connecting the Netskope cloud with the internal network. It ensures that users can access private applications seamlessly while maintaining security and compliance.


Netskope documentation on Private Access and the role of the Publisher.

Best practices for configuring and deploying Netskope Publisher to ensure secure connectivity to private applications.

Contribute your Thoughts:

Herman
29 days ago
A? Oh, come on! Blocking the messenger app? That's like trying to catch the wind with a butterfly net.
upvoted 0 times
...
Joesph
1 months ago
B is the way to go! A custom connector will give you full visibility and control over that proprietary encryption.
upvoted 0 times
Albina
4 days ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Thurman
5 days ago
B) Create a new custom cloud application using the custom connector that can be used in the real-time policy.
upvoted 0 times
...
...
Afton
1 months ago
D? Really? Steering exceptions for a messenger app? That's like trying to herd cats with a laser pointer.
upvoted 0 times
Kizzy
12 days ago
That sounds like a good solution too, it would give more control over the application.
upvoted 0 times
...
Hana
16 days ago
B) Create a new custom cloud application using the custom connector that can be used in the real-time policy.
upvoted 0 times
...
Ashleigh
18 days ago
I think that could work, it would allow access while still maintaining visibility.
upvoted 0 times
...
Nada
23 days ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Ashlyn
2 months ago
C seems like the right choice here. Bypassing the SSL decryption for the messenger domain should do the trick.
upvoted 0 times
Mariko
23 days ago
Agreed, it's a good balance between security and functionality.
upvoted 0 times
...
Jacki
25 days ago
Exactly, it's important to maintain visibility while still permitting access.
upvoted 0 times
...
Raina
1 months ago
That makes sense, it would allow the messenger application to work without interference.
upvoted 0 times
...
Fannie
1 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Oliva
2 months ago
That makes sense, it should allow the messenger application to work while still maintaining visibility.
upvoted 0 times
...
Malcolm
2 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Carmelina
3 months ago
I'm not sure, but maybe creating a custom cloud application with a custom connector could also solve the issue.
upvoted 0 times
...
Xenia
3 months ago
I agree with Derrick, option C seems like the best choice to permit access while maintaining visibility.
upvoted 0 times
...
Derrick
3 months ago
I think option C would work because we need to bypass the encryption used by the messenger application.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77