Cyber Monday 2024! 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-701 Topic 4 Question 23 Discussion

Actual exam question for CompTIA's SY0-701 exam
Question #: 23
Topic #: 4
[All SY0-701 Questions]

An organization wants to limit potential impact to its log-in database in the event of a breach. Which of the following options is the security team most likely to recommend?

Show Suggested Answer Hide Answer
Suggested Answer: B

To limit the potential impact on the log-in database in case of a breach, the security team would most likely recommend hashing. Hashing converts passwords into fixed-length strings of characters, which cannot be easily reversed to reveal the original passwords. Even if the database is breached, attackers cannot easily retrieve the actual passwords if they are properly hashed (especially with techniques like salting).

Tokenization is used to replace sensitive data with a token, but it is more common for protecting credit card data than passwords.

Obfuscation is the process of making data harder to interpret but is weaker than hashing for password protection.

Segmentation helps isolate data but doesn't directly protect the contents of the login database.


Contribute your Thoughts:

Oneida
2 months ago
Hey, did you hear about the IT guy who tried to secure the database with duct tape and a rubber band? I bet he'd recommend that over these options!
upvoted 0 times
Sheridan
1 months ago
C) Obfuscation
upvoted 0 times
...
Denae
1 months ago
B) Hashing
upvoted 0 times
...
Lucille
1 months ago
A) Tokenization
upvoted 0 times
...
...
Quinn
2 months ago
Segmentation, eh? That's like building little forts around your data, so if one falls, the rest are still standing. Smart move, if you ask me.
upvoted 0 times
...
Denny
2 months ago
I believe segmentation could help in limiting impact as well.
upvoted 0 times
...
Kris
2 months ago
Obfuscation, eh? Sounds like a fancy way to make things really confusing. I wonder if they'll throw in some glitter and rainbows too.
upvoted 0 times
Kenneth
1 months ago
D) Segmentation
upvoted 0 times
...
Jesusita
1 months ago
C) Obfuscation
upvoted 0 times
...
Skye
1 months ago
B) Hashing
upvoted 0 times
...
Ronnie
2 months ago
A) Tokenization
upvoted 0 times
...
...
Raul
3 months ago
I'm not sure, but I think hashing could also be a good choice.
upvoted 0 times
...
Carmela
3 months ago
Hashing is the way to go! It's like turning your sensitive data into a secret code that no one can crack. Brilliant!
upvoted 0 times
Valentine
2 months ago
Tokenization and obfuscation are good too, but hashing is the most secure choice.
upvoted 0 times
...
Christa
2 months ago
I agree, it's like a secret code that keeps our data safe from prying eyes.
upvoted 0 times
...
Mee
2 months ago
Segmentation might help too, but hashing is the most recommended method for data protection.
upvoted 0 times
...
Loise
2 months ago
Hashing is definitely the best option for protecting our log-in database.
upvoted 0 times
...
Pura
2 months ago
Tokenization could also be a good choice, but hashing is more secure.
upvoted 0 times
...
Chau
2 months ago
I agree, it's like a secret code that keeps our data safe from prying eyes.
upvoted 0 times
...
Arlyne
2 months ago
Hashing is definitely the best option for protecting our log-in database.
upvoted 0 times
...
...
Bok
3 months ago
I agree with Annett, tokenization is a good option to limit impact.
upvoted 0 times
...
Annett
3 months ago
I think the security team would recommend tokenization.
upvoted 0 times
...
Luis
3 months ago
Hmm, tokenization seems like a reasonable option to limit the impact of a breach. Plus, it's got a cool name that makes it sound high-tech.
upvoted 0 times
Inocencia
3 months ago
Yeah, tokenization is a strong option. It adds an extra layer of security.
upvoted 0 times
...
Cherelle
3 months ago
Tokenization is a good choice. It can help protect the log-in database.
upvoted 0 times
...
...

Save Cancel