Skip to content

Interview question · Software, Data & Model Supply Chain

Harden a CI/CD pipeline: runners, secrets, pinned actions and branch protections.

The pipeline holds the keys to production and runs code from pull requests. The scored answer separates untrusted from privileged work, pins what it executes, and removes long-lived secrets.

mediumNewPreparation tags: Google, Microsoft, AmazonUpdated Nov 2026

The pipeline holds the keys to production and runs code from pull requests. The scored answer separates untrusted from privileged work, pins what it executes, and removes long-lived secrets.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 6 follow-ups like an interviewer would

A company's CI/CD system builds every service and deploys straight to production, using long-lived cloud keys stored as pipeline secrets and self-hosted runners.

  1. Why treat CI/CD as production infrastructure?
  2. What should replace long-lived cloud keys?
  3. What if pull requests from forks trigger workflows?
  4. What about third-party actions and tools?
  5. What is the risk with self-hosted runners?
  6. How would you harden the pipeline?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.