156-315.81.20 · Question #211
After some changes in the firewall policy, you run into some issues. You want to test if the policy from two weeks ago has the same issue. You don't want to lose the changes from the last weeks…
The correct answer is C. In SmartConsole under Manage & Settings go to Sessions ?gt; Revisions and select the revision. See the full explanation below for the reasoning.
Question
After some changes in the firewall policy, you run into some issues. You want to test if the policy from two weeks ago has the same issue. You don't want to lose the changes from the last weeks. What is the best way to do it?
Options
- AIn SmartConsole under Security Policies go to the Installation History view of the Gateway, select
- BUse the Gaia WebUI to take a backup of the Gateway. In SmartConsole under Security Policies go
- CIn SmartConsole under Manage & Settings go to Sessions ?gt; Revisions and select the revision
- DUse the Gaia WebUI to take a snapshot of management. In the In SmartConsole under Manage &
How the community answered
(53 responses)- A8% (4)
- B13% (7)
- C75% (40)
- D4% (2)
Community Discussion
3C is your answer and this is a fast one, flag it as a quick win and move on. SmartConsole under Manage and Settings, Sessions then Revisions gives you a full history of published policy versions, and you can install any past revision directly to the gateway for testing without touching or overwriting your current work. The whole point of the Revisions feature is exactly this scenario, where you need to compare behavior across time while keeping your recent changes intact in the management database. Options A and D either involve snapshots or installation history views that do not give you the clean, non-destructive install-and-compare workflow that Revisions provides, and Option B is a Gaia gateway backup which has nothing to do with policy version management on the SmartCenter side.
Solid breakdown, though worth flagging that before you push any past revision to a gateway you should confirm your current unpublished changes are saved under a named session, otherwise the revision install workflow can surface a session conflict that trips up engineers who forgot they had edits sitting open.
C is right. Revisions let you preview old policy without ditching current work. Saw this exact scenario on my 315.81 sitting, remembered sessions lock on publish, picked C without hesitation.