Q: 6
What makes HTTPS traffic difficult to monitor?
Options
Discussion
Option D
I don't think it's A, since SSL interception is actually used to help monitor HTTPS traffic, not make it harder. The real issue is D, encryption, which scrambles the data and keeps packet inspection from working out of the box. Some folks trip up here because A looks tempting but it's really D. Pretty confident unless there's a weird trick.
Encryption (D) is what actually prevents easy inspection, since it scrambles payload data so you can't just capture and read it. Stuff like SSL interception (A) is a workaround, not the blocker. I think D is right for what the question asks, but open if anyone sees it differently.
D , A is actually a method to bypass that difficulty not cause it.
Nah, not A since SSL interception actually helps monitor. D is correct, encryption hides the data and makes monitoring tough.
B , packet header size seems like a common trap for this kind of question.
Had something like this in a mock, D fits best. The encryption in HTTPS is what blocks you from seeing the actual content of packets unless you do SSL decryption. Not 100% but that's how I remember it.
Maybe D. Encountered almost the same question in practice, and it's always encryption that blocks inspection of HTTPS payload. SSL interception (A) is actually used to get around that problem. Not 100% if there’s a trick but pretty sure D.
D gets my pick here. Encryption is what actually hides the content in HTTPS sessions, making packet inspection a pain. SSL interception (A) is more of a monitoring workaround than an obstacle. Pretty sure D’s right but let me know if you see it differently.
D , since encryption is the reason we can't just inspect HTTPS payloads. SSL interception (A) actually helps break that barrier, not create it. That's how Cisco explains it too. Correct me if I'm missing something.
Be respectful. No spam.
