정보처리기사
467 incident response problems that help with 정보처리기사 prep.
먼저 읽을 가이드
추천 문제
All problems (467)
LINUX-100Filesystem is remounted read-only after transient storage errors but the app hides it as generic 500sThe application logs are noisy, yet the real cause is the kernel remounting the filesystem read-only after I/O faults the app never surfaces clearly.LinuxAdvanced18 minProLINUX-077Rsync restore with numeric-ids shifts file ownershipThe backup looks intact, but the restored application loses access because numeric UID preservation no longer matches the target system account layout.LinuxAdvanced20 minProLINUX-068tmpfs-backed runtime path fillsThe service outage looks like a simple restart loop, but the deeper issue is runtime storage pressure from large repeated coredumps on a limited tmpfs path.LinuxAdvanced20 minProCICD-080Feature flag migration step runs before the dependent schema change reaches every shardThe rollout script succeeds centrally, but one shard still serves the old schema and the new flag path begins calling a column that does not exist everywhere yet.CI/CDAdvanced23 minProLINUX-062Missing bind mount at boot makes rsync --delete clean the host path instead of the volumeThe sync command is valid, but the intended mount point never appeared and the cleanup step now targets the underlying directory on the root filesystem.LinuxAdvanced24 minProLINUX-053rsyslog disk queue fills /var after the remote collector becomes unreachableCentral logging is configured correctly for healthy periods, but when the collector disappears the buffered queue grows until the local partition reaches pressure.LinuxAdvanced24 minProLINUX-009An rsync deploy filling the root partitionA scenario that narrows down the root cause, centered on improving the deploy tool's temp-file strategy and the partition policy, in the situation of an rsync deploy filling the root partition because of temp files.LinuxAdvanced26 minProLINUX-098Rsync transfer is complete but hard links were expanded and the backup target fills twice as fastThe restore path works, yet storage usage explodes because the transfer options did not preserve link semantics the source tree relied on.LinuxAdvanced16 minProLINUX-093Systemd path unit keeps relaunching a failed helperThe service appears to restart itself, but the real trigger is a path unit that keeps firing on the same file activity loop.LinuxAdvanced17 minProLINUX-113A shell cleanup trap unmounts the bind mount before the child process exits and late writes vanish from the host pathThe script looks tidy, but teardown runs too early and data written by a still-running child process disappears into a dead mount namespace.LinuxAdvanced18 minProLINUX-090Systemd cgroup memory limit kills the helper process and the main service logs look unrelatedThe application seems to fail in an unrelated code path, but the hidden cause is a helper process being OOM-killed inside the unit's cgroup budget.LinuxAdvanced18 minProLINUX-080XFS project quota silently blocks writes inside the container content pathThe filesystem still has free space, but one workload starts failing writes because a project quota limit was reached on the specific content subtree it uses.LinuxAdvanced18 minProLINUX-081OverlayFS upperdir fills the root filesystem while the underlying data volume still looks emptyContainer workloads write successfully for a while, but the host runs out of space because the upper layer resides on root and not on the large data device operators are watching.LinuxAdvanced19 minProLINUX-087Package rollback restores binaries but not the migrated systemd unit dependency graphThe older package version is back, yet the service still behaves incorrectly because the dependency units changed in a later release and were not reverted with the package.LinuxAdvanced20 minProLINUX-054nftables hotfix disappearsA manual packet filter change solves the immediate outage, but the next reload or reboot brings back the old policy because the permanent source of truth was never updated.LinuxAdvanced23 minProLINUX-035PAM limits are raised but the systemd service still hits too many open filesInteractive shells inherit the new limit correctly, but the daemon still fails under load because its service-level limit remains unchanged.LinuxAdvanced25 minProLINUX-026Swap activity stays high after memory spike is goneSwap activity stays high (Timeouts and Latency) is a hands-on troubleshooting drill. The incident is over, but swap churn remains elevated and keeps latency unpredictable for the rest of the day. Linux Service Operations needs to be checked by narrowing scope, recent change, a...LinuxAdvanced25 minProLINUX-023Ephemeral disk pressure kills cache but not the root causeEphemeral disk pressure kills cache but not the root cause is a hands-on troubleshooting drill. Cleaning temp files buys time, but write amplification from another process quickly recreates the same disk pressure. Linux Service Operations needs to be checked by narrowing scope...LinuxAdvanced26 minProLINUX-040Overlay mount reports no space left on device while df still shows free blocksContainer creation fails with a storage error even though normal disk and inode checks look healthy, pointing to overlay, mount, or lower-level storage limits rather than a simple full disk.LinuxAdvanced27 minProLINUX-029Readonly remount happens only after storage latency burstThe filesystem looks healthy most of the time, but latency spikes trigger IO errors that remount the volume as readonly.LinuxAdvanced28 minPro