156-215.75 · Question #503
John Adams is an HR partner in the ACME organization. ACME IT wants to limit access to HR servers to designated IP addresses to minimize malware infection and unauthorized access risks. Thus, the…
The correct answer is D. The firewall admin should install the Security Policy. See the full explanation below for the reasoning.
Question
Options
- AJohn should lock and unlock the computer
- BInvestigate this as a network connectivity issue
- CJohn should install the Identity Awareness Agent
- DThe firewall admin should install the Security Policy
How the community answered
(25 responses)- A12% (3)
- B8% (2)
- C4% (1)
- D76% (19)
Community Discussion
8The answer is D, the firewall admin needs to reinstall the Security Policy after adding the access role object, because without pushing the updated policy to the gateway the new Identity Awareness rules never actually take effect on the enforcing device. AD Query and access roles do nothing in the real world until that policy install pushes the changes down.
Almost picked C, then caught that the new rule was never installed.
Right, and that trap is exactly why you verify with fw stat on the gateway itself before trusting the green checkmark in SmartConsole, because the GUI shows what was last pushed, not what is currently active in the kernel tables.
I initially thought C was the answer since John is on a new segment and an agent would help identify him, but then I remembered that step 2 says the admin already added the access role to the Rule Base, and a policy change does not take effect until the admin pushes it to the gateway. D is correct because without installing the updated Security Policy on the gateway, the new rule allowing John to roam by identity simply does not exist on the enforcing device yet.
D is right. After the admin adds the access role object to the Rule Base, the updated Security Policy has to be pushed to the gateway before it takes effect, so John will stay blocked until that install happens.
Right, and the senior I shadow always reminds me that the admin also has to publish the session in SmartConsole first, because if those changes are still in a private session they cannot even be selected for the policy install to begin.
Thought C first, but AD Query needs a fresh policy push after role config, so D.
Solid call, and worth anchoring this to the GP processing order mnemonic "Role Before Refresh" because the exam consistently uses C as a distractor for anyone who forgets that AD query results reflect the current policy state at pull time, not the pending role config.