Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - 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
13 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
21 days ago
B is the way to go! A custom connector will give you full visibility and control over that proprietary encryption.
upvoted 0 times
...
Afton
28 days ago
D? Really? Steering exceptions for a messenger app? That's like trying to herd cats with a laser pointer.
upvoted 0 times
Ashleigh
2 days ago
I think that could work, it would allow access while still maintaining visibility.
upvoted 0 times
...
Nada
7 days ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Ashlyn
1 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
7 days ago
Agreed, it's a good balance between security and functionality.
upvoted 0 times
...
Jacki
9 days ago
Exactly, it's important to maintain visibility while still permitting access.
upvoted 0 times
...
Raina
16 days ago
That makes sense, it would allow the messenger application to work without interference.
upvoted 0 times
...
Fannie
28 days ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Oliva
1 months ago
That makes sense, it should allow the messenger application to work while still maintaining visibility.
upvoted 0 times
...
Malcolm
1 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Carmelina
2 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
2 months ago
I agree with Derrick, option C seems like the best choice to permit access while maintaining visibility.
upvoted 0 times
...
Derrick
2 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