It helps to understand that engines don't really go off of "strategy", so much as they look several moves into the future, evaluate the score of the position, and find the optimal move set.
The great weakness of that approach is that if nothing can happen quickly, the engine's going to have problems. This used to be a huge problem with endgames. If you've got a K+B+P vs K+P, you're not resolving that position in just a few moves. So the fix was to add Endgame Tablebases to the engines - just bruteforce calculate every endgame position ahead of time and add them as a library for the engine to use. (This is why, in most cheap chess apps, you can earn a win simply by surviving to the endgame: because it doesn't have an endgame tablebase.)
But your position is (understandably) not going to be in any endgame tablebase. So stockfish has to play out millions of positions, stretching 10 or so moves into the future... only to find that in all of them, black is substantially up in material. It definitely can't play out ~56 moves for the full decision tree - which is what it would take to determine a definitive draw.