Where should production secrets live relative to CI?
PICTURE THIS: STACK VS QUEUE
Simple meaning
CI needs deploy credentials, not the production JWT secret, if the runtime can inject secrets itself.
WHY — Deployment instead of guessing?
Why interviewers care about Deployment:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1CI needs deploy credentials,
not the production JWT secret, if the runtime can inject secrets itself.
- 2Cloud secret managers and
locked environment configs beat copying .env files into images.
- 3Rotate credentials when people
leave or when a leak is suspected.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
CI needs deploy credentials, not the production JWT secret, if the runtime can inject secrets itself. Cloud secret managers and locked environment configs beat copying .env files into images.