AIE02 Blue Prism Installing and Configuring a Blue Prism (Version 6.0) Environment (EN) Free Practice Exam Questions (2025 Updated)

If it can’t find a BPServer.exe profile with the name that is expects

If the BPServer.exe profile is not configured with the expected encryption schemes

If the user that the server is attempting to use cannot access the Blue Prism database

If there are no Blue Prism devices configured to connect to the server service

There is a problem with the Blue Prism license key in the environment

If the server service has nothing to process (e.g. if there are no schedules configured)

Using a Blue Prism device, create a device database connection to connect to the server, use the in-product “Create Database” functionality

Using a Blue Prism device, connect to the Blue Prism Application Server, use the in-product “Create Database” functionality

Using SQL Management Studio create a database, manually run the CreateScript provided by Blue Prism, then use in-product “Configure Database” functionality

Using SQL Management Studio manually run the CreateScript provided by Blue Prism to generate to the database, then use the in-product “configure Database” functionality

Use the Blue Prism Client to configure a connection to a supported database server

Use BPServer.exe to create and configure a connection to a supported database server

Use BPServer.exe to create or configure a profile for the server service that uses a configured database connection

Use BPServer.exe to select an appropriate connection mode and, if required, to select a certificate to use

Use BPServer.exe to configure which users can log into Blue Prism

Use BPServer.exe to configure all encryption schemes for the environment that will use an Application Server key store

Use the /SSLCert switch in the Runtime Resource start up parameters

Under System ->Settings, enable the “Require secure resource connections” setting

Within the configuration for the Blue Prism Server select a Connection Mode that does not contain the text “Insecure”

Write an Application Server process which periodically polls all of the connected devise to evaluate the encryption that is being enforced

Not required – All SQL Server implementations are configured to enforce encryption by default

Configure the Blue Prism connection to the database to set encrypt=true; trustservercertificates=true

Configure the SQL Server with an appropriate certificate and configure it to only accept secure connections

Turn on IPsec for the network where the Application Server and SQL Server are deployed

Deploy a certificate on the Application Server and use the SSLCert switch

Configure a connection to a Blue Prism Application Server

Configure the database maintenance procedures

Configure the Runtime Resource to start automatically when the device is logged on with appropriate parameters

Optionally configure the Runtime Resource start-up procedure with the thumbprint of a local certificate

Optionally install and configure Login Agent

Ensure the AutomateC.exe is accessible to the logged in user

Disable all domain policies

Implement firewall rules to prevent unexpected devices from establishing a connection with the Application Server

Under System ->Settings, enable the “Prevent registration of new Resources” setting

All of the above

Review the message across all tabs within appropriate profile via BPServer.exe

Review the device Windows Application Event Logs

Review the server status panel in Control Room

Use a configured Blue Prism process to interrogate each connected server in turn

Review messages when starting the service manually using BPServer.exe

Use BPDiagnostics to start out a Server Diagnostics and Repair task

Provides a Login Agent Runtime Resource which can receive simple instructions prior to being in a logged in state

Allows a Login Agent Runtime Resource to immediately automatically login using saved credentials as part of a device reboot

Removes the requirement for locally stored device credentials

Provides the ability to manually instruct a Login Agent Runtime Resource to login

Provides the ability to schedule when a Login Agent Runtime Resource will be logged in

Allows processes which interact with locally installed applications to be executed without the device being logged in

A number of security settings need to be appropriately configured/disabled on each device where it runs (e.g. ctrl +alt+del prior to login must be disabled)

The Login Agent Runtime Resource is configured to use on of the Blue Prism connections configured on the local device

Editing the configuration of the Login Agent Runtime Resource can be done within the appropriate configuration file

Login Agent can only be used on devices that are members of an Active Directory Domain Network Infrastructure

Once a device has been logged in, a congenital Runtime Resource needs to be configured to start automatically (which will automatically shut-down the Login Agent Runtime Resource)

It ensures that the Runtime Resource establishes a secure outbound connection with the Application Server or Database Server

It ensures that inbound connections on the listening port (default 8181) will be encrypted

When hosting Web Services on the Runtime Resources, the inbound connections will need to use HTTPS

Only users who have used a domain account to log onto the device can launch Blue Prism

Use the /SSLCert switch in the Runtime Resource start up parameters

Under System -> Settings, enable the “Require secure resource connections” setting

Within the configuration for the Blue Prism Server select a Connection Mode that does not contain the text “insecure”

All of the above