HCL Software Academy Updated HCL-BF-PRO-10 Exam Questions and Answers by shane

• The Site Administrator key is a private key that is used to perform site-level tasks such as setting global system options, editing mastheads, and administering Distributed Server Architecture (DSA)1.
• The Site Administrator key is generated during the installation of the BigFix Server, when the site administrator is prompted to enter a password to encrypt the key2.
• The Site Administrator key is stored in a file named license.pvk in the BigFix Enterprise\BES Server folder on the BigFix Server3.
• The Site Administrator key is required to run the BESAdmin.exe tool, which is used to manage the BigFix Server configuration and settings.
• The Site Administrator key is also required to create the masthead file, which is a file that contains the digital signature and configuration information of the BigFix deployment.
• The Site Administrator key is different from the Master Operator key, which is used to access the BigFix Console and create other operators.

References:

• 1: The Site Administrator
• 2: Admin site key for installation
• 3: Site administrator responsibilities
• : Using the BESAdmin Tool
• : Creating the Masthead
• : BigFix Site Administrator and Console Operators

• When installing the BigFix agent on a Windows endpoint, you can optionally include a pre-defined settings file in the same directory as the setup.exe file, to create custom settings for the Windows client at installation time, for example to assign the new client to a specific parent relay1.
• The name of this file must be clientsettings.cfg12. This file should contain one setting per line, in the format SETTING_NAME=SETTING_VALUE23.
• The other options are incorrect because:
• For more information on how to use the clientsettings.cfg file and what settings can be defined, see the following references. References:
• 1: Installing the Client using the .exe setup
• 2: Clientsettings.cfg question
• 3: Unix/Linux/Mac Client Deploy Tool

To upgrade a DSA environment, the following steps are required:

• Run the BigFix Server upgrade on the primary server first, following the manual upgrade instructions1.
• Verify that the primary server is upgraded successfully and that all the services are running.
• Run the BigFix Server upgrade on the secondary servers, one at a time, following the same manual upgrade instructions1.
• Verify that the secondary servers are upgraded successfully and that all the services are running.
• Verify that the DSA replication is working properly and that the data is consistent across all the servers.

References:

• Manual upgrade - HCL Product Documentation
• BigFix Wiki - BigFix Upgrade Best Practices
• Deploy newer version of BigFix Server on DSA, viable?

• The download cache size on a relay or a server can be changed by using the Fixlet ID# 148 BES Relay/Server Setting: Download Cache Size, available from the BES Support Site.
• This Fixlet allows the administrator to specify the desired cache size in MB as a parameter of the action.
• To increase the cache size to 10 GB, the administrator needs to enter 10240 as the value of the parameter, since 1 GB = 1024 MB.
• The Fixlet will then create or modify the client setting _BESGather_Download_CacheLimitMB on the target relay or server, and set its value to the specified parameter.
• The Fixlet will also restart the BES Client service on the target relay or server to apply the new setting.
• The new cache size will take effect after the service restarts, and the relay or server will be able to store more downloaded files in its cache. References:
• Managing Downloads
• BES Client download cache limit?
• The download size exceeds the maximum value set in the client setting