Free Practice Questions for the Blue Prism Developer AD01 Exam (2026 Updated)

Understanding Control Room Functions:

The Control Room in Blue Prism is used to manage and monitor running processes and manage work queues.

Capabilities of Control Room:

Set the Maximum Attempts parameter for the Work Queue (Option A): This is a parameter setting available in the Control Room for work queues.

Rename a Work Queue (Option B): Work queues cannot be renamed from the Control Room.

Delete items from a Work Queue (Option C): Items in a work queue can be deleted from the Control Room.

Refresh Work Queue data (Option D): The Control Room allows refreshing the data displayed for work queues.

Create a Work Queue (Option E): Work queues are created in the System Manager, not in the Control Room.

Encrypt a Work Queue (Option F): This can be managed from the Control Room to ensure data security.

Conclusion:

The activities you can perform in Blue Prism Control Room are:

A. Set the Maximum Attempts parameter for the Work Queue

C. Delete items from a Work Queue

D. Refresh Work Queue data

F. Encrypt a Work Queue

References:

Blue Prism Developer Documentation: Control Room Functions

Blue Prism Training Material on Work Queue Management

Reason: This is happening when identifying the elements in application modeler some of the details which are changing on the different environment and while identifying the elements in application modeler the developer takes the element whose values are changing and when the application run on the different path at that point of the time the process is able to expecting values eg same url, date or title but it is not at there so the process terminates. Follow the best practice for this.

Exception Handling Best Practices :

Proper exception handling involves not only recovering from an error but also ensuring the system is ready for subsequent operations.

This typically includes resetting the application or any global data to a known good state.

Issue in the Main Page :

In the provided diagram, the flow directly connects the Recover stage to the Resume stage without any intermediate logic.

This is problematic because the system might be left in an inconsistent state after an error.

Required Logic :

Implement logic between the Recover and Resume stages to reset the application or any relevant data.

This ensures that after handling an exception, the system is in a known good state and can continue processing new items reliably.

References :

Blue Prism documentation on best practices for exception handling and process design.

Understanding the Process Diagram:

The diagram includes a calculation stage named " Get Date of Previous Day " and a data item named " Result Date " .

The Calculation Properties window shows the expression Yesterday() used in the calculation stage.

Analysis of the Calculation Stage:

The Yesterday() function is used to get the date of the previous day.

The result of this function is stored in the " Result Date " data item.

Data Type Considerations:

Option A: This option is incorrect because there are correct statements regarding the process diagram.

Option B: If " Result Date " is configured as a Text data type, a ' data type mismatch ' Internal Exception will indeed be thrown because the Yesterday() function returns a date, not text.

Option C: If " Result Date " is configured as a Date data type, the Yesterday() function will correctly set " Result Date " to the previous day ' s date.

Option D: This option is incorrect because the Yesterday() function is valid and will not throw a ' Failed to evaluate expression ' Internal Exception if used correctly with a date data type.

Conclusion:

The correct statement is:

C. If the ' Result Date ' data item is configured as a Date data type, then the ' Result Date ' data item will be set to the date of the previous day on execution of the Calculation stage.

References:

Blue Prism Developer Documentation: Date Functions

Blue Prism Training Material on Calculation Stages and Date Manipulation

In Blue Prism, the Wait stage is used to pause the process until specific conditions are met or a timeout occurs. The following points explain why Option B is the correct answer:

If all conditions are met before the TimeOut period expires, the process will continue (Option B) : This is the correct behavior of the Wait stage. If the speci fied conditions are met before the timeout period, the process will continue without waiting for the entire timeout duration.

The other options are incorrect:

The Wait Stage will sequentially check each condition, it does not require all conditions to be met (Option A) : This is incorrect because the Wait stage does not check conditions sequentially but rather waits for any specified condition to be met.

If no conditions are met, an internal error will appear and terminate the process (Option C) : This is incorrect; if no conditions are met within the timeout period, the process will follow the timeout path, which may or may not terminate the process depending on how it is handled.

The Wait Stage will simultaneously check all conditions and follow the logic of whichever condition is met first (Option D) : This is incorrect because the Wait stage waits for any one of the conditions to be met before the timeout, rather than following the logic of the first met condition.

References Refer to Blue Prism ' s documentation on the Wait stage and its behavior in processes, highlighting how conditions and timeouts are managed.

Reason: Global send key events and global keys are not passed through the navigate stage.

Active Directory Integration :

With Active Directory Integration, user authentication can be managed through the organization ' s Active Directory, enabling better user management and security.

Encrypt and Decrypt Work Queue Item Data :

With the Credentials Manager functionality deployed, it is possible to encrypt and decrypt sensitive data within work queue items, enhancing data security.

Functionality Added :

These functionalities enhance security and streamline user management in future automations.

References :

Blue Prism documentation on Credentials Manager and its integration with Active Directory and work queue item encryption.

Defined Package Requirement :

To generate a release, you must first define a package. The package includes all the components (processes, objects, etc.) that will be included in the release.

File Types for Import :

Blue Prism allows importing of two types of files: Release files (.bprelease) and Skill packages (.bpskill). These are the only file types that can be imported via the Release Manager.

Incorrect Statements :

A. Release files cannot be imported by anyone regardless of their user permissions. Importing releases requires specific user permissions.

C. The Modify Package wizard does not update previous components released within your environment; it modifies the package for the current release.

E. The Verify wizard does not test a Package ' s components for changes since the last release; it ensures all components are included and dependencies are met.

References :

Blue Prism documentation on Release Manager and package management.

Tagging Exception Items :

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging :

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits :

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.

References :

Blue Prism documentation on exception handling, tagging, and logging.

Understanding Environment Variables:

Environment variables are global variables that are accessible across multiple processes and sessions within Blue Prism.

They are typically used to store configuration settings and other information that need to be consistent across different processes.

Updating Environment Variables:

Internal - Global Variables Business Object (Option A): This business object can be used to update the value of environment variables programmatically within a process.

Calculation Stage (Option B): This stage cannot be used to update environment variables directly because it only works with data items within the context of the process.

Global Variables Store in Environment Manager (Option C): This is a specific area within the Environment Manager where environment variables can be managed and updated.

System Manager (Option D): This is another tool within Blue Prism where environment variables can be updated.

Conclusion:

The correct options to update the value of a data item exposed as an Environment Variable are:

A. Using the ' Internal - Global Variables ' Business Object to update the value.

C. Using the Global Variables store in Environment Manager to update the value.

D. Using System Manager to update the value.

References:

Blue Prism Developer Documentation: Environment Variables

Blue Prism Training Material on Variable Management and Configuration

Understanding Session Variables:

Session variables are specific to a running instance of a process and can be changed dynamically during the execution of the process.

Behavior of Session Variables:

When the value of a session variable is changed, it is designed to be immediately available to the running process. This allows for real-time adjustments and interactions during the process execution.

Conclusion:

The new value of a session variable is available to a running process immediately after it is changed.

References:

Blue Prism Developer Documentation: Session Variables

Blue Prism Training Material on Process Execution and Variable Management

In Blue Prism ' s Application Modeller, the " Identify " button offers different options for identifying and working with elements in an application. Understanding the difference between the " Spy Element " and " Navigator " options is crucial for effective element identification and automation design.

Spy Element (Option D) : This option allows you to manually identify an element to use in the Application Modeller. When you select " Spy Element, " you manually click on the element within the application to capture its attributes and use them for automation.

Navigator Options (Option D) : The Navigator options, including " Open Application Navigator " and " Open UI Automation Navigator, " display a tree of elements available to choose from. These navigators allow you to browse through a hierarchical view of elements in the application, making it easier to select and identify elements that might be difficult to manually spy.

The other options are incorrect because:

Option A : This does not accurately describe the functionality of the Spy Element and Navigator options.

Option B : This option misrepresents the primary use of the Navigator options, which is for browsing and selecting elements rather than debugging.

Option C : This is the reverse of the actual functionality. The Spy Element is used for manual identification, while the Navigator options display a tree of elements.

References Consult Blue Prism ' s documentation and user guides on Application Modeller and element identification methods to understand the distinct functionalities of Spy Element and Navigator options.

Understanding the Diagram:

The diagram shows a retry loop where the process attempts to perform a search, read results, and handle exceptions by retrying up to 3 times.

' Retry Limit ' is set to 3, and ' Retry Count ' starts at 0 and is incremented by 1 in each retry attempt.

Analyzing the Logic:

Option A: The Resume stage should resume the process outside the exception block, which is correct.

Option B: Exception handling in the process layer is valid; it does not have to be exclusively in the object layer.

Option C: Each action does not need an individual retry loop; the overall block retry is acceptable.

Option D: This option highlights a missing step. After handling an exception and before retrying, the application needs to be reset or ensured it is ready to retry the ' Search Screen - Perform Search ' action.

Identifying the Issue:

The retry logic should include steps to ensure the application state is appropriate for another search attempt. This might include resetting fields, waiting for the application to be ready, or ensuring the previous error state is cleared.

References:

Blue Prism Developer Documentation: Exception Handling and Retry Logic

Blue Prism Training Material on Process Flow and Exception Handling