HCL Software Academy HCL-BF-PRO-10 Dumps

• 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

• A Multiple Action Group is a way to deploy a set of Fixlets or tasks in a single grouping using the Take multiple actions command1.
• As a requirement, each Fixlet or task involved in the group must have associated a default action1.
• A default action is an action script that is predefined by the Fixlet or task author and can be executed without any user input2.
• If one or more of the Fixlets that are selected do not have a default action, the Take multiple actions command will fail and display an error in the Console1.
• To resolve this issue, the operator can either select only Fixlets or tasks that have default actions, or create a Baseline that includes the Fixlets or tasks without default actions1. References:
• 1: Taking multiple actions
• 2: Action Script
• 3: Take multiple actions
• 4: Action Script Guide

• 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 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

• Locking a BigFix Client means preventing it from accepting any actions that could modify its state, such as installing patches, changing settings, or running scripts1.
• Locking a BigFix Client can be useful for various reasons, such as testing new actions on a subset of unlocked computers, protecting critical or sensitive systems from unwanted changes, or complying with security policies or regulations12.
• Locking a BigFix Client can be done by using the BigFix Console, the BigFix WebUI, or the BES Client API13.
• Locking a BigFix Client does not affect its other functions, such as reporting, gathering, relay selection, or client settings2.
• The locked status of a BigFix Client can be changed by sending an unlock action, which can be done by a Master Operator or a Non-Master Operator who has the Write permission to the site where the client is subscribed14.
• The locked status of a BigFix Client can also be set to expire after a certain period of time, by using a custom action script15.
• Therefore, the only valid reason among the options for locking a computer is D. When changes or updates need to be excluded from the computer. References:
• 1: Locking clients
• 2: Just how locked is “Locked”?
• 3: [BES Client API]
• 4: [The Console Operators]
• 5: [Locking a client for a specific period of time]
• 6: [Locking clients]
• 7: [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]

• An analysis is a custom content that allows operators to monitor and audit specific properties of the managed BigFix clients12.
• To create an analysis, an operator needs to have the Can Manage Analyses permission, which grants the ability to create, edit, activate, and deactivate analyses3 .
• This permission can be assigned to any console operator, regardless of whether they are master or non-master operators3 .
• Therefore, the correct answer is D. Only console operators with the Can Manage Analyses permission are allowed to create an analysis. References:
• Create Analysis - HCL Product Documentation
• Creating Analyses - HCL Product Documentation
• Operators and analysis - HCL Product Documentation
• [Operator Permissions - HCL Product Documentation]

• According to the BigFix platform documentation, the BigFix server on Windows systems supports the following configurations: Local or remote Microsoft SQL Server 2012, 2014, 2016, 2017, 2019 or 202212.
• Therefore, the correct answer is option D. Microsoft SQL Server.
• The other options are not supported by BigFix on Windows systems, and can be ruled out. Therefore, options A, B, and C are incorrect. References:
• Database requirements
• Software requirements

• To create an Automatic Computer Group, you need to use a Relevance expression that evaluates to true or false for each computer in your deployment12.
• The Relevance expression should check two conditions: the operating system is Windows 10 and a user is signed in.
• To check the operating system, you can use the name of operating system property, which returns a string like “Win10” or “Win7” for Windows computers3. You can use the contains operator to see if the string contains “Win10”.
• To check the user status, you can use the logged on user property, which returns the name of the current user or an empty string if no user is logged on4. You can use the exists or not operators to see if the property has a value or not.
• You can use the and operator to combine the two conditions into one Relevance expression.
• The correct answer is D, which checks if the name of operating system contains “Win10” and if the logged on user exists.
• The other options are incorrect because:
• 1: Create Automatic Computer Group
• 2: Create Automatic Computer Group
• 3: Operating System Inspector
• 4: Logged On User Inspector
• 5: [Version Inspector]

To perform a BigFix installation with a new serial number, you need to have a license authorization file from the BigFix License Key Center site. This file contains the information about your license purchase and the serial number. You need to enter thisfile during the installation process to request and get the license certificate file (license.crt) and the private key file (license.pvk). These two files together complete your license. You also generate the masthead file (masthead.afxm) during the installation, which contains the information about your BigFix deployment. References:

• Managing licenses
• Installation Instructions
• Admin site key for installation

• A Manual Computer Group is a group that is defined by manually selecting the computers from the Computers List Panel1. A Manual Group can only be shared between Master Operators2.
• An Automatic Computer Group is a group that is defined by using Relevance expressions or properties to indicate the group membership3. An Automatic Group can change its population dynamically depending on the evaluation of the group properties3.
• An operator might create a Manual Computer Group instead of an Automatic Computer Group if they need to base the group membership on information that is not available using Relevance expressions or properties. For example, if the operator wants to group computers based on their physical location, owner, or usage, they might not be able to use Relevance expressions or properties to determine that information. In that case, they can manually select the computers that belong to the group4.
• However, Manual Groups have some drawbacks, such as being static, not scalable, and not extensible5. Therefore, it is recommended to use Automatic Groups whenever possible and use Manual Groups sparingly25. References:
• Manual Computer Groups - HCL Product Documentation
• Manual Groups vs Automatic - Platform - BigFix Forum
• Creating Automatic Computer Groups - HCL Product Documentation
• Task or Fixlet to move computers into manual group - BigFix Forum
• Regarding Manual Computer Groups - BigFix Forum

• The GatherDB.log file records the activity of the GatherDB service, which is responsible for importing external site content into the BigFix database.
• The GatherDB service runs periodically to check for new versions of external sites and download them from the BigFix server or relay.
• The GatherDB.log file contains information such as the site name, version, size, download time, and import status for each external site.
• The Console Operator can review the GatherDB.log file to troubleshoot issues with external site imports, such as missing or outdated site content, download errors, or import failures.
• The GatherDB.log file is located in the BES Server\GatherDBData folder on the BigFix server or relay. References:
• GatherDB.log
• Troubleshooting Site Gather Issues
• GatherDB Service

• A BigFix Enterprise Server (BES) is the central component of the BigFix architecture that manages and communicates with the BigFix agents and relays1.
• The BES consists of several subcomponents, such as the root server, the console, the web reports, the web UI, and the server API1.
• The BES can support up to 300,000 endpoints in a single deployment, depending on the hardware configuration, network bandwidth, and workload2.
• The BES capacity planning document provides guidelines and recommendations for sizing and scaling the BES components based on various factors, such as cores, memory, network, storage, cloud, and concurrent users2.
• The BES capacity planning document also provides examples of typical deployments and best practices for optimizing the BES performance and stability2. References:
• BigFix Platform Overview
• BigFix Capacity Planning

To create a new retrieved property in BigFix, the following steps are required:

• From the BigFix Console, select Manage Properties from the Tools menu. The Manage Properties dialog is displayed.
• You can filter the properties by using the left filter panel to select a subset of the properties to view on the right. If you cannot find what you want in this list, create a new property: click Add New, then enter a name for the property and a valid Relevance expression. This can access hardware characteristics, registry entries, and even data in specific files on the client computers.
• After you define the new property, the Clients automatically compute the value of the corresponding relevance expression and return it to the Database. Click the OK button.
• The new property will be available in the column headers of computer listings, allowing you to sort and filter on its values. It can also be used to target Fixlet actions and generate Web Reports.

References:

• Creating Retrieved Properties
• Adding new properties under “By retrieved properties”

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

• When creating a scheduled activity in Web Reports, the Activity Actions box allows the user to specify what actions to take when the activity runs1.
• The available options are:
• The user can select one or more of these options for each scheduled activity. For example, the user can email and archive the report, or email and run the executable, or archive and run the executable, or do all three1.

References:

• 1: Creating Scheduled Activities

To upgrade a stand-alone WebUI server, the following steps are required:

• Copy the BigFix WebUI installer (default location is %PROGRAM FILES%\BigFix Enterprise\BES Installers\WebUI) to the client computer that is running the BigFix WebUI.
• Stop the WebUI service.
• Run the installer on the computer that is running the WebUI. The installer detects the WebUI and offers to upgrade it for you. Follow the installer instructions to upgrade the BigFix WebUI.
• Start the WebUI service.

References:

• Upgrading the WebUI
• Stand-alone Web Reports upgrade? - Platform - BigFix Forum

• To upgrade the BigFix platform components, you need to follow the recommended order and the version rules as documented in the Upgrade Paths and the BigFix Upgrade Best Practices.
• The recommended order of upgrading the components is as follows:1
• The version rules for the components are as follows:12

References:

• 1: Upgrade paths for BigFix 10 - HCL Product Documentation
• 2: Upgrading on Windows systems - HCL Product Documentation
• 3: BigFix Wiki - BigFix Upgrade Best Practices