Exercise 1: Ubuntu Guide, CentOS Server — Possible Solution
====================================================================

WHAT'S LIKELY GOING ON
------------------------------
Per this chapter, "Debian/Ubuntu-family distros and RHEL/CentOS-family
distros use different conventional filenames for the same underlying
log" - specifically naming "auth.log vs. secure" as one of the exact
pairs that differs. The guide isn't wrong, and the server isn't
missing its authentication log - the guide was simply written for a
different distro family than the one actually being used, so it
references that family's own filename convention instead of CentOS's.

WHY THE FILE APPEARS "MISSING"
------------------------------
Per this chapter, this is "a real, common way to end up looking for a
file that simply doesn't exist on the system in front of you" - not
because the log itself doesn't exist, but because /var/log/auth.log
specifically is the Debian/Ubuntu name, and that exact filename was
never going to exist on a CentOS system in the first place.

WHAT FILE TO CHECK INSTEAD
------------------------------
Per this chapter's own table, the RHEL/CentOS equivalent authentication
log is /var/log/secure - the same underlying category of event
(logins, sudo usage), just filed under the naming convention that
distro family actually uses.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies the distro-naming-convention mismatch as the
actual cause rather than a genuinely missing log, and correctly names
/var/log/secure as the CentOS equivalent per this chapter's own table.