AWS DevOps Engineer Professional
942 incident response problems that help with AWS DevOps Engineer Professional prep.
먼저 읽을 가이드
추천 문제
All problems (942)
CICD-1221Reusable workflow secret is marked required but still arrives blankA deployment moved behind a reusable workflow and only the environment-backed secret fails to appear.CI/CDAdvanced20 minProCICD-096Rollback policy depends on ALB 5xx but the failure is only visible in gRPC status codesThe release is unhealthy, yet rollback never triggers because the monitored signal ignores application-layer failure semantics used by this service.CI/CDAdvanced20 minProCICD-1211Matrix jobs all succeed but the release step still sees only the last computed outputA matrix workflow computes per-target metadata, yet the downstream stage reads only one value because outputs are not aggregated the way the team assumed.CI/CDAdvanced21 minProCICD-028Retry policy re-runs destructive migration job twiceRetry policy re-runs destructive migration job twice is a hands-on troubleshooting drill. A generic retry wrapper helps flaky steps but becomes dangerous when applied to a migration or cleanup command. GitHub GitHub Actions Workflows needs to be checked by narrowing scope, rec...CI/CDIntermediate21 minProCICD-067Argo Rollouts analysis never promotesTraffic and pods look healthy, yet automated promotion never happens because the analysis provider keeps evaluating metrics for an old release label set.CI/CDAdvanced22 minProCICD-039ECR lifecycle cleanup deletes digest still referenced by promotion manifestThe production promotion manifest points to an immutable digest, but registry cleanup removes the only copy before the delayed deployment window starts.CI/CDIntermediate22 minProCICD-1212OIDC deploy works in the main workflow but fails after being moved into a reusable fileThe same shell commands now lose cloud auth because the reusable boundary no longer exposes the permission surface the original workflow relied on.CI/CDAdvanced22 minProCICD-1206Reusable workflow inherits secrets but one environment secret is still blank at runtimeThe reusable deployment starts normally, yet one secret resolves blank because the call boundary does not expose the environment-scoped secret the way the team assumed.CI/CDAdvanced22 minProCICD-1202Deploy key works for one checkout path but package restore still fails on a second private repositoryOne private repository is accessible, yet restore still breaks because a second dependency path needs a different credential scope than the first successful checkout.CI/CDAdvanced23 minProCICD-1210Reusable workflow runs by tag but an internal checkout still resolves against caller contextThe reusable workflow is versioned by tag, yet one internal action path still follows caller context and breaks unexpectedly.CI/CDAdvanced23 minProCICD-061Argo CD app-of-apps sync waves leave the platform upgrade stuck on a child dependencyThe root application looks healthy, but one child app never becomes ready because the sync ordering assumes a dependency finished before its CRDs actually became usable.CI/CDAdvanced24 minProCICD-1204Container registry login succeeds but build still pulls anonymouslyA registry login step copied from public examples looks green. The later builder still pulls anonymously because it uses a different execution context than the shell that performed the login.CI/CDAdvanced24 minProCICD-1192Docker layer cache grows until the self-hosted runner exhausts disk and silently poisons later jobsBuild jobs keep succeeding until the runner fills with old image layers and future runs fail in strange places because disk pressure is now shared across every pipeline.CI/CDAdvanced24 minProCICD-1199Container image scan passes on build but release still ships an older vulnerable tagThe current build artifact is scanned successfully, yet the release pipeline promotes a different tag or digest that was never covered by the scan result.CI/CDAdvanced25 minProCICD-1189Matrix integration fan-out turns one shared preview stack into a false failure factoryParallel jobs hit the same preview environment and make stable application code look flaky under shared-state contention.CI/CDAdvanced25 minProCICD-054Buildx multi-arch pipeline failsThe image builds successfully for one architecture, but the overall publish stage fails when temporary layers and cache exports exceed the runner disk budget.CI/CDAdvanced26 minProCICD-1197OIDC deploy works for the workflow caller but fails inside a reusable deployment workflowThe top-level job can authenticate to AWS, yet the reusable deployment workflow fails because the assumed identity boundary differs inside the called workflow.CI/CDAdvanced26 minProCICD-023Artifact signing step succeeds locally but fails in CI runnersThe same signing command works on a developer machine but breaks in ephemeral runners because the key material and trust chain differ.CI/CDAdvanced27 minProCICD-1182Self-hosted runner leaves root-owned workspace after Docker build stepOne privileged container step writes files as root into the shared workspace, breaking later jobs on the same self-hosted runner.CI/CDAdvanced27 minProCICD-059Artifact attestation exists but the deploy gate verifies the wrong repository subjectSupply-chain verification is enabled, yet trusted artifacts are rejected because the admission or deploy gate expects a different repository identity than the builder actually signs.CI/CDAdvanced28 minPro