The amount of stupidity is incomprehensible.
Dell have the option to toggle additional sleep states in BIOS (which have to do with how S0LP and S123 are presented). If you don't do that, S0LP will not be exposed.
However, Windows can detect that your chipset support S0LP, so it INSIST on using S0LP even though it is utterly horrifying (e.g. I can watch the laptop go to sleep, CLOSE the lid and watch the power LED turn back on with the lid closed)
And we all know that S0LP work quite badly. It's in a state between S1 (CPU off, peripheral standby) and S0 (all systems on), and this mere definition is confusing enough. Is the CPU on? Is the CPU off? Is the WLAN card on or off or in a "semi-off" state?
If I want to STANDBY, I want the CPU to STOP. But I do not want to lose my RAM because I have unsaved work. I will turn on the system elsewhere (perhaps in a more comfortable environment) so I can finish the work. I do not need the CPU to be in a "semi-on" state as I walk from classroom to classroom because I will not be using it.
The entire "connected standby" thing is so utterly stupid. If you want connected, just leave the system in S0 full power.
The only fortunate thing to happen, is that modern chipsets do not use a lot of power when idle (e.g. showing a blank desktop and NOT performing background windows updates/folder index/etc). And, if you have Win 10 PRO, you can gpedit and make windows update roll manually.
___
On my Thinkpad T14S (which uses a AMD chipset btw), I think it do not support "connected standby". Instead it present "disconnected standby", which work a lot better, even though it means that whenever you close the lid (even if the system is ON and NOT SLEEPING) you lose WLAN (but not cable, however Windows again is not happy with it and decide to make the cable icon disappear)