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

CompTIA Exam SY0-601 Topic 2 Question 73 Discussion

Contribute your Thoughts:

Vanesa
7 months ago
D? Really? I mean, sure, tokenization can work for that, but it seems a bit overkill. Wouldn't basic data masking or segmentation be enough in that case? Save the tokenization for the financial stuff, you know?
upvoted 0 times
Gilberto
6 months ago
A
upvoted 0 times
...
Janine
6 months ago
C
upvoted 0 times
...
Kristel
6 months ago
D
upvoted 0 times
...
Lucina
6 months ago
C
upvoted 0 times
...
Clarence
6 months ago
A
upvoted 0 times
...
...
Cassi
7 months ago
You guys are spot on. Tokenization is the perfect solution for that scenario. Although, I could see an argument for option D as well, if you're dealing with highly sensitive personal data in a database.
upvoted 0 times
...
Nada
7 months ago
I agree, C is the way to go. Tokenization is the gold standard for protecting customer payment info. Plus, it makes things super easy for the users - they don't have to worry about their card details being compromised.
upvoted 0 times
...
Erinn
7 months ago
Hmm, I think option C is the best here. Tokenization is great for securely storing sensitive financial data like credit card numbers. It's a lot safer than having the actual card numbers in the database.
upvoted 0 times
...

Save Cancel