Database Setup and Configuration
The database is the heart of the platform
Every Blue Prism environment depends on a supported SQL Server instance holding the Blue Prism database. Candidates must know the creation workflow: an empty database is created with appropriate collation and recovery settings, the schema is then built using the Blue Prism-provided scripts or the installer's database configuration step, and finally the connection is validated. Collation must be consistent between the database and the server; a mismatch is a frequent cause of failures during schema creation or later during queries.
Service accounts need the right permissions. The account running the application server services requires rights to connect and execute within the database, typically through a dedicated login mapped to a database user with the appropriate role. Granting sysadmin to everything is a red flag in exam questions - the correct answer usually describes least privilege with the specific roles Blue Prism documents.
Other concepts to master: recovery model choice (full recovery with regular transaction log backups for production, simple only where loss tolerance is acceptable), the importance of a maintenance plan for index and statistics upkeep, and the behaviour of the database when the application server loses connectivity. Questions often present a scenario where the database is restored from backup and ask what else must be reconfigured - encryption keys and connection strings are common answers.
Rule of thumb: if the database was restored to a different server name, expect to reconfigure the connection and re-establish any encrypted credentials rather than assuming the restore is complete.
Worked example: after restoring a production database to a test instance, the environment fails to start sessions. The engineer verifies the service account login exists on the new instance, checks collation matches, and confirms the connection string points to the new host.