Skip to content

Interview question · Software, Data & Model Supply Chain

Write a check that verifies downloaded model and dependency files against pinned hashes before they are used.

Pinning a version is not pinning content. The scored answer verifies every file against a recorded hash, treats unexpected and missing files as failures, and explains where the lockfile's own trust comes from.

mediumNewPreparation tags: Google, Microsoft, Hugging FaceUpdated Nov 2026

Pinning a version is not pinning content. The scored answer verifies every file against a recorded hash, treats unexpected and missing files as failures, and explains where the lockfile's own trust comes from.

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 build installs Python dependencies and downloads a model from a lockfile that records a SHA-256 hash for each package and model file.

  1. Why pin by content rather than version or name?
  2. What must the verifier check?
  3. What if the model has many files?
  4. What if the lockfile itself is modified?
  5. Does a hash match mean the content is trustworthy?
  6. How would you implement artefact verification?

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.