Short explicit parent-child flow
Use props and emits
Best fitUse provide and inject
ReasonableTRADEOFF BATTLE
SettingsPage owns the current draft, validation state, and save actions. Under it, the page has several layout layers such as SettingsSection, SectionCard, and FieldGroup, and the real leaf components are toggles, text inputs, and status chips. Those leaf components need access to the shared form context and must report user changes back up. One teammate wants to keep everything with props and emits so the data flow stays explicit. Another teammate wants to provide a narrow settings context from the page and inject it in the deep field components so the layout wrappers stop forwarding props they do not actually care about. In the interview, the panel asks which direction you would defend.
You are not looking for the universal winner. You are picking the strongest answer for this prompt.
Pick the option you would defend, then reveal the stronger interview framing for this prompt.
STRONG ANSWER
Watch how the answer changes as the scenario changes. This is where tradeoff thinking starts to feel real.
Use props and emits
Best fitUse provide and inject
ReasonableUse props and emits
ReasonableUse provide and inject
Best fitUse props and emits
ReasonableUse provide and inject
StretchOnce the answer is revealed, compare all options. The selected card stays highlighted so you can pressure-test your own instinct.
Alternative
Alternative
A strong answer survives follow-up pressure. These are the questions most likely to expose shallow reasoning.
Pushback
Pushback
Pushback
This is often the fastest way to internalize the difference between opinions and interview-grade reasoning.
Weak answer
I would use provide and inject because props drilling is bad.
What it is missing
Decent answer
I would probably use provide and inject because the field components are nested deeply and forwarding props through wrappers feels noisy.
What it is missing
Strong answer
For this prompt I would provide a narrow settings context from the page and inject it into the deep field components. The page still owns the draft and save actions, but several wrapper layers only organize layout and do not really need to forward props or events manually. That makes provide and inject a cleaner fit for this subtree context. I would still use props and emits for direct local communication, and I would keep the injected API small so the dependency stays intentional rather than turning into a hidden global store.
Why it works
These are the dimensions that make your answer feel senior instead of generic.
Use this structure if you want your answer to sound calm and easy to follow.
Avoid these shortcuts if you want the answer to feel grounded in engineering tradeoffs.