Get Netskope NSK200 Exam Practice Questions - Real and Updated

Answer : C

To block any screenshots from being uploaded, the engineering firm should use the ML image classifier feature of Netskope DLP. This feature uses machine learning to detect sensitive information within images, such as screenshots, whiteboards, passports, driver's licenses, etc. The firm can create a DLP policy that blocks any image upload that matches the screenshot classifier. This will prevent employees from circumventing the DLP controls by taking screenshots of sensitive documents.Reference:Improved DLP Image Classifiers,Netskope Data Loss Prevention,The Importance of a Machine Learning-Based Source Code Classifier

Answer : B, D

To provision Netskope users from Okta with SCIM Provisioning, and users are not showing up in the tenant, the two Netskope components that you should verify first in Okta for accuracy are B. OAuth token and D. SCIM server URL.The OAuth token is a credential that allows Okta to authenticate with the Netskope SCIM server and perform user provisioning operations4.The SCIM server URL is the endpoint that Okta uses to communicate with the Netskope SCIM server and send user data5. Both of these components must be configured correctly in Okta for the SCIM Provisioning to work.You can find them in the Netskope UI under Settings > Tools > Directory Tools > SCIM Integration6. Therefore, options B and D are correct and the other options are incorrect.Reference:SCIM-Based User Provisioning - Netskope Knowledge Portal,Netskope + Okta Use Case: Provisioning Users and Managing Groups Using SCIM - Netskope,Netskope Partner Okta - Netskope

Answer : B

In order to restrict users from logging into their personal Google accounts, the policy should include a user constraint. This will ensure that only users with corporate accounts can access the corporate collaboration suite. The user constraint can be added by selecting the ''User'' option in the ''Source'' field and then choosing the appropriate user group or identity provider. The other options are not relevant for this scenario.Reference: [Creating a Policy to Block Personal Google Services], [Policy Creation], [User Constraint]

Answer : B

The problem in this scenario is that the Netskope client connection is being decrypted by a network security device. This is evident from the log message ''ERROR SSL certificate verification failed: self signed certificate in certificate chain''. This means that the Netskope client is receiving a certificate that is not issued by Netskope, but by a device that is intercepting and decrypting the traffic between the client and the Netskope cloud.This can cause the client to fail to download the required configuration and remain in a disabled state1. Therefore, option B is correct and the other options are incorrect.Reference:Troubleshooting Netskope Client - Netskope Knowledge Portal,Using Netskope Client - Netskope Knowledge Portal

Answer : A, B, D

Netskope's REST API v2 provides access to various event types via URI paths. The event types include application, alert, infrastructure, audit, incident, network, and page. These event types can be used to retrieve data from Netskope's cloud security platform. The event types client and user are not supported by the REST API v2.Reference:REST API v2 Overview,Cribl Netskope Events and Alerts Integration,REST API Events and Alerts Response Descriptions