Under what specific condition is `git push --force-with-lease` preferred over `git push --force`, and what protection does it offer?

The specific condition under which `git push --force-with-lease` is preferred over `git push --force` is when a user needs to rewrite the history of a remote branch, for instance, after locally rebasing or squashing commits, but also wants to prevent accidentally overwriting new commits that other collaborators might have pushed to that same remote branch since the user's last fetch or pull operation. This preference arises in collaborative environments where multiple developers might be working on the same branch simultaneously.