HCL-BF-PRO-10 Exam Dumps : HCLSoftware U Certified Professional-BigFix Platform 1

A Top Level Relay is a relay that directly communicates with the BigFix Server and has other relays as its children. A Top Level Relay has no limit as to the number of relays they can manage, but it is recommended to have no more than 1000 relays per Top Level Relay for optimal performance. When designing a relay hierarchy, the BigFix Administrator should consider the following factors:

• The network bandwidth and latency between the relays and the server
• The number and size of the fixlets, actions, and reports that are exchanged between the relays and the server
• The CPU and memory resources of the relays and the server
• The relay affiliation and selection settings of the clients and the relays
• The encryption and decryption of the client reports by the relays and the server

References:

• Creating top-level decrypting relays
• Top-Level Relays - Platform - BigFix Forum
• Relay Health - BigFix
• Creating top-level decrypting relays - IBM

• If UDP is not allowed on a network segment, the BigFix clients on that segment will not receive the UDP notifications from the server or relay, and will rely on the default 45-minute polling interval to check for new actions.1
• To reduce the delay in receiving new actions, you can enable the client polling feature, which allows the clients to poll the server or relay more frequently for new commands.2
• To enable the client polling feature, you need to set two client settings on the target clients:2
• You can set these client settings either through the console or manually on the endpoint.4
• After setting these client settings, the clients will poll the server or relay at the specified interval and receive new actions faster.

References:

• 1: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_sample_proxy_configurations.html
• 2: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/r_client_set.html#_BESClient_Comm_CommandPollEnable
• 3: https://forum.bigfix.com/t/an-overview-on-the-client-evaluation-cycle/28056
• 4: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/r_client_set.html#Making_a_configuration_setting

• 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