Free Practice Questions for Blue Prism AD01 Exam

Attributes in Application Modeller:

Attributes List Consistency (Option A): The attribute list varies depending on the target application and element. Different applications and elements expose different attributes.

Initial Selection (Option B): Blue Prism's initial selection is not always optimal. It is recommended to review and adjust attributes for the best match.

Attributes Source (Option C): The attributes are provided by the target business application, meaning they are specific to what the application exposes.

Match Criteria (Option D): Attributes used in matching criteria have a tick in the Match column within Application Modeller, indicating their use in identifying the element.

Conclusion:

The correct statements are:

C. The attributes displayed in Application Modeller are provided to Blue Prism by the target business application.

D. Attributes which are included in the element match criteria contain a tick in the Match column of Application Modeller.

References:

Blue Prism Developer Documentation: Application Modeller Attributes

Blue Prism Training Material on Element Matching and Attributes

Pausing a Schedule:

Pausing the schedule is the best practice for temporarily stopping a process. This maintains the schedule's configuration and simply suspends its execution for the specified period.

Maintaining Configuration:

Pausing the schedule ensures that once the period is over, the same schedule can be resumed without needing to recreate it or adjust any start/end dates. This approach is simpler and minimizes the risk of configuration errors.

Reactivation:

After the required period, the schedule can be easily unpaused to resume its normal operation.

References:

Blue Prism documentation on scheduling and best practices for managing schedules.

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

Startup Parameters:

Startup parameters allow a process to be configured with specific input data before it runs. This can be used to customize the behavior of the process based on the provided inputs.

Setting Startup Parameters:

In Control Room, you can set startup parameters by right-clicking the session for the process you want to run and selecting "Startup Parameters".

This allows you to input the necessary data directly before the process starts, ensuring it runs with the correct configuration.

References:

Blue Prism documentation on setting and using startup parameters.

Intelligent wait stage should always be used after every stage and that should be minute wait to overcome the lag when the application runs and on wait should only be used when some of action interfacing the screens or any updating is going on as per the best practices pdf

In Blue Prism, there are specific stages that are available in Object Studio but not in Process Studio. These stages are designed to interact with applications and perform specific actions at a more granular level.

Option A (Action Stage): Found in Object Studio. It allows the object to call actions within other objects or business objects.

Option B (Read Stage): Found in Object Studio. It is used to read data from an application or interface.

Option E (Write Stage): Found in Object Studio. It is used to write data to an application or interface.

These stages are part of the functionality provided by Object Studio for interacting directly with applications, and they are not available in Process Studio, which is used for high-level process orchestration.

References:

Blue Prism Object Studio documentation

Blue Prism Process Studio documentation

Understanding Work Queue Icons in Blue Prism:

Work queue icons in Blue Prism provide a visual indication of the status of cases in the queue.

Each icon represents a different state of a work queue item.

Icons and Their Meanings:

Option A (Flag): This typically indicates a flagged item, often used to mark items that need special attention or have been deferred.

Option B (Lock): This represents a locked item, indicating that the item is locked and cannot be processed.

Option C (Checkmark): This indicates that the item has been completed successfully.

Option D (Three Dots): This icon represents a case currently being worked on by a digital worker.

Conclusion:

The icon that indicates a case currently being worked is Option D (three dots).

References:

Blue Prism Developer Documentation: Work Queue Icons and Status Indicators

Blue Prism Training Material on Work Queue Management