Skip to content

Interview question · Cryptography, PKI & TLS

Who decides which root CAs your devices trust? Explain root programs, trust stores per runtime, distrust events and root expiry.

There is no single list of trusted roots. Browsers, operating systems, language runtimes and container images each carry their own, updated on their own schedules, and production outages follow from the differences.

hardEssentialNewPreparation tags: Google, Apple, MicrosoftUpdated Nov 2026

There is no single list of trusted roots. Browsers, operating systems, language runtimes and container images each carry their own, updated on their own schedules, and production outages follow from the differences.

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 CA your company uses is announced as distrusted by a major browser for certificates issued after a cut-off date.

  1. Who decides which CAs are trusted?
  2. Which trust store does each client use?
  3. What does a distrust with a cut-off date mean?
  4. What should the company do?
  5. What about internal clients and pinning?
  6. What would your response plan be?

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.