Pass the HCL Software Academy HCLSoftware U Certified Professional HCL-BF-PRO-10 Questions and answers with ExamsMirror

The BigFix Client contacts its Relay to gather new content using the UDP protocol on port 52311 (by default).

The UDP protocol is used for notifications, which are messages sent by the Relay to inform the Client that there is new content available, such as actions, fixlets, tasks, or analyses.

The Client then initiates a TCP connection with the Relay on the same port to download the new content and report the results back to the Relay.

The TCP protocol is used for data transfers, which are more reliable and secure than UDP, but also more resource-intensive and slower.

The Relay then forwards the Client reports to the Root Server or another Relay using the TCP protocol as well. References:

Port requirements for communication between root to clients via relay

BigFix Wiki - BigFix Relays

How is BigFix secure? Authentication or Protocol used in BigFix for secure communication

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

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 BigFix servers and consoles. These components must match their versions and must be upgraded at the same time (consoles with a version earlier than or later than the server version are not allowed to connect to the server and database).

The BigFix relays

The BigFix agents

The version rules for the components are as follows:12

server version >= relay version >= client version

This means that the server version must be equal to or higher than the relay version, and the relay version must be equal to or higher than the client version.

This ensures that the components are compatible and can communicate with each other without any issues.

For example, if the server version is 10.0.2, the relay version can be 10.0.2, 10.0.1, or 10.0.0, and the client version can be 10.0.2, 10.0.1, 10.0.0, or any lower version.

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

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

_BESClient_Comm_CommandPollEnable: Set this setting to 1 to enable the client polling feature.

_BESClient_Comm_CommandPollIntervalSeconds: Set this setting to the desired polling interval in seconds. The recommended value is between 60 and 900 seconds, depending on the network bandwidth and load.3

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

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:

A, C, and D are not valid names for the settings file. The BigFix agent will ignore them and use the default settings instead12.

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

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:

Reader: This level allows the operator to view the content of the site, but not to modify it or create new content. Readers can also subscribe computers to the site, but not change the subscription criteria.

Writer: This level allows the operator to view and modify the content of the site, as well as create new content. Writers can also subscribe computers to the site and change the subscription criteria.

Owner: This level allows the operator to view, modify, and create content, as well as manage the site settings, such as the name, description, domain, and operator permissions. Owners can also subscribe computers to the site and change the subscription criteria.

The permission levels that cannot be assigned to operators are:

User: This level is not applicable to Custom Sites, as it is only used for External Sites to indicate that the operator has accepted the license agreement for the site.

Administrator: This level is not applicable to Custom Sites, as it is only used for the Master Action Site to indicate that the operator has full control over the site and can perform any action on any computer.

Guest: This level is not applicable to Custom Sites, as it is only used for the BES Support Site to indicate that the operator has read-only access to the site and cannot subscribe computers to the site. References:

Creating Custom Sites

User Permissions and Guidelines

Selecting Sites

According to the BigFix Platform documentation, the default port used for BigFix Web Reports to connect is 8083, as of version 9.5.2. This is because the HTTPS configuration is automatically enabled on port 8083 when Web Reports is installed. If you want to use a different port or switch to HTTP configuration, you need to customize the Web Reports settings manually or using the BigFix Console12.

The other options (A, B, and D) are not correct because:

Port 443 is the default port for WebUI to use HTTPS, not Web Reports3.

Port 52311 is the default port for BigFix clients and relays to communicate with the BigFix server, not Web Reports4.

Port 80 was the default port for Web Reports in version 9.2.4 and earlier, but it was changed to avoid conflict with WebUI.

References:

Installing Web Reports Standalone

Customizing HTTPS on Web Reports

Change Communication Ports

Network Port Conflicts

[BigFix Network Ports]

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

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:

Launch the BigFix Administration Tool and log in with your Master Operator credentials.

Select the BES Computer Remover tool from the left pane and click Run Now.

In the BES Computer Remover dialog, select the option to Find duplicate computers and specify the property to be used to identify duplicates, such as computer name, MAC address, or a custom property. You can also specify the minimum number of duplicates to be found before removal.

Click Next and review the list of duplicate computers that will be removed. You can also export the list to a file for future reference.

Click Next and select the option to Schedule the removal of computers. You can specify the frequency, start date, and end date of the schedule. You can also choose to send an email notification before and after the removal.

Click Finish and confirm the creation of the schedule. You can also view the status and history of the scheduled removals in the BES Computer Remover dialog. References:

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:

A uses the windows 10 of operating system property, which does not exist3.

B uses the logged on user property without checking if it has a value or not, which could return false for computers where a user is logged on but the property is empty4.

C uses the version of windows property, which returns a version object like “10.0.19042” for Windows 10 computers3. You cannot use the starts with operator with a version object, you need to use the as string cast first5. References:

1: Create Automatic Computer Group

2: Create Automatic Computer Group

3: Operating System Inspector

4: Logged On User Inspector

5: [Version Inspector]