Skip to content

Interview question · Cloud, Container & AI Infrastructure Security

Design an inference platform's control plane so that a compromised serving node cannot replace, roll back or steal models.

Serving nodes parse hostile input all day, so assume one falls. The design question is what it can reach: the registry, other tenants' models, the signing keys, or nothing at all.

hardNewPreparation tags: Google, Amazon, MicrosoftUpdated Nov 2026

Serving nodes parse hostile input all day, so assume one falls. The design question is what it can reach: the registry, other tenants' models, the signing keys, or nothing at all.

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

An inference platform has a control plane that uploads, approves and deploys models, routes traffic and manages keys, and serving nodes currently share its credentials.

  1. Why separate the control plane from the data plane?
  2. What should serving nodes have?
  3. What should serving nodes be unable to reach?
  4. How should deployments work?
  5. How do you detect control-plane misuse?
  6. What architecture would you require?

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.