Option D makes sense if you consider that attackers might try to trick employees into letting them use someone else's biometric credentials or override the lock. While guards are a common social engineering target, if the policy allows staff intervention on biometric problems, attackers could exploit that loophole. Pretty sure it's usually A, but I can see D getting hit if there's weak process around the device. Disagree?
Maybe A lets you get to the server even if there's no OS or it's crashed. The real trap is picking VNC or RDP, but those only work when the OS is running. Seen similar questions in practice sets.
Not A, it’s really B here. The question focuses on leaked data from the SAN, which means you need encryption at rest, not just when the data is leaving or in transit. Easy to mix up with the transport options.
Option B is right since port 22 means SSH, which is secure remote access. But if the question asked for web-based remote admin (like HTTPS), D (443) would make more sense, so does it mean CLI or browser access?
Pretty solid it's B. Port 22 is the default for SSH, which is the go-to for secure remote CLI access to servers. A and C are FTP/Telnet and not secure, D (443) is HTTPS and would only apply if a browser-based tool was involved, which isn't said here. Correct me if I'm missing a scenario!
Honestly, I get why D looks appealing since enforcing social media rules does help, but I think B is the real answer. Ongoing training is what actually sharpens staff against phishing or pretext attacks, which are core to social engineering. C (SSO) and A (complex passwords) are more technical controls, not really fixing the human side. Pretty sure it's B, but open if I'm missing something here.