Discuss Netskope NSK200 Exam Topic 1 Question 7

You are using the Netskope DLP solution. You notice flies containing test data for credit cards are not triggering DLP events when uploaded to Dropbox. There are corresponding page events. Which two scenarios would cause this behavior? (Choose two.)

AThe Netskope client Is not steering Dropbox traffic.

BThe DLP rule has the severity threshold set to a value higher than the number of occurrences.

CThe credit card numbers in your test data are Invalid 16-dlglt numbers.

DThere is no API protection configured for Dropbox.

Suggested Answer: B, C

There are two possible scenarios that would cause the behavior of files containing test data for credit cards not triggering DLP events when uploaded to Dropbox. One scenario is that the DLP rule has the severity threshold set to a value higher than the number of occurrences. This means that the rule will only trigger an event if the number of matches for the sensitive data exceeds the specified threshold. For example, if the rule has a severity threshold of 10 and the file contains only 5 credit card numbers, then no event will be generated. To fix this, you can lower the severity threshold or remove it altogether. The other scenario is that the credit card numbers in your test data are invalid 16-digit numbers. This means that the numbers do not pass the Luhn algorithm check, which is a validation method used by Netskope DLP to detect valid credit card numbers. For example, if the number is 1234-5678-9012-3456, then it is not a valid credit card number and will not be detected by Netskope DLP. To fix this, you can use valid test credit card numbers that pass the Luhn algorithm check. The other options are not valid scenarios for this behavior. The Netskope client is not steering Dropbox traffic is not a valid scenario because there are corresponding page events, which means that the traffic is being steered to Netskope.There is no API protection configured for Dropbox is not a valid scenario because API protection is not required for DLP detection on file uploads, which are handled by real-time protection.Reference:DLP Rule Settings1,Credit Card Number Detection2

Get Premium NSK200 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

22 comments · newest first

Nydia 11 months ago

Wait, are we sure about C? I thought any number would trigger it!

Sherron 11 months ago

D is a strong contender. API protection is crucial for DLP.

Belen 11 months ago

C seems unlikely. Invalid credit card numbers still should trigger.

Barney 11 months ago

I think B makes sense too. Severity thresholds can be tricky!

Kimberely 11 months ago

A is definitely a possibility. No steering means no DLP.

Sheridan 12 months ago

I feel like I read that if there's no API protection for Dropbox, it could lead to issues with DLP events. So, option D might be a possibility too.

Lou 12 months ago

I practiced a question similar to this, and I think invalid credit card numbers could definitely be a reason for not triggering events, which points to option C.

Kanisha 12 months ago

I'm not entirely sure, but I think if the DLP rule's severity threshold is too high, it might not trigger events. That could be option B?

Denae 1 year ago

I remember something about the Netskope client needing to steer traffic for DLP to work properly, so option A seems likely.

Elenore 1 year ago

Ah, I think I know what's going on here. The Netskope client not steering the Dropbox traffic or the DLP rule having the wrong severity threshold are the most likely culprits in my opinion.

Eliz 1 year ago

Okay, let's see. The key things to focus on are the Netskope client, the DLP rule configuration, and the test data itself. I think I have a strategy to work through this.

Von 1 year ago

This seems like a tricky one. I'll need to carefully consider the different scenarios that could cause the DLP events not to trigger.

Noel 1 year ago

Hmm, I'm a bit confused by this question. I'll need to think through the Netskope DLP solution and how it interacts with Dropbox to figure out what might be going on.

Lino 1 year ago

Wait, is this really a series system? I'm not sure if I'm interpreting the question correctly. I better double-check my understanding before answering.

Herman 1 year ago

This looks like a straightforward data filtering problem. I'll need to carefully read the frequency information and the code to determine how many observations will be written to the output.

Cherry 1 year ago

I'm pretty confident that the correct answer is C. Downloading the update first and then manually installing it later seems like the best way to schedule the update while delaying the installation.

Kaitlyn 3 years ago

Hmm, the client not steering Dropbox traffic also seems like a possible explanation. Maybe the Netskope client is just not configured to handle Dropbox properly.

Colette 3 years ago

I'm not sure about the credit card numbers, but the lack of API protection for Dropbox sounds like a likely culprit. Without that, the Netskope client might not be able to properly monitor the traffic.

Tammara 2 years ago

↳ replying to Colette

D) There is no API protection configured for Dropbox.

Krystal 2 years ago

↳ replying to Colette

B) The DLP rule has the severity threshold set to a value higher than the number of occurrences.

Lorean 3 years ago

Yeah, the credit card numbers could be the problem. If they're not valid 16-digit numbers, the DLP solution won't be able to recognize them. And I agree, the severity threshold could also be an issue.

Whitley 3 years ago

Hmm, this is an interesting one. I'm guessing the issue is with the DLP rule configuration. Maybe the severity threshold is set too high, or the credit card numbers are not being detected properly.

Netskope NSK200 Exam - Topic 1 Question 7 Discussion