System-Design Thought-Process Quiz

Q1. Which activity best exemplifies the ‘Trade-off & Risk Ledger’ track? Running load tests to discover performance limits.
Documenting rejected design options with reasoning so future teams see the context.
Implementing feature flags for safe rollouts.
Adding metrics and alerts to production services.

Q2. When you ask, “Can we run it at 3 a.m. when the pager goes off?” you are invoking which track? Operational Reality Check
Quality-Attribute Radar
Developer-Experience Lens
Systems Thinking

Q3. Selecting two or three key ‘-ilities’ to optimise at the expense of others is part of: Change-Resilience Thinking
Quality-Attribute Radar
Ethics, Safety & Compliance
Problem–Opportunity Framing

Q4. Feature flags, A/B tests, and shadow traffic belong primarily to which track? Feedback Loop Design
Communication & Narrative
Trade-off & Risk Ledger
Operational Reality Check

Q5. Ensuring least-privilege data access and auditability is most directly tied to: Systems Thinking
Developer-Experience Lens
Ethics, Safety & Compliance
Continuous Reflection & Craftsmanship

Q6. Creating a component diagram **and** an interaction diagram for neighbouring systems demonstrates: Systems Thinking
Problem–Opportunity Framing
Change-Resilience Thinking
Operational Reality Check

Q7. Adding structured, one-sentence success criteria to a design document fulfils which track? Problem–Opportunity Framing
Trade-off & Risk Ledger
Quality-Attribute Radar
Developer-Experience Lens

Q8. Which practice best supports Continuous Reflection & Craftsmanship? Using circuit breakers to handle downstream failures.
Scheduling periodic design-debt reviews and micro-retrospectives.
Defining SLIs and SLOs early.
Tagging services with version metadata.

thinking