Blue Prism AD01 Practice Test - Questions Answers, Page 14

In Blue Prism, a Clean Up page is used to perform finalization tasks as the business object is closed down. This can include tasks such as closing all instances of applications, saving any final state, and releasing resources. The Clean Up page is called automatically by Blue Prism when the business object is disposed of at the end of a business process.

Option A (Close All Instances): This is the correct use of the Clean Up page. It involves closing all instances of the application or resources that were used during the process. This ensures that no instances are left open, which could otherwise lead to resource leaks or conflicts.

The other options are not ideal for the Clean Up page:

Option B (Save Workbook): While saving a workbook might be necessary, it is more appropriate to do this as part of the main process or just before the clean-up if it is part of the final steps in the business process.

Option C (Save Workbook): Similar to Option B, this does not fit the primary use case for a Clean Up page.

Option D (Exit): While exiting might seem appropriate, it is too generic and does not convey the specific actions needed for cleaning up resources.

Reference Refer to Blue Prism's best practices and documentation on using Clean Up pages to ensure that resources are properly finalized and released at the end of a business process.

To search for Work Queue items based on tags in Blue Prism, you can use specific search strings in the Control Room:

''+Height;Tall''- This search string will return all items that have been tagged with the 'HeightTall' value. The plus sign (+) indicates that you want to include items with this tag.

''-Material;Brick''- This search string will return all items that do NOT have the 'Material Brick' tag. The minus sign (-) is used to exclude items with this tag.

When using these search strings, Blue Prism will filter the Work Queue items accordingly, showing only those that meet the specified criteria.

Reference For more detailed information on how to use tags for searching Work Queue items in Blue Prism, you can refer to the official Blue Prism documentation or instructional videos provided by Blue Prism University1

Using environment variables is a best practice in Blue Prism for managing configuration settings that may vary across different environments (e.g., Testing, Development, Training, and Production). This approach allows for easy updates and changes without modifying the underlying code.

Environment Variable: Storing the URLs in an environment variable allows you to change the URL for different environments without altering the business object or process code. This makes the automation more flexible and easier to maintain.

Other options are less optimal:

Build per URL (Option A): Creating separate objects for each URL is inefficient and increases maintenance effort.

Dynamic Match (Option B): This does not specifically address URL management.

Global Data Items (Option C): While global data items can store URLs, environment variables are more suited for managing environment-specific configurations.

Reference Refer to Blue Prism's best practices on managing environment-specific configurations using environment variables.

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.

Blue Prism Developer Documentation: Session Variables

Blue Prism Training Material on Process Execution and Variable Management

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.

Blue Prism Developer Documentation: Session Variables

Blue Prism Training Material on Process Execution and Variable Management

Understanding the Exception:

The error message indicates that the read stage 'Read Nasdaq Data' failed because it was not connected.

This suggests that the business object might not be correctly attached to the application or not launched.

Analyzing Possible Causes:

Option A: Internal errors do not always indicate a Blue Prism product problem; they can also result from configuration issues.

Option B: If the action was not published, the error would likely indicate that the action could not be found, not an attachment issue.

Option D: If the action no longer existed, the process would not be able to call it, and the error would reflect that the action was missing.

Option E: The process flow shows the stages are connected, and an unconnected stage would not specifically cause an attachment error.

Most Likely Cause:

Option C is the most likely reason. If the business object is not associated with the application (either by launching or attaching to it), the action cannot be performed because Blue Prism does not have the necessary context to interact with the application.

Blue Prism Developer Documentation: Exception Handling and Troubleshooting

Blue Prism Training Material on Application Modelling and Object Association

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.

Blue Prism Developer Documentation: Exception Handling and Retry Logic

Blue Prism Training Material on Process Flow and Exception Handling

Understanding Blue Prism Flow Representations:

Blue Prism flow diagrams represent the logic and control flow of automated processes.

Each stage must follow the rules of the process flow, and certain configurations are invalid.

Analysis of Options:

Option A: Shows a timeout leading to an Exception stage, followed by an Email Alert. This is valid as it properly handles an exception and sends an alert.

Option B: Shows a timeout leading to a Resume stage, and then directly to an Email Alert. This is invalid because a Resume stage should be followed by logic to recover from the exception, not directly proceed to another action without resolving the issue.

Option C: Shows a timeout leading to a Recover stage. This is valid as it starts the exception handling process.

Option D: Shows a timeout leading to a Resume stage, followed by an Exception stage. This is valid as it properly handles exceptions by resuming and then throwing an exception if needed.

Conclusion:

Option B is the invalid representation because it incorrectly uses a Resume stage without properly handling the exception before proceeding to the next action.

Blue Prism Developer Documentation: Exception Handling

Blue Prism Training Material on Process Flow and Error Management