Free Practice Questions for Blue Prism AD01 Exam

Spy modes in Blue Prism are used to interact with different types of applications. The correct statements about spy modes are:

Browser Mode is the default mode used for web-based applications (Option D): This is the most accurate statement. Browser Mode is specifically designed for interacting with web-based applications and is the default mode for such cases.

The other options are incorrect:

Accessibility Mode is the most commonly used for open source web applications (Option A): Accessibility Mode is used for interacting with applications designed with accessibility in mind, not necessarily open source web applications.

Win32 Mode is the default mode used for web-based applications (Option B): Win32 Mode is used for desktop applications that use the Win32 API, not web-based applications.

HTML Mode is the most commonly used when a Code Stage is required (Option C): HTML Mode is used for web applications, but the use of a Code Stage does not determine the spy mode.

ReferencesRefer to Blue Prism's documentation on spy modes, which explains the appropriate use cases for each mode.

Loop Structure:

The loop iterates through each row in the Data collection.

For each row, it checks the "Full Time?" condition.

Condition:

If "Full Time?" is true, the process continues to "Generate Report of Full Time Employees".

If "Full Time?" is false, the row is removed from the collection.

Loop Execution:

Initially, there are 4 rows in the Data collection.

If any row is not full-time, it is removed.

Outcome:

The decision to generate the report happens only if all rows satisfy the "Full Time?" condition.

Since the diagram does not specify that any rows are full-time and the decision to remove rows occurs based on a negative condition, all rows could potentially be removed.

Final Report:

Given the process flow and assuming all rows do not meet the "Full Time?" condition, no rows are left for generating the report.

References:

Blue Prism documentation on loop stages and decision stages.

In Blue Prism, collection columns are referenced in expressions using dot notation. This allows for dynamic and precise access to specific data within a collection.

Expressions (Option B): When you need to reference a specific column in a collection within an expression, you use dot notation. For example, if you have a collection named EmployeeData with a column named FirstName, you would reference it as EmployeeData.FirstName in an expression.

The other options are not correct in this context:

Loop Properties (Option A): While loops interact with collections, they do not use dot notation to reference columns.

Work Queue (Option C): Work queues handle items as a whole and do not use dot notation for columns within collections.

Business Object (Option D): While Business Objects can manipulate collections, the specific reference to collection columns using dot notation is primarily used in expressions.

ReferencesConsult Blue Prism's documentation on expressions and how to work with collections within them for precise data referencing using dot notation.

Stage Logging in Production:

Logging is essential in a production environment to monitor the process execution and troubleshoot issues.

Decision Stage:

Decision stages typically evaluate conditions and direct the flow based on the evaluation.

Extensive logging for every decision can generate large log files, making it harder to find relevant information.

Best Practice:

Setting the logging to "Errors Only" ensures that only significant issues are logged, reducing log size and focusing on critical problems.

This is especially useful in a production environment where performance and log manageability are key.

References:

Blue Prism best practices for logging and monitoring in production environments.

In a Citrix environment, where traditional spying modes might not work effectively due to the nature of remote desktop applications, Surface Automation techniques are used. The Region mode allows you to define specific areas of the screen to interact with, making it suitable for environments where duplicate elements are present.

Region (Option D): This spy mode allows you to define a specific area on the screen and interact with elements within that region. This is particularly useful in Citrix environments where other spy modes might fail to differentiate between duplicate elements.

The other options are less effective in this scenario:

Win32 (Option A): This mode is used for traditional Windows applications but might not work well in a Citrix environment.

Browser (Option B): This mode is designed for web-based applications and is not suitable for Windows applications in Citrix.

Application Navigator (Option C): This mode is not typically used for surface automation in Citrix environments.

ReferencesConsult Blue Prism's documentation on surface automation techniques and best practices for automating applications in Citrix environments.

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

Environment variables value will only be change when the next time process runs and the session variables will change immediately on change in control room.

Session variables values will only be change from the control room and the env variables is only change from the system manager.

Single Object Design:

According to Blue Prism best practices, it is generally recommended to minimize the number of objects and actions to keep the solution simple and maintainable.

Actions:

Get Account Details: This action retrieves account information from the screen.

Apply New Limit: This action applies a new limit to the account.

Decision-Making Logic:

The decision-making logic (checking for high-risk code) should be placed in the process, not the object. This separation ensures that the object focuses on interacting with the application, while the process handles the business logic.

References:

Blue Prism best practices on object design and separation of concerns between objects and processes.