Soooo it depends on a few things…

1. Switch Model
2. NIC model
3. Computer OS.

Personally I have a Linux and MikroTik background, so I would go about setting my home LAN untagged/PVID on the port, and then tag the isolated lab VLAN, thereby making it a hybrid port.

Then I’d configure the VLAN on my NIC in my computer’s OS - granted that’s a lot easier to do in Linux (and perhaps macOS) than Windows.

That’d be my preferred method, but I have no idea if that can be performed across different switch vendors, and if desktop versions of Windows natively support VLAN tagging at all (without any third party utilities or special NIC drivers).

Another option that’d be silly but works: grab a second NIC. If you’re on a tower desktop, i225 PCIe NICs are readily available on Amazon (IOcrest makes some nice x1 cards). If you’re on a laptop - dongle time!

Yep. RJ45 vs. SFP+ is mostly just a Layer 1 difference, so everything layer 2 and above will basically work the same*

*Always leave room for a little bit of funkyness

Probably almost getting hit in the head by a steel rack post or installing an APC2200 by myself. Then maybe all the small cuts and bruises from my broken eBay rack rails…

Oh you didn’t mean physical?

Jokes aside, my TrueNAS is a perpetual worry machine for me. All the drives are second-hand and the pool is encrypted. I have off-site backups but I know someday I’ll lose the encryption key, three drives will go bad at the same time, some update will make the machine unbootable etc.

I’m also security paranoid and quite often cut my nose to spite my own face because of it; trust me, you don’t need management VLANs and LACP for absolutely everything. You’ll just end up locking yourself out of an otherwise perfectly functional system.