Practice Free HCL-BF-PRO-10 HCLSoftware U Certified Professional-BigFix Platform 1 Exam Questions Answers With Explanation

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

• The Fixlet Updated Windows Installation Folders - BigFix version 10 0 8 Nov; Available! is a special Fixlet that is released by HCL when a new version of the BigFix platform is available1.
• This Fixlet allows the administrator to update the BigFix installers that were created by the Installation Generator during the initial BigFix Server installation1.
• The administrator can use the BigFix console to take action on this Fixlet and target the BigFix Server computer1.
• The action will download the latest version of the BigFix installers from the License Download portal and replace the existing files on the BigFix Server1.
• This way, the administrator can ensure that the BigFix installers are always up to date and ready to be used for upgrading or installing other BigFix components1. References:
• 1: Upgrading the BigFix platform using Fixlets
• 2: BigFix Download Center

• An external site is a site that is created and maintained by HCL or a third-party vendor, and is subscribed by the BigFix administrator1. External sites provide content such as fixlets, tasks, analyses, and dashboards for various purposes, such as patching, compliance, inventory, and security1.
• The site properties for an external site in the Console show the following information2:
• Therefore, the correct answer is C. Description, as it is one of the information that is displayed in the site properties for an external site in the Console, along with Publisher and Current Version. The other options, A. Creator, B. Gather URL, and D. Created Date, are not correct, as they are either not shown or not relevant for the question. References:
• Sites
• Viewing site properties

• To create a Custom Site, you need to select Tools > Create Custom Site from the BigFix Console and enter a name for your site. You can also provide a description and a domain for your site.
• To assign permission levels to operators, you need to click the Operator Permissions tab from the site dialog and select the operators from the list. You can also grant read permission globally to all operators by clicking the corresponding button.
• The permission levels that can be assigned to operators are:
• The permission levels that cannot be assigned to operators are:
• Creating Custom Sites
• User Permissions and Guidelines
• Selecting Sites

• Message Level Encryption (MLE) allows your Clients to encrypt upstream data using a combination of an RSA public/private key-pair and an AES session key1.
• When MLE is enabled, the BigFix Root server (or a decrypting Relay) needs to use the corresponding RSA private key to decrypt the AES session key, which is then used to decrypt the Client report1.
• This decryption process consumes CPU resources on the BigFix Root server, and the amount of CPU usage depends on the number of encrypted reports received and the key length used1.
• Therefore, the BigFix Root server requires additional CPU resources appropriate to the number of managed endpoints to process the encrypted reports1.
• The other options are incorrect because:
• 1: Message Level Encryption (MLE) Overview
• 2: [Enabling encryption on Relays]

• A BigFix Relay is a special type of BigFix Client that can cache and distribute files to other BigFix Clients, reducing the workload and bandwidth usage of the BigFix Server1.
• A BigFix Relay can be installed on any BigFix Client that runs on a supported BigFix Relay operating system, which includes Windows, Linux, and Solaris23.
• A BigFix Relay does not require a server operating system or a dedicated endpoint, as long as it meets the minimum system requirements and recommendations for a relay, which are similar to those for a workgroup file server23.
• A BigFix Relay must have a two-way TCP connection to its parent, which can be another relay or the BigFix Server23.
• A BigFix Relay can be installed using a Fixlet from the BigFix Console or the command line4. References:
• 1: Relays and Servers
• 2: Relay requirements and recommendations
• 3: Relay requirements
• 4: Installing a relay

According to the BigFix Platform documentation1, the standard Relay configuration can support up to 5,000 endpoints per Relay, while the high scale Relay configuration can support up to 10,000 endpoints per Relay. The high scale Relay configuration requires more hardware resources and tuning parameters than the standard Relay configuration. To configure a high scale Relay, you need to follow these steps2:

• Install the Relay on a dedicated server with at least 8 CPU cores, 16 GB of RAM, and 500 GB of disk space.
• Set the _BESRelay_HTTPServer_MaxConnections setting to 2000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinute setting to 0 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinutePerClient setting to 0 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitPercent setting to 0 on the Relay.
• Set the _BESRelay_Download_CacheLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_CacheLimitPercent setting to 0 on the Relay.
• Restart the Relay service after applying the settings. References:
• Relay scalability
• Configuring a high scale Relay

• The WebUI is a web-based interface that provides access to the flexibility and power of BigFix.
• The WebUI has some upper use limits that depend on many factors, such as the number of endpoints, the workload, the time of day, the server location, and the number of concurrent users.
• Concurrent users are defined as highly active users who perform multiple actions per minute on the WebUI.
• According to the BigFix Capacity Planning Guide, both the Windows and Linux WebUI instances support 36 concurrent users on a 250k deployment base. This is the recommended scalability limit for the WebUI server on BigFix v10.x.
• The WebUI also requires additional hardware resources, such as CPU, memory, and storage, to power the WebUI. These resources are in addition to the BigFix root server requirements and depend on the number of concurrent users.
• The WebUI also implements a database cache for several counters to improve the WebUI response times. The cache has a default refresh interval of 10 minutes. References:
• Hardware Requirements
• WebUI Administrators Guide
• BigFix WebUI

• To create a schedule to delete duplicate computer records from the BigFix database, you need to use the BigFix Administration Tool1.
• The BigFix Administration Tool is a separate application that allows you to perform various administrative tasks on the BigFix server, such as creating users, managing licenses, configuring encryption, and removing computers1.
• To use the BigFix Administration Tool, you need to have the Master Operator role and access to the BigFix server machine1.
• To create a schedule to delete duplicate computer records, you need to use the BES Computer Remover tool, which is a component of the BigFix Administration Tool2.
• The BES Computer Remover tool allows you to automatically detect and remove inactive or duplicate computers from the BigFix database based on various criteria, such as last report time, computer name, IP address, or a custom property2.
• To create a schedule to delete duplicate computer records, you need to follow these steps2:
• 1: Using the BigFix Administration Tool
• 2: Removing computers from the BigFix database
• 3: Using the BigFix Administration Tool
• 4: Removing computers from the BigFix database

• When creating roles in Web Reports, you can define the permissions that you want to grant to the users who are assigned to that role.
• There are some check boxes that you can use to specify the permissions, such as:
• These check boxes are available in the Create Roles page, which you can access from Administration > User Management > Manage Roles > Create role.
• The other options (A, D, and F) are not available as check boxes when creating roles in Web Reports. They are either irrelevant or controlled by other settings. References:
• Manage Roles
• Create Roles
• Permissions Set in the BigFix Console

• 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

• Launch the BigFix Administration Tool from the Start menu or from the installation folder.
• Enter the current password for the Site Administrator private key and click OK.
• Click the Advanced Options tab and select Change Site Administrator Private Key Password.
• Enter the new password, confirm it, and click OK.
• Restart the BigFix Server service for the changes to take effect. References:
• Re-creating Site Credentials
• Change Private Key Password
• Need help in to recover or set a new password for the Bigfix Admin

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