MENU
You are testing policies using the DLP predefined identifier "Card Numbers (Major Networks; all)." No DLP policy hits are observed.
Suggested Answer: B
Get Premium NSK200 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
For DLP policies to detect sensitive data like credit card numbers, the data must contain valid credit card numbers as defined by the DLP pattern. Invalid or incorrectly formatted numbers will not trigger DLP policy hits.
34 comments · newest first
CA
Carline
10 months ago
Totally agree, using the API is essential for proper protection!
AS
Ashton
11 months ago
Wait, do we really need to normalize to 16 digits? Sounds odd.
MI
Millie
11 months ago
Definitely need the Netskope client for advanced features!
BA
Barrett
11 months ago
I think you need valid credit card numbers for DLP to trigger.
MA
Markus
11 months ago
No hits means no valid card numbers detected.
HA
Hannah
12 months ago
I’m not confident, but I feel like using the API protection might not be necessary unless specified, so I’m unsure about A.
JA
Jade
12 months ago
I’m leaning towards option D because I recall that the Netskope client is often required for advanced DLP features.
DE
Delsie
12 months ago
I think I saw a practice question that mentioned normalizing data, but I’m not entirely sure if that applies here.
AL
Alton
1 year ago
I remember something about needing actual credit card numbers for the DLP to trigger, so maybe option B is correct?
KR
Kristofer
1 year ago
I think the key here is to focus on the fact that no DLP policy hits were observed. That tells me the data doesn't have valid credit card numbers, so options C and D about normalizing or using advanced DLP tools don't apply. I'm leaning towards B as the answer.
MO
Monte
1 year ago
I'm a bit confused by this one. The question doesn't give us much information to go on. I'll need to carefully read through the options and try to figure out the best approach.
JO
Jonelle
1 year ago
I'm pretty confident the answer is B. The question states that no DLP policy hits were observed, so the data must not have valid credit card numbers. That means option A about using Netskope API protection is not relevant.
CR
Cristal
1 year ago
Okay, let's see. If there are no DLP policy hits, that suggests the data doesn't contain any valid credit card numbers. Maybe I should double-check the data to make sure it's formatted correctly.
CA
Cathrine
1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the different options and what they're asking for.
JU
Junita
2 years ago
Haha, I bet the answer is B. If the data doesn't have valid credit card numbers, no wonder the DLP policy didn't pick them up. Gotta have the real deal for that to work!
AD
Adelle
2 years ago
B) Your data must have valid credit card numbers.
SH
Shoshana
2 years ago
A) You must use Netskope API protection.
DO
Dorinda
2 years ago
I'm torn between B and C. But I'll go with C, just because I like the idea of having all the credit card numbers in a nice, neat 16-digit format. It's like making the DLP policy's job a little easier, you know?
LA
Lavelle
2 years ago
D seems like the way to go. Using Netskope client with advanced DLP and OCR should be able to catch those credit card numbers, even if they're not in the standard format.
MA
Marti
2 years ago
C) You must normalize credit card numbers to 16-digit consecutive numbers.
LE
Lewis
2 years ago
A) You must use Netskope API protection.
PA
Pamella
2 years ago
D) You must use the Netskope client to perform advanced DLP and optical character recognition.
GO
Golda
2 years ago
I'm going with C. Normalizing the credit card numbers to 16-digit consecutive numbers is probably the best way to ensure the DLP policy can detect them.
GE
Geoffrey
2 years ago
B) Your data must have valid credit card numbers.
NI
Nicolette
2 years ago
A) You must use Netskope API protection.
DE
Devorah
2 years ago
C) You must normalize credit card numbers to 16-digit consecutive numbers.
TH
Theola
2 years ago
But maybe our data doesn't have valid credit card numbers.
NO
Noelia
2 years ago
True, we might need to normalize the credit card numbers to 16-digit consecutive numbers.
NO
Noelia
2 years ago
I think we should use Netskope API protection.
EM
Emogene
2 years ago
I think the answer is B. The question states that no DLP policy hits were observed, which means the data likely doesn't have valid credit card numbers.
FE
Felicia
2 years ago
D) You must use the Netskope client to perform advanced DLP and optical character recognition.
LI
Lizbeth
2 years ago
C) You must normalize credit card numbers to 16-digit consecutive numbers.
CA
Carmela
2 years ago
B) Your data must have valid credit card numbers.
NO
Norah
2 years ago
A) You must use Netskope API protection.