Netskope Exam NSK200 Topic 1 Question 2 Discussion

Actual exam question for Netskope's NSK200 exam

Question #: 2
Topic #: 1

After deploying the Netskope client to a number of devices, users report that the Client status indicates "Admin Disabled". User and gateway information is displayed correctly in the client configuration dialog

Why are clients installing in an "Admin Disabled" state in this scenario?

AAll devices were previously disabled by the administrator.

BThe user's identity is not synchronized to Netskope.

CThe user's password was incorrect during enrollment.

DThe user's account has no mail ID attribute In Active Directory.

Show Suggested Answer

Suggested Answer: A

The Netskope client can be disabled by the administrator from the Netskope console. This is useful for troubleshooting or maintenance purposes. When the client is disabled by the administrator, it shows the status as ''Admin Disabled'' and does not apply any policies or steer any traffic. The user cannot enable the client unless the administrator enables it from the console.The other options are not valid reasons for the client to be in an ''Admin Disabled'' state.Reference: Netskope Client Status1, Enable or Disable Netskope Client2

by Deandrea at Nov 25, 2023, 06:33 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Peggie

9 months ago

You guys are overthinking this. The real issue here is that the user's account has no mail ID attribute in Active Directory. That's a classic gotcha in Netskope deployments. I've seen it happen way too many times.

upvoted 0 times

...

Carma

10 months ago

Nah, I don't think that's it. If all the devices were previously disabled by the admin, that would be the more likely scenario, don't you think? This question is trying to trip us up, I can feel it.

upvoted 0 times

...

William

10 months ago

I'm not so sure about that. Maybe the user's password was incorrect during enrollment, and that's causing the issue. It's a common problem in these types of deployments.

upvoted 0 times

...

9 months ago

B) The user's identity is not synchronized to Netskope.

upvoted 0 times

...