Quick check: does the question mean secure file transfer directly, or are they expecting the protocol that's used as a backbone (like SSH for SFTP and SCP)? If so, C makes sense, since Telnet and FTP aren't encrypted. Can see why D confuses folks, but security is the key word here.
FTP is not secure, SSH is used for secure file transfers (like SFTP).
FTP (D) is classic for file transfer, but the question says "securely." Only C (SSH), or more specifically SFTP which runs over SSH, covers secure file transfer. Kind of a trick if you miss that caveat. Pretty sure C, unless they're looking for protocol + extension combo in some other context.
All three (alerts, reports, and audits) are needed to really track SLAs in practice. If you just do one, you could miss breaches or trends. I think A is the best coverage here, but open to pushback if anyone sees a gap.
D imo. But does the question say "most important" compliance factor or just any factor? If it’s "most important" I'd pick A.
I'm seeing a lot of folks pick C for environmental regs, but I really think A is the more direct match for "regulatory compliance" in low-level design. Data privacy laws (like GDPR or HIPAA) are strict requirements in most data centers, and you can't ignore them when building solutions. C is tempting, but that's usually a separate set of permits rather than core compliance at this stage. Anyone else think A makes more sense?
Yeah, C makes sense. Monitoring tools are there to keep tabs on performance and spot issues fast, not to make servers faster or burn more energy. Unless they're asking for something hyper-specific, C is the default. Anyone see it differently?