You already know: how to scope a pilot (previous lesson); cloud networking, IAM and infrastructure as code (D17); agent and prompt-injection security (D19); RAG over documents (D8).
Why this matters for Atlas. A pilot that works in your account proves the model works. A deployment that works in theirs proves the business works. Enterprise customers in education, health, finance and government rarely let regulated data leave their environment, so the FDE's job is to bring the system to the data: pick a deployment model, draw the data boundary, carry the customer's permissions all the way into retrieval, and ship something they can run and you can still upgrade. Get this wrong and the security review, not the model, kills the deal.
1. Pick the deployment model
The question. Where does the system run, and who operates it?
Start from nothing. There are four common answers, and they trade customer control against your operational burden: