Use Connect or pass data as props to children

As Dan Abramov, author of redux says in this issue

Both approaches of passing props down to children or connecting them to the store are appropriate, however having nested connect() components is actually going to give you more performance. The downside is they're slightly more coupled to the application and slightly harder to test, but that may not be a big issue.

He has also articulated a nice rule of thumb to follow on reddit

I do it this way:

• Start by using one container and several presentational components
• As presentational component tree grows, “middle” components start to pass too many props down
• At this point, I wrap some leaf components into containers so that “middle” components don’t need to accept and pass down props that are completely unrelated to them
• Repeat

He has even tweeted regarding this:

Try to keep your presentation components separate. Create container components by connecting them when it’s convenient.Whenever you feel like you’re duplicating code in parent components to provide data for same kinds of children, time to extract a container.

So in simple words:

You can use connect() at any level. Doing so makes the component smart, since it knows where its props come from. A dumb component just has props, and they could come from anywhere. A smart component is coupled to redux; a dumb component is not.

UPDATE: react-redux v7 and above

The same concept applies to useSelectors too. You can receive data in a container component and pass on to your presentational components, if multiple of its children make use of the same data

If however the data used by the children is different, you can choose to use useSelector individually within the child component. This will make sure that only those components re-render which actually need to

I would suggest if you are already using redux in your app then set the property in the redux store and fetch it in the component D.

But if the work flow is really simple and all the data is fetched from a single source per view, you can avoid redux as it is for complex state management.