AWS DevOps Engineer Professional
942 incident response problems that help with AWS DevOps Engineer Professional prep.
먼저 읽을 가이드
추천 문제
All problems (942)
CICD-363A migration approval checks the application schema version while one asynchronous worker still runs the old reader contract in parallel during a staged decommissionThe release gate inspects the main service and misses the parallel consumer that still depends on the old shape. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProCICD-294A package provenance check validates one tarball while the deploy step consumes a repacked archive from a mirror during a failover rehearsalSupply-chain checks pass on the source artifact, but the runtime path uses a derived archive that was never verified. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-306A preview deployment signs in with a lower-privilege identity and the later promote step assumes those same credentials are still sufficient during a failover rehearsalThe early environment works, but the promotion path needs a broader scope that the pipeline never refreshes. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-141A release candidate is promoted from staging with the right image digest, but the production values file still points at the old feature-flag namespaceThe artifact is correct, yet behavior differs because runtime configuration still references an earlier control-plane context.CI/CDAdvanced17 minProCICD-345A release workflow restores a cached dependency graph that no longer matches the promoted lockfile lineage during a staged decommissionBuild reproducibility appears intact, but the promoted dependency graph was reconstructed from stale lineage metadata. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProCICD-1234A reusable test workflow publishes clean results but the caller still marks the run failedA diagnostic or flaky-report step should be informational, but the calling workflow still blocks merge because the status contract was not separated cleanly.CI/CDIntermediate17 minProCICD-192An artifact retention job keeps the image and removes the detached attestation during a failover rehearsalThe primary artifact remains available while admission or provenance checks lose the supporting proof they depend on. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-1249An artifact upload succeeds but a later job downloads an empty bundleA build step writes files after creating the archive path, and a downstream consumer later downloads an artifact that looks valid but has no useful payload.CI/CDIntermediate17 minProCICD-1215Deployment waits foreverA centralized reusable deploy flow still shows a waiting gate after an environment approval was already granted.CI/CDIntermediate17 minProCICD-1219Environment file generation succeeds but later steps read stale valuesA deploy job keeps using an old endpoint even though the pipeline visibly generated the new env file earlier.CI/CDIntermediate17 minProCICD-1227Package restore succeeds but the later build still uses the old dependency graphA monorepo branch changes one workspace lockfile and CI still behaves as if the old dependency tree is present.CI/CDIntermediate17 minProCICD-276Preview environment teardown removes DNS before certificate validation jobs finish probing the old hostname during a failover rehearsalThe environment lifecycle cleanup is correct for cost control and too early for the remaining verification path. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-121Protected environment reviewers are configured, but a branch rename leaves the production rule attached to the old pattern and deployment bypasses approvalThe release pipeline still sees a valid environment, yet the protection logic no longer matches the new main branch name the team now uses.CI/CDAdvanced17 minProCICD-1224Scheduled workflow behaves differently from manual dispatchA nightly deployment behaves differently than the manually triggered path even though both invoke the same workflow file.CI/CDIntermediate17 minProCICD-387A canary job compares median latency while one percentile tail explodes only for a tenant class routed through a different auth provider during a staged decommissionAggregate health stays green while a routed subset proves the release is unsafe. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced18 minProCICD-150A canary metric query excludes the holiday traffic segment and the release looks successful onlyThe analysis engine reports low error rates, yet its sampling window omits the exact traffic cohort that reveals the bug.CI/CDAdvanced18 minProCICD-282A deployment gate reuses the latest successful build from the wrong branch lineage during a failover rehearsalThe artifact is valid, but the gate promotes a build that never belonged to the current release branch. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced18 minProCICD-160A final approval step signs off the release manifest, but the deploy job re-renders templates afterward and ships a different object set than was reviewedApproval happened on one representation of the release, while execution used another.CI/CDAdvanced18 minProCICD-487A preview environment uses feature flags from production defaults and hides...A preview environment uses feature flags from production defaults and hides... focuses on ci-cd-workflow-debugging and asks the reader to isolate Permission Denied in AWS. 실무에서는 ci-cd-workflow-debugging 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate18 minProCICD-222A promotion rule trusts semantic version metadata while mirror sync rewrites the build metadata during a failover rehearsalThe release artifact keeps its version label, yet the mirror path mutates the metadata field one downstream gate still uses. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced18 minPro