Free Practice Questions for HCL Software Academy HCL-BF-PRO-10 Exam

An external site is a site that is created and maintained by HCL or a third-party vendor, and is subscribed by the BigFix administrator1. External sites provide content such as fixlets, tasks, analyses, and dashboards for various purposes, such as patching, compliance, inventory, and security1.

The site properties for an external site in the Console show the following information2:

Name: The name of the site.

Publisher: The name of the organization that created and maintains the site.

Description: A brief summary of the site’s content and purpose.

Current Version: The version number of the site that is currently subscribed by the BigFix server.

Gather Status: The status of the site’s subscription, such as Active, Pending, or Failed.

Gather Date: The date and time when the site was last gathered by the BigFix server.

Gather URL: The URL from which the site’s content is downloaded by the BigFix server.

Subscription: The subscription expression that determines which BigFix clients are subscribed to the site.

Therefore, the correct answer is C. Description, as it is one of the information that is displayed in the site properties for an external site in the Console, along with Publisher and Current Version. The other options, A. Creator, B. Gather URL, and D. Created Date, are not correct, as they are either not shown or not relevant for the question. References:

Sites

Viewing site properties

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

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

The Four Eyes Approval feature is a security mechanism that requires the approval of another console operator who is a member of a specified role before an action can be executed. This feature is useful for preventing unauthorized or accidental actions that could affect the endpoints in the BigFix deployment. To enable this feature, you need to follow these steps:

Use the BigFix Administration Tool to add the useFourEyesAuthentication advanced option and set its value to true.

Restart the BES Root Server service and the BigFix Console.

Create a role for the approvers and add one or more operators to it.

Select the Actions Require Approval option for the operators who need to get approval for their actions and choose the approvers role from the drop-down list.

When an operator takes an action that requires approval, they will see a dialog box asking them to enter the credentials of an approver. The action will be pending until an approver logs in and approves it. References:

Four Eyes Approval Capability

Has anyone tried SAML Authentication with Four-Eyes authentication?

BigFix Platform Security Configuration Guide

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

The WebUI cache is used to improve the response time of the WebUI by storing and refreshing some data that requires complex calculations, such as the number of applicable devices or patches1.

The cache refresh interval, also known as the cache Time To Live (TTL) value, determines how often the cached data is invalidated and updated1. The default value is 600 seconds (10 minutes)1.

To change the cache refresh interval, you can use the client setting _WebUIAppEnv_CACHE_TTL and enter the desired interval in seconds1. The minimum value is 180 seconds (3 minutes)1.

Increasing the cache refresh interval can reduce the impact on system resources, especially for large deployments and intensive patching activities1. However, it can also affect the freshness of the cached data1.

Another setting that affects the WebUI caching is _WebUIAppEnv_CACHE_INTERVAL, which determines how often the WebUI checks for new data from the BigFix server1. The default value is 60 seconds1.

Decreasing the cache interval can improve the responsiveness of the WebUI, but it can also increase the load on the BigFix server1. Therefore, you should balance the cache interval and the cache TTL values according to your needs and environment1.

The other settings, _WebUIAppEnv_SP_QUEUE_CONCURRENT, _WebUIAppEnv_DATA_REFRESH_SECONDS, and _WebUIAppEnv_SITE_CACHE_SIZE, are not related to the WebUI cache refresh interval12.

_WebUIAppEnv_SP_QUEUE_CONCURRENT limits the number of stored procedures that run simultaneously per app in the background that update cache values1. The default value is 51.

_WebUIAppEnv_DATA_REFRESH_SECONDS determines how often the WebUI polls the BigFix server for new data2. The default value is 15 seconds2.

_WebUIAppEnv_SITE_CACHE_SIZE specifies the maximum size of the site cache in megabytes2. The default value is 100 MB2.

References:

Caching - HCL Product Documentation

Server settings definitions - HCL Product Documentation

Domains are a major organizing principle in the BigFix Console that allow you to access and manage related sites, such as Patch Management, AntiVirus Management, Power Management, and so on.

Domains are not collections of Fixlet messages, but rather contain a set of related sites that have Fixlet messages, tasks, analyses, and other content. The content is created by HCL, other vendors, or yourself, depending on the site type and subscription.

Domains do not provide a way to deploy actions across the network, but rather help you to find and select the relevant content for your actions. You can still use the Action Wizard or the Take Action button to deploy actions from any domain or site.

Domains are located in the lower-left portion of the Console, where you can select the domain you want from the buttons at the bottom of the panel. The contents of the domain are then displayed in the upper-right panel, where you can filter and sort them by various criteria.

Domains are not located under Tools in the Console, but rather under the Sites node in the navigation tree. You can also access the Manage Domains dialog from the Tools menu, where you can create, edit, or delete domains. References:

Domains

Introducing Domains

Manage Domains

The Fixlet Updated Windows Installation Folders - BigFix version 10 0 8 Nov; Available! is a special Fixlet that is released by HCL when a new version of the BigFix platform is available1.

This Fixlet allows the administrator to update the BigFix installers that were created by the Installation Generator during the initial BigFix Server installation1.

The administrator can use the BigFix console to take action on this Fixlet and target the BigFix Server computer1.

The action will download the latest version of the BigFix installers from the License Download portal and replace the existing files on the BigFix Server1.

This way, the administrator can ensure that the BigFix installers are always up to date and ready to be used for upgrading or installing other BigFix components1. References:

1: Upgrading the BigFix platform using Fixlets

2: BigFix Download Center