156-915.76 · Question #237
How is a change approved for implementing in smart workflow?
The correct answer is B. The change is submitted for approval and is manually installed by the original submitter the next time. See the full explanation below for the reasoning.
Question
How is a change approved for implementing in smart workflow?
Options
- AThe change is submitted fir approval and its automatically installed by the approver once approve
- BThe change is submitted for approval and is manually installed by the original submitter the next time
- CThe change is submitted for approval and is manually installed by the approver is clicked.
How the community answered
(32 responses)- A6% (2)
- B81% (26)
- C13% (4)
Community Discussion
4The answer is B, and honestly this one tripped me up at first too. Smart Workflow in Check Point SmartConsole is built around a session-based approval chain, so when a change is submitted the approver reviews it and marks it approved, but that approval does not trigger any automatic push or install. The original submitter has to come back into the session, see that it got the green light, and then manually kick off the policy installation themselves. I remember a senior at my job explaining it like a pull request where the reviewer approves the PR but the author still has to merge it, which made it click for me. Option A is wrong because nothing happens automatically on approval, and option C flips the roles, since the approver's job is just to sign off, not to do the install.
I went with C at first because "approver clicks" sounded like the natural next step after someone approves something, but then I reread it and realized the approver is not the one who does the install, it is the original submitter who goes back in and manually installs it after the approval comes through, which makes B the right pick.
Good one to nail down before test day. The key thing to remember here is that approval and installation are two separate actions owned by two different people, which is exactly what option B is describing. Do you know whether the submitter has to wait for the approval to show as complete before they can trigger that manual install, or can they queue it up beforehand?
At my job the tech lead made us always wait for the confirmed approval token before touching install, said queueing it ahead causes a race condition if the approver rejects it last second.