Blue Prism Technical Architect study plan

Diagram the full Blue Prism architecture from interactive client through application server, database, and runtime resources, labeling each tier's role and communication path.

Explain the difference between an interactive client license and a runtime resource license, and list which components each one enables.

Describe how Blue Prism handles session persistence and what happens to a running process when the client disconnects.

Identify the database platform options and the minimum infrastructure prerequisites for a production deployment.

Compare authentication modes (native Blue Prism, Active Directory, SSO) and state the trade-offs for a regulated enterprise.

Explain how role-based access control maps users to process and object permissions, and design a minimal role matrix for three personas.

Describe how credentials are stored and retrieved at runtime, including the role of the credential store and the encryption boundary.

Outline the network and firewall requirements between client, application server, and database tiers.

Map each ROM pillar (vision, organization, process, technology, people) to a concrete artifact an architect would produce.

Define the responsibilities of the key delivery roles: Solution Design Authority, Process Owner, and the automation delivery team.

Draft a governance checklist for approving a new process for automation, including intake criteria and prioritization scoring.

Distinguish the control points an architect owns versus those the operations team owns during and after go-live.

Apply process design standards: naming conventions, page structure, and separation of business logic from exception logic.

Design a process that uses work queues correctly, including item locking, retry behavior, and status transitions.

Specify how to decompose a large process into reusable objects and sub-processes without creating circular dependencies.

Write a solution design document outline that a reviewer could use to sign off before build starts.

Compare application integration approaches: surface automation, UI automation, API/web services, and direct database access, with criteria for choosing each.

Model an application in Object Studio with a clean action layer, separating navigation, read, write, and wait actions.

Explain spying modes and when each is appropriate, and describe how to make element attributes resilient to UI change.

Design an object interface that a process layer can consume without knowing application internals.

Classify exceptions into business, system, and recoverable categories, and specify the handling path for each.

Design a retry and recovery pattern that avoids duplicate transactions when a process fails mid-item.

Define data retention and audit logging requirements, including what must be captured for regulatory review.

Describe how to secure data in transit and at rest within the automation estate, and where sensitive data must never be written.

Describe the release lifecycle from development through test to production, including the artifacts promoted at each stage.

Explain how to package and import a release, and what must be verified before promotion is approved.

Identify environment-specific configuration that must not be hard-coded in process logic.

Outline a rollback plan for a failed production release.

Estimate capacity requirements from transaction volume, average handling time, and peak load, and translate that into runtime resource counts.

Identify common performance bottlenecks in process design and in infrastructure, and propose mitigations for each.

Review the full domain list and close knowledge gaps by re-testing the two weakest areas.

Assemble a personal one-page reference sheet of the facts most likely to be tested.