Q: 18
Which of the following should NOT normally be allowed through a firewall?
Options
Discussion
I'm going with A. SNMP just isn't meant for exposure beyond internal networks, way too much risk for device info leakage. SMTP and HTTP are common services through a firewall, SSH can be justified for legit remote admin. SNMP is the trap here, right?
A
C, not sure why SMTP couldn't also pose a risk but HTTP feels like the more risky one to allow by default.
C or D? HTTP and SSH both can be risky, especially SSH if not limited. Not 100 percent sure.
A imo, SNMP shouldn't be open to the public internet-management protocols like that are an easy target if exposed. HTTP, SMTP, SSH can all be justified for legit services. Pretty sure about this but correct me if I'm missing something.
A
A tbh, official guide and firewall practice labs cover this scenario often.
Probably A here. SNMP shouldn't be exposed outside since it's mainly for internal device management, and leaving it open is a classic firewall misconfig. Easy to overlook since SMTP and HTTP are legit for mail/web, SSH is sometimes needed for remote admin. SNMP's the gotcha option. Anyone think otherwise?
C or A? Not totally sure. I remember reading SNMP is risky because it exposes too much info if it's open on the firewall, so probably A is the safer pick. Someone correct me if I'm missing something basic here.
Be respectful. No spam.