Interview prompt
Problem context
Egress is 22% of cloud spend. Teams replicate data broadly, services cross availability zones chattily, customers export large datasets, and a multi-cloud recovery plan assumes moving petabytes quickly. Finance asks for savings without creating deeper vendor lock-in.
Skills being evaluated
data-flow economicsplacement designportability strategyrecovery realism
The full reasoning guide is part of Pro
The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.
Sign in to continueWhat the full guide covers
Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize