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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Netskope NSK101 Exam - 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.

by Lauran at Sep 15, 2024, 01:08 PM

Limited Time Offer

25%

Off

Get Premium NSK101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ruthann
6 months ago
Blocking the app is definitely not the solution here!
upvoted 0 times
...
Delmy
6 months ago
I agree, steering exceptions might just complicate things more.
upvoted 0 times
...
Deane
6 months ago
Wait, are we sure the messenger app is really using proprietary encryption?
upvoted 0 times
...
Ronnie
7 months ago
I think bypassing the SSL decryption could work too.
upvoted 0 times
...
Gail
7 months ago
Sounds like a custom connector is the way to go!
upvoted 0 times
...
Harris
7 months ago
I recall something about steering exceptions, but I can't quite remember if that would actually solve the issue with the encryption.
upvoted 0 times
...
Kiley
7 months ago
I feel like bypassing the messenger domain could work, but I’m not entirely confident if that would maintain visibility as well.
upvoted 0 times
...
Dick
7 months ago
I think creating a custom cloud application might be the right approach, similar to what we practiced in the last session.
upvoted 0 times
...
Gail
8 months ago
I remember we discussed how proprietary encryption can complicate visibility, but I'm not sure which option would best address that.
upvoted 0 times
...
Dean
8 months ago
I'm a little confused on the difference between options B and D. Both seem like they could work, but I'm not sure which one is the better approach in this scenario.
upvoted 0 times
...
Fatima
8 months ago
Okay, I think I've got it. Option C to bypass the SSL decryption for the messenger domain is probably the way to go here. That should let the traffic through while still giving us some visibility.
upvoted 0 times
...
Joye
8 months ago
Hmm, the question mentions proprietary encryption, so I'm guessing that means we can't just block the app. Option B seems like the best approach to maintain visibility.
upvoted 0 times
...
Glory
8 months ago
This seems like a tricky one. I'll need to think through the options carefully to make sure I understand the implications of each.
upvoted 0 times
...
Herman
1 year ago
A? Oh, come on! Blocking the messenger app? That's like trying to catch the wind with a butterfly net.
upvoted 0 times
Kaitlyn
11 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Ora
11 months ago
A? Oh, come on! Blocking the messenger app? That's like trying to catch the wind with a butterfly net.
upvoted 0 times
...
Freeman
11 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Lillian
11 months ago
A) Change the real-time policy to block the messenger application.
upvoted 0 times
...
...
Joesph
1 year ago
B is the way to go! A custom connector will give you full visibility and control over that proprietary encryption.
upvoted 0 times
Cheryl
11 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
11 months ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Thurman
11 months 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 year 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 months ago
That sounds like a good solution too, it would give more control over the application.
upvoted 0 times
...
Hana
12 months 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
12 months ago
I think that could work, it would allow access while still maintaining visibility.
upvoted 0 times
...
Nada
1 year ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Ashlyn
1 year ago
C seems like the right choice here. Bypassing the SSL decryption for the messenger domain should do the trick.
upvoted 0 times
Mariko
1 year ago
Agreed, it's a good balance between security and functionality.
upvoted 0 times
...
Jacki
1 year ago
Exactly, it's important to maintain visibility while still permitting access.
upvoted 0 times
...
Raina
1 year ago
That makes sense, it would allow the messenger application to work without interference.
upvoted 0 times
...
Fannie
1 year ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
Oliva
1 year ago
That makes sense, it should allow the messenger application to work while still maintaining visibility.
upvoted 0 times
...
Malcolm
1 year ago
C) Add a policy in the SSL decryption section to bypass the messenger domain(s).
upvoted 0 times
...
...
Carmelina
1 year 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
1 year ago
I agree with Derrick, option C seems like the best choice to permit access while maintaining visibility.
upvoted 0 times
...
Derrick
1 year ago
I think option C would work because we need to bypass the encryption used by the messenger application.
upvoted 0 times
...

Save Cancel