There is an error in the RHEL 8, RH124, Chapter 10, Section 1 explanation, here:
This says that it "seeks the user's confirmation on whether or not to continue with the connection." By default, it does not. Instead, it flat-out disallows the connection, as seen here (this was done an a CentOS 8 machine because I didn't want to go messing with all the SSH keys and things in the lab environment):
Notice that the output says "you have requested strict checking."
The note in the blue box says that StrictHostKeyChecking needs to be set to yes in /etc/ssh/ssh_config (or ~/.ssh/config) in order to "always abort the SSH connection." This is a semi-true statement. If it is undefined, it will also automatically abort the SSH connection as seen here - the setting in the file is, by default, commented out:
And, additionally, the man pages support this (that the default behavior is to abort the connection):
"...and ssh will refuse to connet to hosts whost host key has changed."
This one may seem a bit confusing. It boils doen to this: with no changes to the the system or default SSH settings, the connection will automatically be aborted, contrary to what the text says in the first image.
Program Lead at Arizona's first Red Hat Academy, est. 2005 Estrella Mountain Community College