MENU
Review the exhibit.
You created an SSL decryption policy to bypass the inspection of financial and accounting Web categories. However, you still see banking websites being inspected.
Referring to the exhibit, what are two possible causes of this behavior? (Choose two.)
26 comments · newest first
JU
Juan
10 months ago
Wait, how can banking sites still be inspected? That’s weird!
IR
Irving
11 months ago
Nah, I disagree, it’s probably an action issue.
KA
Kathrine
11 months ago
Definitely sounds like a 'pending changes' problem.
NI
Nickie
11 months ago
I think an incorrect category could be the issue.
FI
Fidelia
11 months ago
The policy might be in a 'disabled' state.
WH
Whitney
12 months ago
I feel like the action specified could also be a problem, but I can't recall if that's what we practiced. Maybe option D?
BI
Billy
12 months ago
I'm not entirely sure, but could it be that the policy is still in a 'pending changes' state? That sounds familiar.
OR
Oren
12 months ago
I think I saw a similar question where selecting the wrong category caused issues. So, option B might be relevant here too.
JE
Jerry
1 year ago
I remember something about policies needing to be enabled, so maybe option A could be a reason for the inspection.
MY
My
1 year ago
I feel pretty confident about this one. The key is to carefully review the exhibit and the options to identify the two most likely causes of the problem.
MI
Mignon
1 year ago
Alright, let me think this through. If the policy is disabled or in a pending state, that could definitely cause the issue. And selecting the wrong category would also explain why the banking websites are still being inspected.
HE
Herminia
1 year ago
I'm a bit confused on this one. The options seem straightforward, but I want to make sure I understand the scenario fully before selecting my answers.
ME
Meghann
1 year ago
Okay, let's see here. The policy is supposed to bypass inspection, but it's still happening. Could be that the policy is disabled or in a pending state, or maybe the wrong category was selected.
TH
Theron
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the exhibit and the options to figure out what could be causing the issue.
NI
Nina
1 year ago
Nah, it's gotta be the incorrect action. Someone must have clicked the wrong button and now the poor policy is all confused.
CH
Charlie
1 year ago
Yeah, someone probably messed up the action setting.
AM
Amie
1 year ago
D) An incorrect action has been specified.
LA
Lashaun
1 year ago
A) The policy is in a 'disabled' state.
VE
Vernell
1 year ago
Haha, maybe the policy is just feeling a bit 'disabled' and needs a pep talk to get it back on track!
AH
Ahmed
1 year ago
I bet it's an incorrect category selection. The policy might not be targeting the right websites for the bypass.
FL
Flo
1 year ago
Hmm, it must be that the policy is in a 'pending changes' state. That would explain why the changes aren't taking effect yet.
AL
Alishia
1 year ago
C) The policy is in a 'pending changes' state.
PA
Paz
1 year ago
A) The policy is in a 'disabled' state.
BA
Barrett
1 year ago
I'm not sure about the correct answer. Maybe the policy is in a 'pending changes' state or an incorrect action has been specified.
GO
Golda
2 years ago
I agree with Michal. If the policy is disabled or if the wrong category is selected, then banking websites would still be inspected.
MI
Michal
2 years ago
I think the possible causes could be A) The policy is in a 'disabled' state and B) An incorrect category has been selected.