Cloud Engineer — Landing Zone & Identity
Account structure, networking, workload identity and how you keep secrets out of your applications.
- Landing zones
- Networking
- IAM
- Secrets
- Duration
- 35 min
- Questions
- 4 questions
- Difficulty
Design for zone failure with a five-minute recovery objective, then justify the bill you just created.
1. How would you lay out accounts or subscriptions, networking and identity for a company moving its first twenty workloads to the cloud?
~3 minChecks landing-zone thinking rather than single-VPC habits.
2. A workload must survive the loss of an availability zone with under five minutes of downtime. What architecture do you propose and what does it cost you?
~3 minTests resilience design paired with honest cost framing.
3. Cloud spend grew 30% quarter over quarter with flat traffic. How do you find the cause and stop the bleeding?
~3 minFinOps instinct and evidence gathering.
4. Explain how you grant an application access to a managed database without long-lived secrets.
~3 minChecks identity fundamentals.
Warm-up & context · 5 min
Interviewer intro, your background, how the session runs.
Core questions · 27 min
Role-specific questions with live follow-ups based on your answers.
Deep dive · 9 min
One topic explored to the edge of your experience.
Your questions & wrap · 5 min
Close the loop and hand over to feedback generation.
Account structure, networking, workload identity and how you keep secrets out of your applications.
Design a multi-region delivery and rollback strategy, then defend the operational cost of your choices.
Decompose a product requirement into services, data ownership and contracts, then defend the boundaries you drew.