CompTIA SY0-701 Exam - Topic 4 Question 23 Discussion

Actual exam question for CompTIA's SY0-701 exam

Question #: 23
Topic #: 4

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?

ATokenization

BHashing

CObfuscation

DSegmentation

Show Suggested 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.

by Merlyn at Sep 12, 2024, 07:38 PM

Limited Time Offer

25%

Off

Get Premium SY0-701 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Larae

3 months ago

Not sure if tokenization is the best choice for a log-in database.

upvoted 0 times

...

Lemuel

3 months ago

I agree, tokenization really limits exposure!

upvoted 0 times

...

Samira

3 months ago

Wait, isn't segmentation more about network security?

upvoted 0 times

...

Catina

4 months ago

Hashing is definitely more secure than obfuscation.

upvoted 0 times

...

Dean

4 months ago

I think tokenization is the best option here.

upvoted 0 times

...

Antonio

4 months ago

Segmentation could help limit access, but I wonder if it directly addresses the database impact like tokenization does.

upvoted 0 times

...

Dorothea

4 months ago

Obfuscation sounds familiar, but I feel like it’s more about making data unreadable rather than protecting it from breaches.

upvoted 0 times

...

Cordelia

4 months ago

I'm not entirely sure, but I remember hashing is often used for passwords. Would that apply to a log-in database?

upvoted 0 times

...

Sherill

5 months ago

I think tokenization might be the best choice here since it replaces sensitive data with non-sensitive equivalents.

upvoted 0 times

...

Rozella

5 months ago

Segmentation seems like a good approach to isolate the login database and minimize the potential damage. But I'm not 100% sure if that's the security team's top recommendation.

upvoted 0 times

...

Kandis

5 months ago

I'm a bit confused on the differences between these options. Tokenization, hashing, obfuscation - which one would really be the best to limit the impact of a breach?

upvoted 0 times

...

Chantay

5 months ago

Hashing is definitely the way to go here. It's a well-established technique for securely storing sensitive data like login credentials.

upvoted 0 times

...

Hillary

5 months ago

Hmm, I'm not sure about this one. Tokenization, hashing, obfuscation, or segmentation - they all have their pros and cons. I'll need to think this through carefully.

upvoted 0 times

...

Jamika

5 months ago

This one seems pretty straightforward. I'm thinking the security team would recommend hashing to protect the login database in case of a breach.

upvoted 0 times

...

Dusti

5 months ago

I feel like navigator could be relevant, but it seems more about the browser itself rather than page navigation.

upvoted 0 times

...

Emile

5 months ago

Hmm, I'm a bit confused. Disabling the user in Active Directory should immediately prevent them from authenticating to Azure AD, so I'm not sure why there's a 30-minute delay. I'll need to think this through carefully.

upvoted 0 times

...

Oneida

1 year 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 year ago

C) Obfuscation

upvoted 0 times

...

Denae

1 year ago

B) Hashing

upvoted 0 times

...

Lucille

1 year ago

A) Tokenization

upvoted 0 times

...

Quinn

1 year 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

1 year ago

I believe segmentation could help in limiting impact as well.

upvoted 0 times

...

Kris

1 year 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 year ago

D) Segmentation

upvoted 0 times

...

Jesusita

1 year ago

C) Obfuscation

upvoted 0 times

...

Skye

1 year ago

B) Hashing

upvoted 0 times

...

Ronnie

1 year ago

A) Tokenization

upvoted 0 times

...

Raul

1 year ago

I'm not sure, but I think hashing could also be a good choice.

upvoted 0 times

...

Carmela

1 year 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

1 year ago

Tokenization and obfuscation are good too, but hashing is the most secure choice.

upvoted 0 times

...

Christa

1 year ago

I agree, it's like a secret code that keeps our data safe from prying eyes.

upvoted 0 times

...

Mee

1 year ago

Segmentation might help too, but hashing is the most recommended method for data protection.

upvoted 0 times

...

Loise

1 year ago

Hashing is definitely the best option for protecting our log-in database.

upvoted 0 times

...

Pura

1 year ago

Tokenization could also be a good choice, but hashing is more secure.

upvoted 0 times

...

Chau

1 year ago

I agree, it's like a secret code that keeps our data safe from prying eyes.

upvoted 0 times

...

Arlyne

1 year ago

Hashing is definitely the best option for protecting our log-in database.

upvoted 0 times

...

Bok

1 year ago

I agree with Annett, tokenization is a good option to limit impact.

upvoted 0 times

...

Annett

1 year ago

I think the security team would recommend tokenization.

upvoted 0 times

...

Luis

1 year 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

1 year ago

Yeah, tokenization is a strong option. It adds an extra layer of security.

upvoted 0 times

...

Cherelle

1 year ago

Tokenization is a good choice. It can help protect the log-in database.

upvoted 0 times

...