Requirements to Architecture Mapping Questions
Bridges business and customer requirements to concrete architectural or non functional specifications. Candidates should extract throughput, concurrency, availability, latency, durability, security, compliance and budget constraints from scenarios and translate them into measurable goals such as requests per second targets, latency SLOs, durability levels, retention and encryption requirements. The topic includes creating a requirements matrix that directly informs component choices, capacity planning, and trade off justification.
EasyTechnical
0 practiced
Explain how latency budgets differ from SLOs and describe a simple approach for allocating an end-to-end latency budget across these components: client rendering, CDN, edge LB, API gateway, service A, service B, and downstream third-party payment API.
MediumSystem Design
0 practiced
Scenario-based: An enterprise customer requires audit logging of all administrative actions with immutable retention for 10 years and must be able to export logs for e-discovery. How would you translate this into architecture requirements (storage class, immutability features, indexing, export APIs) and cost considerations?
EasyTechnical
0 practiced
Describe three common trade-offs when mapping a durability requirement (e.g., 11 9's) to architecture decisions for event logs and backups. For each trade-off, state the architectural options (replication, erasure coding, multi-region backups) and cost/complexity implications.
MediumTechnical
0 practiced
Scenario: The customer requires 'no single point of failure' for a core API but will only budget for a single active region. Propose architectural mitigations to meet 'no single point of failure' within a single region and explain the remaining risks that must be communicated to the customer.
HardTechnical
0 practiced
Technical-domain: For a streaming API that must guarantee 'at-least-once' delivery and 99.999% durability, explain how you would translate those into component-level requirements: message broker durability settings, consumer checkpointing, and replay capability. Include measurable RPO/RTO implications.
Unlock Full Question Bank
Get access to hundreds of Requirements to Architecture Mapping interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.