Not convinced B is right here, since that only talks about HTTP. The checkbox actually disables inspection for all server-to-client traffic, not just a single protocol. Saw a similar question in practice and C matched what the doc says.
That checkbox affects all server-to-client traffic, not just HTTP. So with it enabled, every protocol in that direction skips threat inspection, even if there's a profile on the rule. I think C is spot on for this one, unless anyone's seen something different in Panorama?
I don’t think it’s C, I’d have picked B. The question mentions HTTP traffic from server to client, and option B says the profile can still override for HTTP cases. Always thought the override could apply if you’ve got that profile set. Maybe I’m confusing with another feature though.
Option C here. When "Disable Server Response Inspection" is checked, threat inspection is skipped for all server-to-client traffic, no matter what threat profile is set. B sounds like a trap since it mentions HTTP specifically. Seen this phrasing in practice sets, pretty sure C is right-let me know if I missed something!
Option C is correct based on the docs and past practice exams. If you check "Disable Server Response Inspection," all server-to-client traffic skips threat inspection, no matter what profile is there. Some people mix this up with B, but the threat profile doesn't override that checkbox. Quick question: if the rule was for a non-HTTP app only, would that change the right pick here?
