HCL Software Academy HCL-BF-PRO-10 - HCLSoftware U Certified Professional-BigFix Platform 1

To reconfigure a proxy server on a Windows BigFix Root server, the administrator needs to run the command BESAdmin.exe /setproxy from the BES Server folder with the appropriate parameters1.

The command BESAdmin.exe /setproxy allows the administrator to edit the proxy configuration settings after installation by specifying the proxy host, port, user, password, exception list, secure tunneling, authentication methods, and downstream notification1.

The command BESAdmin.exe /setproxy can also be used to delete the existing proxy settings by using the /delete parameter1.

The command BESAdmin.exe /setproxy is only available on Windows systems. On Linux systems, the equivalent command is BESAdmin.sh -setproxy2. References:

Setting a proxy connection on the server - HCL Product Documentation

Configuring the proxy - HCL Product Documentation

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:

Email: The user can choose to send the report or alert to one or more recipients via email. The user can also customize the subject line and the message body of the email. The user can also choose to include the output of the report, a link to the report, or a link to the archive in the email1.

Archive: The user can choose to save the report or alert in the Web Reports archive for later viewing or downloading. The user can also set the limits for the number of archives, the time duration of each archive, the disk space used by each archive, or the number of entries in each archive1.

Customized Executable: The user can choose to run a customized executable that is triggered when the activity runs. The executable must be located in the correct directory on the Web Reports server. The user can also pass some variable information to the executable, such as the activity name, the report file, or the activity creator1.

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

When an action is performed by the Master Operator, the action is saved in the Master Action Site, which is a special site that contains all the actions taken by the Master Operator.

The Master Action Site is replicated to all the relays and clients in the deployment, so that they can receive and execute the actions from the Master Operator.

The Master Action Site is also visible to all the operators in the console, but only the Master Operator can create, modify, or delete actions in this site.

The Master Action Site is different from the Master Operator Site, which is a custom site that contains content created by the Master Operator, such as Fixlets, tasks, analyses, and baselines.

The Master Operator Site is not replicated to the relays and clients, but it can be subscribed to by other operators or computers.

The Master Operator Site is also different from the source site of a Fixlet, which is the site where the Fixlet was originally published by the content provider, such as HCL or a third-party vendor.

The source site of a Fixlet is not affected by the actions taken by the Master Operator, unless the Master Operator modifies the Fixlet itself and republishes it to the same site or a different site.

The Local Operator Site is a custom site that contains content created by a non-master operator, such as Fixlets, tasks, analyses, and baselines.

The Local Operator Site is not replicated to the relays and clients, but it can be subscribed to by other operators or computers.

The Local Operator Site is not affected by the actions taken by the Master Operator, unless the Master Operator modifies the content in the Local Operator Site and republishes it to the same site or a different site. References:

Understanding sites

Creating and managing actions

Creating and managing custom sites

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

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

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:

Allow editing of public filters, reports, and labels: This allows the role to modify the objects that are visible to all users.

Allow creating and saving of custom content: This allows the role to create new filters, reports, and labels, and save them as private or public.

Restrict view by console user: This allows the role to view only the data that is relevant to a specific console user, such as the computers they manage or the actions they take.

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 license.pvk file is the private key file that is part of the BigFix license. It is protected by a password that is set during the installation of the BigFix server.

The license.pvk file is used to authenticate the BigFix Master Operators, who are the highest level of authority in the BigFix hierarchy. They can perform any action on any computer or site in the BigFix deployment.

The license.pvk file is also used to sign the masthead file, which contains the configuration settings and the public key for the BigFix deployment. The masthead file isdistributed to all BigFix components, such as clients, relays, and consoles, to verify the identity and authority of the BigFix server.

The license.pvk file is not used to authenticate the BigFix Site Administrator, who is a special Master Operator that can manage the license and the masthead files. The Site Administrator uses the site admin password to access the license.pvk file and perform license-related tasks.

The license.pvk file is not used to authenticate the BigFix local operators, who are the lower level of authority in the BigFix hierarchy. They can only perform actions on the computers and sites that are assigned to them by the Master Operators. The local operators use their username and password to log in to the BigFix console.

The license.pvk file is not used to authenticate the BigFix LDAP operators, who are the local operators that are authenticated by an external LDAP server. They use their LDAP credentials to log in to the BigFix console. References:

Managing licenses

Missing or Lost license.pvk file

Check private key password - license.pvk

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