Free CompTIA Tech+ FC0-U71 Actual Exam Questions - Question 1 Discussion
policies would most likely prevent this practice?
A, because reuse policies aim to stop the same password being used repeatedly, even across sites.
A imo, reuse policies usually mean no repeating passwords within the same service, not across different sites. So it might not fully prevent using the same password everywhere.
Actually, I’d go with complexity (B) here. If passwords have to be complex—mix of chars, numbers, symbols—it becomes much harder to remember the same one for multiple sites. So users are pushed to create different passwords instead of reusing the same simple one. Reuse policies (A) usually only stop repeated passwords on the same site, not across different websites since they don’t share data. Privacy (C) and length (D) don’t really target reuse directly, so complexity seems like the best fit to indirectly discourage reusing passwords everywhere.
I get why reuse (A) seems right, but usually reuse policies are about the same site, not different websites. Could complexity (B) indirectly force users to create unique passwords that they can’t easily remember and reuse?
A vs B? Complexity makes passwords harder but doesn’t stop using the same one everywhere. Reuse policies are the only ones that specifically stop repeating passwords across sites.
A - reuse specifically targets using identical passwords repeatedly, even across sites.
It’s A since reuse rules prevent the same password from being accepted on multiple sites.
A. To add on, complexity and length rules might make passwords tougher, but they don’t actually monitor if the same password shows up on different platforms. Privacy is more about data handling, not password reuse. So, reuse policies are the only ones that really tackle this issue head-on by enforcing unique passwords per site.
Probably A as well. Complexity and length make passwords stronger but don’t stop using the same password on multiple sites, which is exactly what reuse policies block.
Option A fits best here because it specifically targets the issue of using the same password repeatedly. Complexity and length mainly focus on how strong or hard to guess a password is, but they don’t stop someone from using that same password on different sites. Privacy policies aren’t really about password reuse either, so that leaves A as the one that makes the most sense.
Maybe A, since complexity or length don’t address reusing passwords across sites.
A imo, reuse policies directly stop using identical passwords everywhere.
Guessing A, since reuse policies specifically target using the same password repeatedly.
A. This one makes the most sense since reuse policies are designed to block using the same password across multiple platforms, which fits the question perfectly.
A imo, reuse policies stop same passwords on different sites.