1. Coupling intermediate Multiple choice

    At Meesho-scale marketplace growth, catalogue, pricing, order and logistics teams all read and write one shared product table, each deploying schema changes independently. Which kind of coupling is this, and why does it get worse rather than plateau?

    2 min answer couplingmeeshomarketplaceshared-database
  2. CQRS intermediate Multiple choice

    A team proposes CQRS for a CRUD admin panel because reads are slow. Is that the right call?

    2 min answer cqrsover-engineeringread-model
  3. Cross-Border Transfer intermediate Multiple choice

    An EU-based SaaS product runs entirely in Frankfurt. Its 24-hour support rota includes engineers in a country without an adequacy decision, who can view customer records to diagnose issues. Legal flags this as a cross-border transfer. Which control best addresses the finding?

    3 min answer cross-border-transfersupport-accessdata-minimisationscc
  4. Cutover Planning intermediate

    A cutover is planned for a Sunday night. What must be prepared beyond the technical steps, and what is the most commonly missing item?

    2 min answer ackocutoverrollbackrunbook
  5. Cutover Planning intermediate

    A platform must cut over a critical service. What does a cutover plan need beyond the switching steps?

    2 min answer cutoverrollbackrehearsalcommunication
  6. Cutover Planning intermediate

    What is in a cutover plan besides the steps, and what would you rehearse?

    1 min answer cutoverrollbackabort-criteriarehearsal
  7. Dashboards intermediate

    A platform has hundreds of dashboards and engineers cannot find the right one during an incident. How should dashboards be structured?

    2 min answer dashboardsincident-responsehierarchybooking
  8. Dashboards intermediate

    Design the one dashboard your team opens first during an incident. What is on it and what is deliberately not?

    2 min answer dashboardsincident-responsedesignobservability
  9. Dashboards intermediate

    Review this incident dashboard. One page holds 28 panels, the default range is 6 hours, auto-refresh is 10 seconds, the scrape interval is 30 seconds, and every panel plots a 5-minute rate over per-pod series for a 900-pod fleet. During the last incident the page took 40 seconds to load and two panels timed out. What would you remove, what would you change, and what would you leave alone?

    3 min answer dashboardsquery-costresolutionincident-response
  10. Dashboards intermediate

    Your metrics pipeline normally makes data queryable about 20 seconds after it is emitted. During a large incident the ingestion tier falls behind and the lag grows to four minutes. Nothing is lost. Walk through what happens to the on-call engineer's decisions.

    3 min answer telemetry lagincident responserollbackalerting
  11. Data Architecture intermediate

    A dashboard query that took 200ms now takes 40 seconds. The table has grown to 200 million rows. Walk me through diagnosis and fix, including what you would not do.

    3 min answer indexingquery-performancedatabasesdiagnosis
  12. Data Architecture intermediate

    A product catalogue page does 40,000 reads per second against a database that can serve 5,000. Walk me through the caching design, including what happens at 3 AM when the cache is empty.

    2 min answer cachingperformancestampedeavailability