HCL-BF-PRO-10 Exam Dumps - HCL Software Academy Certification Questions and Answers

According to the BigFix Platform documentation, the upgrade Fixlet in the Support site does not upgrade a remote server correctly. You must run the full BigFix server installer to perform the upgrade. Remote database setups might encounter problems during upgrade and require resetting database connection settings after manually running the BigFix Server installer1.

The upgrade procedure is as follows:

• Upgrade the Server Installers using the Support Fixlets.
• Run the Server installer as a user that has DB Owner or SA permissions to the database server. The installer recognizes that the Server is at an earlier version and asks if you want to upgrade to the latest version.
• Run the BigFix Administrator Tool (BESAdmin.exe) to update the remote database tables; you will be prompted for the site admin password. Note: The BESAdmin.exe should be run automatically, if your account has the DB Owner or SA privileges to the remote database.
• The BigFix server is now correctly upgraded.

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

• Running the server installer as a local administrator does not guarantee that the user has the appropriate database permissions.
• Using the upgrade Fixlets from the console does not work for a remote server setup.
• Upgrading the server installers and using the upgrade Fixlets from the BigFix Console is redundant and unnecessary.

References:

• Upgrading a BigFix server with a remote database
• [BigFix Server Upgrade Guide]

• Launch the BigFix Administration Tool from the Start menu or from the installation folder.
• Enter the current password for the Site Administrator private key and click OK.
• Click the Advanced Options tab and select Change Site Administrator Private Key Password.
• Enter the new password, confirm it, and click OK.
• Restart the BigFix Server service for the changes to take effect. References:
• Re-creating Site Credentials
• Change Private Key Password
• Need help in to recover or set a new password for the Bigfix Admin

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?

According to the BigFix Platform documentation1, the standard Relay configuration can support up to 5,000 endpoints per Relay, while the high scale Relay configuration can support up to 10,000 endpoints per Relay. The high scale Relay configuration requires more hardware resources and tuning parameters than the standard Relay configuration. To configure a high scale Relay, you need to follow these steps2:

• Install the Relay on a dedicated server with at least 8 CPU cores, 16 GB of RAM, and 500 GB of disk space.
• Set the _BESRelay_HTTPServer_MaxConnections setting to 2000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ParentRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxSize setting to 10000000000 on the Relay.
• Set the _BESRelay_PostResults_ChildRelayBufferDirectoryMaxCount setting to 100000 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinute setting to 0 on the Relay.
• Set the _BESRelay_Download_LimitBytesPerMinutePerClient setting to 0 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_PreCacheStageDiskLimitPercent setting to 0 on the Relay.
• Set the _BESRelay_Download_CacheLimitMB setting to 100000 on the Relay.
• Set the _BESRelay_Download_CacheLimitPercent setting to 0 on the Relay.
• Restart the Relay service after applying the settings. References:
• Relay scalability
• Configuring a high scale Relay

• On a Windows Root Server, the service that is responsible for inserting client report data into the database is BES FillDB.
• BES FillDB is a process that runs on the BigFix Server system and is responsible for storing the information returned from the BigFix Agents into the BigFix database. This information can be data, such as the value of retrieved properties or the result of the evaluation of the applicability relevance or the success criteria of Fixlets and Tasks, or the information contained in a report returning the result of a BigFix Query1.
• BES FillDB reads the buffer directory content, parses the report, and stores the report data in the database. It also offers a parameter called DatabaseBoostLevel to optimize BigFix performance2.
• The other services listed are not responsible for inserting client report data into the database. BES ServerDB Plugin Service is a service that allows the BigFix Server to communicate with the database. BES Root Server is a service that manages the communication between the BigFix Server and the BigFix Agents. BES GatherDB is a service that gathers the site content from the BigFix Server and stores it in the database3. References:
• Configuring FillDB
• Configuring the FillDB database performance
• BigFix Services

• Locking a BigFix Client means preventing it from accepting any actions that could modify its state, such as installing patches, changing settings, or running scripts1.
• Locking a BigFix Client can be useful for various reasons, such as testing new actions on a subset of unlocked computers, protecting critical or sensitive systems from unwanted changes, or complying with security policies or regulations12.
• Locking a BigFix Client can be done by using the BigFix Console, the BigFix WebUI, or the BES Client API13.
• Locking a BigFix Client does not affect its other functions, such as reporting, gathering, relay selection, or client settings2.
• The locked status of a BigFix Client can be changed by sending an unlock action, which can be done by a Master Operator or a Non-Master Operator who has the Write permission to the site where the client is subscribed14.
• The locked status of a BigFix Client can also be set to expire after a certain period of time, by using a custom action script15.
• Therefore, the only valid reason among the options for locking a computer is D. When changes or updates need to be excluded from the computer. References:
• 1: Locking clients
• 2: Just how locked is “Locked”?
• 3: [BES Client API]
• 4: [The Console Operators]
• 5: [Locking a client for a specific period of time]
• 6: [Locking clients]
• 7: [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]
• : [Locking clients]
• : [Just how locked is “Locked”?]
• : [BES Client API]
• : [The Console Operators]
• : [Locking a client for a specific period of time]

• 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

• 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