HCL-BF-PRO-10 Dumps With Exact Questions and Answers

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

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 key 1 .

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 report 1 .

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 used 1 .

Therefore, the BigFix Root server requires additional CPU resources appropriate to the number of managed endpoints to process the encrypted reports 1 .

The other options are incorrect because:

A is not relevant to the question, as it assumes that there are top-level Relays in the deployment. The question states that there are no top-level Relays, so all Relays are downstream from the BigFix Root server.  Moreover, the RAM requirement for Relays is not affected by MLE, as Relays do not perform any encryption or decryption by default 1 .

C is not necessary, as adding an additional NIC to the BigFix Root server does not affect the CPU load caused by the encrypted reports.  The network bandwidth requirement for MLE is not significantly higher than for clear-text reports, as the encryption adds only a small overhead to the report size 1 .

D is not a valid setting for the BigFix Root server, as it only applies to Relays that are configured to decrypt and repackage encrypted reports before relaying them to the BigFix Root server 2 .  This setting controls the maximum number of concurrent decryption threads on a Relay, and does not affect the BigFix Root server 2 .  References:

1 :  Message Level Encryption (MLE) Overview

2 : [Enabling encryption on Relays]

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

passwordComplexity : Set to a regular expression that defines the password complexity requirement. For example,  (?=.*\d)(?=.*[a-z])(?=.*[A-Z] ).{8,}  means that the password must contain at least one digit, one lowercase letter, one uppercase letter, and be at least 8 characters long.

passwordComplexityDescription : Set to a human-readable string describing the password complexity requirement. This string will be shown to the user when a password choice fails the complexity requirements set using the  passwordComplexity  option. An example password complexity description is “Passwords must have at least 6 characters.”

passwordMinLength : Set to the minimum length of acceptable passwords. The default value is  6 .

passwordMaxLength : Set to the maximum length of acceptable passwords. The default value is  256 .

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