AWS DevOps Engineer Professional
942 incident response problems that help with AWS DevOps Engineer Professional prep.
먼저 읽을 가이드
추천 문제
All problems (942)
CICD-1273A cache hit restores successfully but the next job failsA matrix build spanning x64 and arm64 starts showing nondeterministic failures after cache keys were simplified.CI/CDAdvanced17 minProCICD-1277A containerized build works but later jobs failA pipeline with service containers and generated artifacts starts failing only on later shell-based packaging or cleanup steps.CI/CDAdvanced17 minProCICD-138A deployment circuit breaker watches the startup probe, but the one-off migration pod shares the same label and trips the release incorrectlyApplication pods are healthy, yet rollout halts because the failure budget includes a different workload type with a separate lifecycle.CI/CDAdvanced17 minProCICD-151A deployment freeze opens for one hour, but the delayed approval queue starts the rollout after the window closes and the policy engine revokes credentials mid-releaseEverything was approved at the right time, yet execution drifted outside the governance boundary.CI/CDAdvanced17 minProCICD-1285A matrix release publishes the right artifacts but the production deploy reuses staging metadataA signed release pipeline shows matching artifacts and later production deploys an older or partially updated manifest.CI/CDAdvanced17 minProCICD-1299A multi-arch image promotion succeeds but arm64 pods fail laterA team adds multi-arch release support and later one architecture alone begins failing cluster admission.CI/CDAdvanced17 minProCICD-157A package signing key rotates in the build stage, but the downstream install test still trusts only the old fingerprint and rejects the freshly built repositoryThe package was published correctly, yet the validation environment pins a previous trust root.CI/CDAdvanced17 minProCICD-1287A private package restore works on push events but fails on pull_requestA private package restore works on push events but fails on pull_request focuses on Identity And Access and asks the reader to isolate the key signal in GitHub. Different GitHub event types can run the same pipeline under materially different secret...CI/CDAdvanced17 minProCICD-1263A private submodule checkout worked before repository hardening but now failsCI/CD incident scenario used for structured troubleshooting practice.CI/CDAdvanced17 minProCICD-1268A private submodule checkout worked before repository hardening but now failsA security hardening change reduces token permissions and suddenly only private submodule checkout begins failing in CI.CI/CDAdvanced17 minProCICD-252A queued ChatOps rerun inherits stale authorization after the original release freeze window already closed during a failover rehearsalThe command looks approved from the chat log while execution happens under a no-longer-valid auth context. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced17 minProCICD-393A release artifact is immutable while the runtime startup still downloads a policy pack from a bucket with newly narrowed cross-account access during a staged decommissionThe artifact did not change, but its boot dependency contract did. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProCICD-1281A reusable workflow can mint an OIDC token in one repository but fails in anotherA deployment pipeline is refactored into a shared workflow and later only one repository can no longer assume the cloud role.CI/CDAdvanced17 minProCICD-1258A runner was deleted and re-registered, but jobs still bounceA team replaces a broken self-hosted runner and the new one keeps cycling between connected and unusable states.CI/CDAdvanced17 minProCICD-1271A setup-node cache step succeeds on hosted runners but hangs on one self-hosted repoA monorepo using workspaces starts failing only on one self-hosted lane after cache support is enabled.CI/CDAdvanced17 minProCICD-1318An artifact signing step succeeds and provenance verification failsA release pipeline renames or relocates packaged output between signing and promotion and later attestation checks start failing.CI/CDAdvanced17 minProCICD-153An emergency patch bypasses the normal image scan stage, but admission still expects the scan metadata label and production refuses the deploymentThe fast path skips validation intentionally, yet the runtime guardrail still requires proof that only the normal path produces.CI/CDAdvanced17 minProCICD-132An ephemeral runner image misses the internal CA root and only private registry pulls fail after autoscaling adds new workersLegacy workers continue working, but new ones cannot trust the organization registry chain.CI/CDAdvanced17 minProCICD-158An IaC drift detector ignores a tag-only difference, but the omitted tag controls an SCP exception and the next deploy fails in production onlyThe infrastructure looks equivalent in shape, yet one governance-relevant tag changed the allowed behavior.CI/CDAdvanced17 minProCICD-375An infrastructure drift policy ignores deleted optional resources while a recovery run still expects their outputs to exist for rollback wiring during a staged decommissionThe live state looks acceptable until rollback tries to consume outputs from deleted optional blocks. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minPro