1. Backend for Frontend intermediate

    A platform has a backend-for-frontend per client, and they have diverged with duplicated logic. Is BFF still the right pattern?

    2 min answer bffduplicationownershipshared-logic
  2. Backend for Frontend intermediate

    A product runs on web, iOS, Android and a television app. The shared API team is the bottleneck for every client change. Design the fix.

    3 min answer bffapi-designnetflixownership
  3. Backend for Frontend intermediate

    A quick-commerce platform serves a mobile app, a web app and a partner API from the same services. When does a backend-for-frontend earn its place?

    2 min answer zeptobffaggregationclients
  4. Backend for Frontend intermediate

    A travel platform with Booking.com's catalogue breadth replaces nine client-side calls with one backend-for-frontend call that fans out to the same nine services. Mobile p99 improves by 40% on the first day. Each of the nine services holds 99.9% availability. What has the team given up, and when does the bill arrive?

    3 min answer bffaggregationavailabilitypartial rendering
  5. Backend for Frontend intermediate

    Several client applications with different needs consume the same backend. When is a backend-for-frontend justified, and when does it become an unowned distributed monolith?

    2 min answer bffapi-designclientsownership
  6. BI Governance intermediate Multiple choice

    A company certifies 400 of its 4000 dashboards with a badge an owner and a review at the moment the badge is granted. Eighteen months later an audit finds the certified set has the highest proportion of reports whose underlying model has changed since certification. Review the design. Which single change matters most?

    2 min answer bi governancecertificationstalenessattestation
  7. BI Governance intermediate

    A travel company has thousands of dashboards, several conflicting definitions of the same metric, and a large BI bill. Diagnose it.

    1 min answer bi-governancemetric-consistencysprawlcost
  8. BI Governance intermediate

    Two dashboards disagree about revenue. What mechanism would have prevented it, and what would not?

    2 min answer bi-governancesemantic-layercertificationdefinitions
  9. Bias & Fairness Controls intermediate

    A lending team's fairness dashboard shows approval-rate parity across protected groups, refreshed monthly, green for six months. Review it. What would you remove, what would you change, and what would you leave alone?

    3 min answer fairnessmetricsmonitoringproxies
  10. Bottleneck Analysis intermediate

    A service is slow and the team disagrees about the cause. What method identifies the actual bottleneck rather than the suspected one?

    2 min answer swiggybottleneckmethodmeasurement
  11. Bounded Contexts intermediate

    Review this context map. Eleven bounded contexts, and nine of the relationships between them are shared kernel: a common library of domain types that every team imports and any team may change. The teams report that releases have to be coordinated. What would you change, what would you keep, and how would you argue it?

    2 min answer domain driven designbounded contextsshared kernelcoupling
  12. Branching Models intermediate

    A design platform in the mould of Canva moves 90 engineers off long-lived feature branches onto trunk-based development with a merge queue. Six weeks later the mean branch still lives four days and the trunk is no healthier. Review this change. What did they actually need to change?

    2 min answer canvatrunk-based-developmentcode-reviewbranch-lifetime