HCL-BF-PRO-10 Practice Exam Questions with Answers HCLSoftware U Certified Professional-BigFix Platform 1 Certification

• 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:
• 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 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 WebUI is a web-based interface that provides access to the flexibility and power of BigFix.
• The WebUI has some upper use limits that depend on many factors, such as the number of endpoints, the workload, the time of day, the server location, and the number of concurrent users.
• Concurrent users are defined as highly active users who perform multiple actions per minute on the WebUI.
• According to the BigFix Capacity Planning Guide, both the Windows and Linux WebUI instances support 36 concurrent users on a 250k deployment base. This is the recommended scalability limit for the WebUI server on BigFix v10.x.
• The WebUI also requires additional hardware resources, such as CPU, memory, and storage, to power the WebUI. These resources are in addition to the BigFix root server requirements and depend on the number of concurrent users.
• The WebUI also implements a database cache for several counters to improve the WebUI response times. The cache has a default refresh interval of 10 minutes. References:
• Hardware Requirements
• WebUI Administrators Guide
• BigFix WebUI

• A Non-Master operator can create a Retrieved Property by creating an Analysis, which is a collection of properties and relevance expressions that can be evaluated on a set of computers1.
• To create an Analysis, the operator needs to have the Create Custom Content permission and the Read permission on the site where the Analysis will be created2.
• To create an Analysis, the operator can follow these steps3:
• After creating the Analysis, the operator can activate it by right-clicking on it and choosing Activate from the context menu. The Analysis will then be evaluated on the computers that match the relevance expression and the property values will be reported to the server4.
• The operator can view the property values by selecting the Analysis from the Analyses list area in the Console and then selecting the Results tab. The property values will be displayed in the columns corresponding to the property names.
• The operator can also use the property values as filters, sorts, or targets in other Console features, such as computer listings, Fixlet actions, or Web Reports.

References:

• 1: What is an Analysis?
• 2: Creating an Analysis
• 3: Creating an Analysis
• 4: [Activating an Analysis]
• : [Viewing Analysis Results]
• : [Using Analysis Properties]

To create a patch policy, you need to follow these steps12:

• On the Policies page, click Add Policy. The Add Policy page is displayed.
• Provide the following information under Policy Criteria page: Policy Name, Site, Description, Custom Content Criteria, and External Content Criteria.
• Click Next to configure the Pre-Patch and Post-Patch behaviour of the new policy.
• Click Next to configure the Schedule for the new policy. You can set the Start Date, End Date, Frequency, and Execution Window for the policy deployment.
• Click Next to select the Targets for the new policy. You can choose from Manual Selection, Automatic Group, or Relevance Expression.
• Review the Summary of the new policy and click Save to activate it. References:
• Patch Policy Overview
• Create a Patch Policy

• 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

• Starting from V9.5.6, the relay diagnostics page is disabled by default and can be protected by a password when enabled.
• To enable the relay diagnostics page, you need to set the client setting _BESRelay_Diagnostics_Enable to a value of 1 on the relay computer. You can do this using the BigFix Console, the registry editor, or a custom fixlet or task.
• To protect the relay diagnostics page with a password, you need to assign a value to the _BESRelay_Diagnostics_Password client setting on the relay computer. You can do this using the same methods as above.
• After setting the _BESRelay_Diagnostics_Password, the URL to the relay diagnostics page must use the https protocol instead of http, otherwise the browser will show the “403 forbidden” error and the relay diagnostics page will not display.
• To access the relay diagnostics page, open a browser and type in the address field: https://:52311/rd or https://:52311/RelayDiagnostics, where is the address of the workstation where the relay that you want to check is installed. You will be prompted to enter the password that you set for the _BESRelay_Diagnostics_Password client setting.
• On the relay diagnostics page, you can gather information about your environment settings, relay status, console user authorization, site gathering, and client registration. References:
• Relay and Server diagnostics
• How can I enable _BESRelay_Diagnostics_Enable" = “1”
• Relay diagnostics

• A BigFix Client is a software agent that is installed on every computer that must be managed by the BigFix platform1.
• The BigFix Client continuously assesses the state of the computer against all subscribed content, which includes policies, checklists, and remediation tasks12.
• The BigFix Client communicates with its parent, which can be either the BigFix Server or a BigFix Relay, to report its status and receive new content13.
• The BigFix Client performs most of the analysis, processing, and enforcement work locally, reducing the workload and bandwidth usage of the BigFix Server14.
• The BigFix Client operates with less than 10 megabytes of RAM and can run on various operating systems, such as Windows, Linux, UNIX, and Mac OS1 . References:
• 1: BigFix Platform
• 2: Learning about SCAP
• 3: Relays and Servers
• 4: BigFix Architecture
• : Client requirements

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

According to the BigFix Platform documentation, when creating a new property, you need to provide a name and a relevance expression for the property. You also have the option to specify an evaluation period for the property, which controls how often the property is evaluated by the clients. This field is called Evaluate Every, and you can choose a time period from 5 minutes to one month, or use the default value of Every Report, which reevaluates the property with each report1.

The other options (A, B, and D) are not available fields when creating a new property, because:

• Create in site is not a field, but a button that allows you to create the property in a specific site2.
• Applicability is not a field, but a concept that determines whether a property is relevant for a given client or not3.
• CVEID is not a field, but an identifier for a common vulnerability and exposure that can be used in fixlets or analyses.

References:

• Creating Retrieved Properties
• Manage Properties
• Applicability Relevance
• [CVEID]

To create a new retrieved property in BigFix, the following steps are required:

• From the BigFix Console, select Manage Properties from the Tools menu. The Manage Properties dialog is displayed.
• You can filter the properties by using the left filter panel to select a subset of the properties to view on the right. If you cannot find what you want in this list, create a new property: click Add New, then enter a name for the property and a valid Relevance expression. This can access hardware characteristics, registry entries, and even data in specific files on the client computers.
• After you define the new property, the Clients automatically compute the value of the corresponding relevance expression and return it to the Database. Click the OK button.
• The new property will be available in the column headers of computer listings, allowing you to sort and filter on its values. It can also be used to target Fixlet actions and generate Web Reports.

References:

• Creating Retrieved Properties
• Adding new properties under “By retrieved properties”

• 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 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