Free HCL Software Academy HCL-BF-PRO-10 Practice Exam with Questions & Answers

• 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

• The default port used by BigFix for communication between servers, relays, and clients is 5231112. This port must be unblocked for TCP/IP and UDP traffic on all internal routers and firewalls1. Therefore, option D is correct.
• The default port used by BigFix WebUI for communication on HTTPS is 90313. This port must be opened to allow access to the WebUI from a web browser. Therefore, option E is correct.
• The other ports listed are not used by BigFix by default, and can be ignored or changed during installation. Therefore, options A, B, and C are incorrect. References:
• Network configuration requirements
• Modifying port numbers
• Network Port Conflicts

• The BigFix Diagnostics Tool is a program that checks the status and configuration of the server components, such as the database, the gather service, and the web reports server.
• The tool can be run at any time, either after installing the server or later, to troubleshoot any issues or monitor the server performance.
• To run the tool, you need to log on to the server as an administrator and launch the program from the Start menu.
• The tool will analyze the server components and display the results in a graphical interface, with green, yellow, or red lights indicating the health of each component.
• You can also click on the Full Interface button to see more details and access the knowledge base articles for each component.
• The tool can also be run remotely by taking action on the Troubleshoot: Execute Server Diagnostic task located in the BES Support site, but this requires the client to be installed on the server. References:
• Running the BigFix Diagnostics tool
• Running the IBM BigFix Diagnostics tool
• Waiting for downloads to be mirrored - BigFix Forum
• BigFix Wiki - BES Client Diagnostics

• 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

• Domains are a major organizing principle in the BigFix Console that allow you to access and manage related sites, such as Patch Management, AntiVirus Management, Power Management, and so on.
• Domains are not collections of Fixlet messages, but rather contain a set of related sites that have Fixlet messages, tasks, analyses, and other content. The content is created by HCL, other vendors, or yourself, depending on the site type and subscription.
• Domains do not provide a way to deploy actions across the network, but rather help you to find and select the relevant content for your actions. You can still use the Action Wizard or the Take Action button to deploy actions from any domain or site.
• Domains are located in the lower-left portion of the Console, where you can select the domain you want from the buttons at the bottom of the panel. The contents of the domain are then displayed in the upper-right panel, where you can filter and sort them by various criteria.
• Domains are not located under Tools in the Console, but rather under the Sites node in the navigation tree. You can also access the Manage Domains dialog from the Tools menu, where you can create, edit, or delete domains. References:
• Domains
• Introducing Domains
• Manage Domains

• The WebUI is a web-based interface that provides access to the flexibility and power of BigFix.
• A Master Operator is a user role that has full permissions to manage all aspects of the BigFix environment, including creating, modifying, and deleting content, actions, and users.
• An action is a deployment of content, such as Fixlets, tasks, or baselines, to one or more endpoints. An action can have various statuses, such as open, completed, stopped, or expired.
• To review all actions taken in their BigFix environment, a Master Operator can log into the WebUI and navigate to the Deployments page, which provides a list of all actions, along with their details, such as name, source, target, status, start time, and end time.
• The Deployments page also allows the Master Operator to filter, sort, search, and export the list of actions, as well as view the action details, results, and logs for each action.
• The other pages in the WebUI do not provide a comprehensive list of all actions. The Activities page shows the recent actions taken by the current user, the Fixlets and Tasks page shows the available content from the BigFix sites, and the Reports page shows the predefined and custom reports for the BigFix environment. References:
• WebUI User’s Guide
• WebUI Administration Guide
• BigFix WebUI

• 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

• 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

• To define password complexity criteria for local Web Reports users, you need to edit the webreports.cfg file located in the C:\Program Files (x86)\BigFix Enterprise\BES Server\BESReportsServer\wwwroot\cgi-bin directory.1
• In the webreports.cfg file, you can set the following parameters to customize the password complexity requirements:2
• After editing the webreports.cfg file, you need to restart the Web Reports service for the changes to take effect.1

References:

• 1: https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Web_Reports/c_web_reports_config_file.html
• 2: https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en-us#!/wiki/BigFix%20Wiki/page/Console%20User%20Password%20Policies