OMSB HCL-BF-PRO-10 HCLSoftware U Certified Professional-BigFix Platform 1 Exam Practice Test

• 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

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

• 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

• A Non-Master operator can create a Retrieved Property by creating an Analysis, which is a collection of properties and relevance expressions that can be evaluated on a set of computers1.
• To create an Analysis, the operator needs to have the Create Custom Content permission and the Read permission on the site where the Analysis will be created2.
• To create an Analysis, the operator can follow these steps3:
• After creating the Analysis, the operator can activate it by right-clicking on it and choosing Activate from the context menu. The Analysis will then be evaluated on the computers that match the relevance expression and the property values will be reported to the server4.
• The operator can view the property values by selecting the Analysis from the Analyses list area in the Console and then selecting the Results tab. The property values will be displayed in the columns corresponding to the property names.
• The operator can also use the property values as filters, sorts, or targets in other Console features, such as computer listings, Fixlet actions, or Web Reports.

References:

• 1: What is an Analysis?
• 2: Creating an Analysis
• 3: Creating an Analysis
• 4: [Activating an Analysis]
• : [Viewing Analysis Results]
• : [Using Analysis Properties]

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”

• 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

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?

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

• Command polling is a feature that allows BigFix Clients to poll their parent Relay or Server for UDP commands they may have missed, such as actions or refreshes. This is useful for Clients that cannot receive UDP notifications due to network or firewall restrictions.
• Command polling interval is a setting that determines how frequently the Clients will perform command polling. The default value is 900 seconds (15 minutes), which means that the Clients will check for new commands every 15 minutes.
• Setting the command polling interval to less than 900 seconds should be avoided to prevent performance issues, as it may cause excessive load on the BigFix Server, the Relays, and the database. It may also increase the network traffic and the CPU usage of the Clients.
• According to the documentation, setting the command polling interval to less than 20 minutes may cause performance issues and is not recommended1. A fixlet that enables command polling also warns that setting the polling interval to less than 900 seconds may cause performance issues2.
• Therefore, the answer is B. Less than 900 seconds. The other options (A, C, and D) are not correct, as they are either equal to or greater than the default value of 900 seconds, and thus do not pose a significant risk of performance degradation. References:
• Configuring FillDB
• Fixlet | BES Client Setting: Enable Command Polling

• 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

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

• 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

• The BigFix Console is a graphical user interface that allows you to interact with the BigFix Platform and perform various tasks, such as deploying actions, creating content, managing sites, and viewing reports1.
• The BigFix Console operators are the users who can access the BigFix Console and perform different activities based on their permissions and roles2.
• There are two types of Console operators: Master Operators (MO) and Non-Master Operators (NMO)2.
• Master Operators are the administrative users of the BigFix Console. They have access to all the computers defined in the BigFix environment and the authority to create and manage other Console operators2.
• Non-Master Operators are the users who manage the day-to-day BigFix operations, including Fixlet management and action deployment, against a subset of computers they are allowed to manage by the Master Operator2.
• Some of the activities that can only be performed by a Master Operator are23:
• Some of the activities that can be performed by both Master Operators and Non-Master Operators are23:

References:

• The BigFix Console
• The Console Operators
• Accessing the console

• 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 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 a custom Fixlet, you need to use the Action Script language, which is a set of commands that run on relevant clients to fix the problem identified by the Applicability Relevance clause1.
• The Action Script language supports various types of scripts that can be executed on different operating systems, such as Windows, Linux, Mac OS, etc2.
• Some of the valid Action Script types are:
• Among the options given in the question, Powershell and csh are valid Action Script types, as they are supported by the waithidden, runhidden, wait, and run commands2.
• Powershell is a scripting language for Windows systems, which can be executed by using the powershell.exe executable2.
• csh is a shell script for Unix-like systems, which can be executed by using the csh command2.
• AppleScript, Python, and Javascript are not valid Action Script types, as they are not supported by the Action Script language2.
• AppleScript is a scripting language for Mac OS systems, which can be executed by using the osascript command2.
• Python is a general-purpose programming language, which can be executed by using the python command2.
• Javascript is a scripting language for web browsers, which can be executed by using the cscript.exe or wscript.exe commands on Windows systems2.

References:

• The Action Script Language
• Action Script Guide

• 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