RHCSA
862 incident response problems that help with RHCSA prep.
먼저 읽을 가이드
추천 문제
All problems (862)
LINUX-1609A journald hostname fix is present and one log stream still shows the old node nameOne log stream still shows the old node name after a hostname fix.LinuxIntermediate7 minProLINUX-1593A sudo path cleanup is correct and one host still runs the old binaryOne host still runs the old binary after sudo path cleanup.LinuxIntermediate7 minProLINUX-1563A sudo path is updated and one host still denies the commandOne host denies a deploy command after the binary path was standardized.LinuxIntermediate8 minProLINUX-1583A sudo rule is fixed and one command still resolves the old pathOne host still executes the old binary after a sudo rule fix.LinuxIntermediate8 minProLINUX-1573A sudoers cleanup lands and one deploy host still denies the commandOne deploy host still denies a command after sudoers cleanup.LinuxIntermediate8 minProLINUX-1601A tmpfiles cleanup rule is updated and one directory still comes back world-writableA hardened directory keeps returning world-writable after tmpfiles cleanup.LinuxIntermediate8 minProLINUX-1579A journald forward path is corrected and one relay still writes duplicatesOne relay writes duplicates after a journald forward path correction.LinuxAdvanced9 minProLINUX-1589A journald forwarder changes and one parser still reads the old hostOne parser still reads the old host after logging standardization.LinuxAdvanced9 minProLINUX-1599A journald relay fix lands and one parser still reads the old hostOne parser still reads the old host after journald relay fixes.LinuxAdvanced9 minProLINUX-1585A logrotate fix is correct and one service still loses logsOne service still loses logs after a logrotate path fix.LinuxAdvanced9 minProLINUX-1595A logrotate policy rotates cleanly and one app still loses dataOne app still loses data after a logrotate policy correction.LinuxAdvanced9 minProLINUX-1576A Podman auto-update points to the new registry and one service still pulls the old imageOne Podman service still pulls the old image after registry migration.LinuxAdvanced9 minProLINUX-1596A Podman mirror migration succeeds and one host still pulls the old imageOne host still pulls the old image after Podman mirror migration.LinuxAdvanced9 minProLINUX-1522A sudo drop-in looks correct and automation still loses privilegePrivilege escalation fails only after config sync to one bastion host.LinuxAdvanced9 minProLINUX-1532A sudo drop-in looks correct and privilege still failsPrivilege escalation fails only after config sync to one bastion.LinuxAdvanced9 minProLINUX-1603A sudo hardening change is correct and one automation user still runs the old binaryOne automation user still invokes the wrong binary after sudo hardening.LinuxAdvanced9 minProLINUX-1502A sudo include file looks correct and automation still loses rootAutomation starts failing after a sudo include file is edited from a different workstation.LinuxAdvanced9 minProLINUX-1492A sudo rule looks correct and automation still loses rootAutomation that relies on a sudo include file starts failing after the file is edited from a different workstation.LinuxAdvanced9 minProLINUX-1512A sudoers drop-in looks correct and automation still loses privilegePrivilege escalation fails only after config synchronization to one bastion.LinuxAdvanced9 minProLINUX-1551A sudoers include is fixed and one host still denies deploy commandsOnly one host still denies deployment sudo commands after a sudoers fix.LinuxIntermediate9 minPro