Blue Prism Designing a Blue Prism (Version 6.0) Environment ATA02 Exam Dumps: Updated Questions & Answers (November 2025)

Blue Prism Interactive Clients

Blue Prism Application Server(s)

Other Blue Prism Runtime Resources

Third party systems accessing Blue Prism web services

Blue Prism Credential Manager

Whether the different environments will be accessing the same processes

Whether there are any security related reasons to segregate services on to separate devices

Whether it is acceptable for product updates to be applied to all environments simultaneously

It is not possible to host multiple Application Server services on a single device

One of the WCF connection modes should be used. .NET remoting is provided for legacy support purposes only.

Either WCF or .NET remoting may be selected. It does not matter which is used.

It is important to ensure that all Blue Prism clients are configured to use the same connection mode as the Blue Prism Server that they are expected to connect to

It is important to configure the Blue Prism certificate server prior to establishing a connection from a client

The Blue Prism interactive client can be used on its own to monitor the environment in its entirety

Monitoring of Blue Prism is not necessary

External Monitoring tools should be used to monitor system performance

Event logs should be monitored for application errors

Process execution related errors may need to be dealt with by a business operations team

Process related errors are automatically sent to the event log

SQL Always on Availability Groups

Windows Clustering

Replication

Blue Prism Active Sync

Connect an application server to 2 Database Instances in parallel

Resource pools and Active Queues can be used to distribute work to Runtime Resources which are online

The Runtime Resources are “stateful” devices, therefore any failure or maintenance event should also be taken into account in the process design and scheduling methodology

Using a load balancer and 2 application servers will ensure high availability of an automated process

Use the setting within a Blue Prism Process to force a process to fail over to an alternative Runtime Resource in the event of a failure.

There may be additional implications to the overall complexity of the architecture, due to the additional components involved in the virtualization technology

It will only ever be possible to use Surface Automation to Automate these applications

The Login Agent application must be available prior to User Login

The mapping between virtualized applications and users is often 1:1. This needs to be considered when designing the credential management approach for the Runtime Resources

Customizations to the application may be lost after the user is logged out or the system is rebooted, unless additional mechanisms are used to preserve them

Surface Automation will always need to be used in these scenarios

Redundancy - e.g. to provide a level of continuity if one Application Server fails

To increase the overall security of the environment

The number of connected clients and runtime resources

The Application Server doubles up as a Web Server for a separate application

Virtualization of the database server should only be considered after fully reviewing the specific vendor recommendations for the Hypervisor and SQL server version

The Database server should never be virtualized

Virtualization is only supported on Vmware Hypervisor technology

Virtualization should be considered only in very small environments

The key is always stored in the database

The key is always stored within the config file on the Application Server

The key can either be stored in the database, in the config file on the Application Server, or in a separate securable file on the Application Server

The key is hard-coded and stored securely within the Application. It is subjected to obfuscation to ensure it's protection

The key can only be stored in the database or in the config file on the Application Server