Skip to content

Interview question · Cryptography, PKI & TLS

Design an internal PKI for tens of thousands of services, devices and developers: hierarchy, issuance, revocation and failure.

Issuing a certificate is easy. Knowing every certificate you issued, renewing them before they expire, and surviving the day a CA key leaks is the design.

expertNewPreparation tags: Google, Microsoft, AmazonUpdated Nov 2026

Issuing a certificate is easy. Knowing every certificate you issued, renewing them before they expire, and surviving the day a CA key leaks is the design.

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

You must design an internal PKI for service-to-service TLS across thousands of workloads, laptops and a code-signing pipeline.

  1. How should the root CA be handled?
  2. How should issuing CAs be separated?
  3. How should certificates be issued?
  4. How long should certificates last?
  5. What operational pieces are needed?
  6. What PKI design would you propose?

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.