Your question is Late-Arriving Dimensions vs Facts. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Explain the difference between a late-arriving dimension and an early-arriving fact, and how would you handle this scenario in a payments database at Rippling?
Clarify how you would preserve payment records, maintain dimensional history, and correct records when related dimension data arrives later. Address pipeline ordering, idempotency, data quality, backfills, and monitoring. State any assumptions you would validate about the source system, warehouse, latency requirements, and payment identifier design.