Which of the following is the BEST reason for salting a password hash before it is stored in a database?

Salting involves appending a unique, random string (salt) to each user's password before it undergoes the hashing process. This crucial step ensures that even if multiple users select the exact same password, their individual stored hash values will be distinct within the database. Consequently, this prevents the storage of identical or duplicate hash values, which enhances security by making it harder for attackers to identify accounts with shared passwords through simple hash comparison or pre-computed tables.

While salting adds computational overhead, its primary purpose is to enhance the security of the hash by making pre-computation attacks more difficult, not specifically to slow down a retrieval process which typically compares a newly hashed password to a stored hash.

Hashing itself transforms a password into an unreadable format; salting enhances the security of this hashed output against attacks like rainbow tables, rather than initially protecting it from being saved in readable format.

Password complexity rules, such as minimum length and character requirements, are used to prevent users from choosing simple passwords, whereas salting strengthens the security of whatever password hash is created.