Why should you use a password manager, and what are good password practices?

Why should you use a password manager, and what are good password practices?

• A. For generating and storing strong unique passwords; use long, random passwords, avoid reuse, and enable MFA.
• B. It stores passwords in plain text for quick access.
• C. It only stores usernames.
• D. It replaces the need for any password policies.

Answer: (A)

The main idea here is using a password manager to generate and securely store strong, unique passwords for every account, and to enable multi-factor authentication for added protection. A password manager creates long, random passwords that are hard to guess and keeps them in an encrypted vault, so you don’t have to remember them all. This approach prevents password reuse across sites, which is a major weak link, and it makes it practical to use robust credentials everywhere. Enabling multi-factor authentication adds a second layer of security, so even if a password were somehow compromised, an attacker would still need the second factor to gain access. Together, these practices reduce the risk from data breaches and phishing, because you aren’t relying on weak or reused passwords and you’re adding an extra hurdle for attackers. Storing passwords in plain text is unsafe because anyone who accesses that file would see every password, so a breach would expose all accounts. Storing only usernames misses the actual credentials needed to log in, leaving accounts open to compromise. And while password policies matter, they don’t replace the need for strong, unique credentials or the protection a password manager provides; policies guide behavior, but a manager enforces and simplifies it across sites.

The main idea here is using a password manager to generate and securely store strong, unique passwords for every account, and to enable multi-factor authentication for added protection. A password manager creates long, random passwords that are hard to guess and keeps them in an encrypted vault, so you don’t have to remember them all. This approach prevents password reuse across sites, which is a major weak link, and it makes it practical to use robust credentials everywhere.

Enabling multi-factor authentication adds a second layer of security, so even if a password were somehow compromised, an attacker would still need the second factor to gain access. Together, these practices reduce the risk from data breaches and phishing, because you aren’t relying on weak or reused passwords and you’re adding an extra hurdle for attackers.

Storing passwords in plain text is unsafe because anyone who accesses that file would see every password, so a breach would expose all accounts. Storing only usernames misses the actual credentials needed to log in, leaving accounts open to compromise. And while password policies matter, they don’t replace the need for strong, unique credentials or the protection a password manager provides; policies guide behavior, but a manager enforces and simplifies it across sites.