정보처리기사
467 incident response problems that help with 정보처리기사 prep.
먼저 읽을 가이드
추천 문제
All problems (467)
CICD-003Adding an approval stage to an unverified production deployment pipelineA template-style problem for designing an approval flow and staging verification with per-environment deployment boundaries.CI/CDBeginner15 minProLINUX-393An application writes Unicode filenames correctly while a backup or sync service still runs under the old locale and drops part of the path set during a staged decommissionThe system stores the files and one scheduled path can no longer see them all. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.LinuxIntermediate15 minProLINUX-102Journal rate limiting suppresses the real crash pattern and the team chases the wrong processOperators only see a handful of logs because the journal quota is dropping the repetitive fault signal during the outage window.LinuxIntermediate15 minProLINUX-123sudo timestamp caching is per-tty, but the automation wrapper assumes a shared session and fails only on the second commandPrivilege escalation seems inconsistent because the execution environment changed the terminal scope of the cached credential.LinuxIntermediate15 minProLINUX-330A login shell exports one locale while the noninteractive service unit inherits another and decimal parsing diverges across the same host during a failover rehearsalNothing is wrong globally; the environment contract is simply different by execution mode. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.LinuxIntermediate16 minProLINUX-511An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate17 minProLINUX-571An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate18 minProLINUX-691An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate20 minProLINUX-028Container host shows low CPU while one cgroup throttles hardContainer host shows low CPU (Resource Exhaustion) is a hands-on troubleshooting drill. Overall node utilization looks safe, but one service is heavily throttled because its cgroup limit is too low. Linux Service Operations needs to be checked by narrowing scope, recent change...LinuxIntermediate20 minProLINUX-025Socket backlog tuning hides application accept bottleneckKernel queue settings were increased, but the service still stalls because the application cannot drain connections fast enough.LinuxIntermediate22 minProLINUX-810An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate23 minProLINUX-1170An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate29 minProCICD-136A coverage gate compares against a stale default-branch baseline after the repository renamed its main branchNew tests are good enough, but the gate keeps failing because it still measures against a branch that no longer receives changes.CI/CDIntermediate14 minProLINUX-153A profile script exports a locale unavailable on one batch host, and only the nightly report job starts misparsing decimal inputEverything interactive seems normal, but one noninteractive environment inherits a broken locale assumption.LinuxIntermediate14 minProLINUX-139The login shell sources an unexpected umask from an earlier profile.d file and new release artifacts inherit overly broad permissionsFile mode drift appears random until the team notices which profile file wins lexically for interactive release sessions.LinuxIntermediate14 minProCICD-381A pipeline pins the runner image while the fetched bootstrap script still resolves the latest policy bundle from a mutable channel during a staged decommissionThe execution environment is frozen and its policy input is not. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDIntermediate15 minProCICD-140A release notes bot creates the Git tag before the artifact upload finalizes, and downstream consumers fetch a version with no binaries yetThe version appears published to automation, but its payload is still in flight when the deployment job tries to consume it.CI/CDIntermediate15 minProCICD-156A test flake suppressor matches any timeout string, and the real deadlock regression gets auto-muted during release qualificationNoise reduction automation masks the exact new symptom the release gate was meant to catch.CI/CDIntermediate15 minProCICD-149The build step caches test reports by branch name, and a recreated hotfix branch reuses stale pass results from the previous incidentNo tests actually ran for the new code, but the cache key made the workflow appear green.CI/CDIntermediate15 minProCICD-198A branch-based cache key reuses stale test evidence during a failover rehearsalThe workflow turns green even though the current code path never executed fresh validation. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate16 minPro