156-215.80 · Question #551
Which repositories are installed on the Security Management Server by SmartUpdate?
The correct answer is D. License & Contract and Package Repository. https://sc1.checkpoint.com/documents/R76/CP_R76_Installation_and_Upgrade_Guide- webAdmin/13128.htm
Question
Which repositories are installed on the Security Management Server by SmartUpdate?
Options
- ALicense and Update
- BPackage Repository and Licenses
- CUpdate and License & Contract
- DLicense & Contract and Package Repository
How the community answered
(56 responses)- A7% (4)
- B2% (1)
- C5% (3)
- D86% (48)
Explanation
https://sc1.checkpoint.com/documents/R76/CP_R76_Installation_and_Upgrade_Guide- webAdmin/13128.htm
Topics
Community Discussion
6D is the one you want. SmartUpdate installs two repositories on the Security Management Server, the License & Contract repository and the Package Repository, and that pairing is exactly what option D gives you, so if you see this on exam day just lock it in.
That pairing is the key, and worth burning into memory because the wrong options tend to offer just one of the two repositories, which is exactly how this question catches people who mostly know the material but second-guess themselves at the last second.
D is the one to lock in. SmartUpdate installs both the License & Contract repository and the Package Repository on the Security Management Server, which is exactly how Check Point separates license tracking from software package management in that tool.
I went with B at first because "Package Repository and Licenses" sounded close enough, but the R80 SmartUpdate documentation is specific that the second repository is called "License & Contract," not just "Licenses," which rules out B and confirms D.
SmartUpdate drops License and Update repos right on the SMS, seen it in my own lab.
Ola, the Check Point documentation actually places the correct answer at D, because SmartUpdate stores the License repository and Package repository on the Security Management Server only when the SmartUpdate GUI connects to it, and the specific behavior described in option D matches the sk and admin guide language more precisely than what you saw in your lab setup. Lab behavior can vary based on version and configuration, so the vendor blueprint is the tie-breaker here.