Hi
RealGold,
Fair question, and I'd rather answer the deeper part of it than the surface part.
On frequency:
MSR is a guaranteed part of Data Insights, and sets built exactly like this one, two tabs with one of them a dense table, plus a rule stated in the text that you have to apply to the data, show up regularly. This particular set sits on the harder end of the scale, mostly because of how many near-identical definitions it juggles. So no, you won't see six questions this punishing in a row. But you will absolutely see the
skills it's testing.
And that's the part worth your attention. Look at what this set actually asks you to do.
1. Hold two definitions apart when they're deliberately similar. ROHH and ROB differ by one detail: whether you leave the hotel, or just leave the block. Get them mixed up and every number that follows is wrong. This is term sheets. This is pricing tiers. This is two vendor contracts where clause 7 differs by a single word, and that word is worth $2M.
2. Compare total cost, not one component. Q1 and Q2 fail you if you compare room rates and forget that the registration fee moves in the opposite direction. Cheaper room, pricier registration: which wins? That trade-off structure is the single most common analytical error in business. People approve the lower sticker price and eat the higher total.
3. Apply a stated policy to messy data. Q3 hands you a new rule (25% reimbursement) and asks what it implies. Translating "the hotel loses revenue" into "lowest rate < 0.75 x block rate" is exactly what you do with a debt covenant, a discount-approval threshold, or a rebate clause.
4. Work out who actually bears the loss. Q4 has no arithmetic at all. The room-service waiter on tips loses, the salaried front-desk manager doesn't, the speaker on a fixed fee doesn't. That's fixed vs. variable cost incidence, the foundation of unit economics and of every "who is exposed if volume drops" conversation you'll have.
5. Read scope precisely. Q3 says "at least one conference." Asiawest hosts three. Check one, answer No, and you're wrong, not because you can't compute, but because you generalized from partial data.
Those five things are the job description of a good analyst and a good business leader. A difficulty rating is just a classification. So if you got this wrong, don't log it as "hard MSR question." Log it as
which of those five broke down, because that's the thing that will break down again, in a meeting, with real money.
So yes: DEF work on it.