← 문제 라이브러리
CI/CD Beginner CICD-1617 · 8 min

A GitHub deployment succeeds and one post-deploy check still reports old health

무료
시나리오

One post-deploy verification path still shows stale health after a regional release.

먼저 볼 것
  • Identify the primary failure signal in the The New Delivery Arrived and One Inspector Still Read the Checklist Stored in the Drawer Without the Region Sticker scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
점검 체크리스트
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
복구와 재발 방지

Trace cache keys before clearing the entire verification job.

같이 보면 좋은 질문
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.