Blue Prism ATA02 Designing a Blue Prism (Version 6.0) Environment Exam Practice Test

Policies applied by Active Directory such as multi-factor authentication and password complexity are applied to Blue Prism

It makes it possible to add custom security roles in Blue Prism

Users are assigned security roles based on their group membership in Active Directory

Data encryption between Blue Prism devices is provided by default

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

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

WCF: Soap with Message Encryption and Windows Authentication

WCF: Soap with Remote Encryption

WCF: Soap with Transport Encryption

.NET Remoting with Transport Encryption

HTTPS Connection mode

Remoting connections between Application server and runtime resource

Instructional communications between Interactive Clients and Runtime resource

Database connection between the database server and Runtime resource

Inbound web services connections from the Application server to Runtime resource

The credentials are managed by the Windows Credential store and the security applied is proprietary to Microsoft

The credentials are encrypted by the Application Server for storage in the database using either 3DES or AES-256 and a user generated key

The credentials are encrypted by the Application Server for storage in the database using either 3DES or AES-256 and a secure key hardcoded within the application

Credential Management is handled using session variables and security is applied based on the process logic that is defined.