How would you set up accounts, permissions and guardrails across dozens of teams so they move fast but cannot create risky public resources?

What the interviewer is looking for

• This question tests identity & access management. Applies least privilege, roles over long-lived keys, account structure and guardrail policies, with examples.
• Strong answers: Multi-account structure, organisation-level policies, preventive and detective controls, single sign-on with roles, and self-service templates.
• Likely follow-up: How would you handle a team that needs an exception?

Another way it may be asked: Fifty teams share your cloud. How do you let them build freely while stopping things like a public storage bucket full of customer data?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• What does least privilege mean in cloud access management, and how would you apply it to a new developer joining the team?
• If you had to host a simple web app with a database in the cloud, which services would you pick, and why?
• Explain the difference between a public and a private subnet, and what kinds of resources you would put in each.
• An app server in a private subnet cannot reach an external payment service. How do you troubleshoot that connection?
• How do you structure infrastructure code so several teams and environments can reuse it without stepping on each other?

Browse all questions