Download Full Version AD01 Blue Prism Exam

A block has not been placed around the Write stage and the Recover stage, meaning the credentials action could be unnecessarily retried if another stage further into this action throws an exception.

There is a potential for an infinite loop if the 'Credentials' stage keeps throwing an exception for some unforeseen reason.

The credentials stage is a read stage not a write stage

There is not a Resume stage following the timeout of the Wait stage

There is nothing wrong with the sub-page flow shown in this image

The sub-page process flow is missing any retry exception handling that should exist where a process calls object actions that interface with an application.

For better visibility of the process logic the flow steps shown in the image should be on the main page rather than in a sub-page of the process.

The exception stage within the flow should be removed and replaced with an End stage that returns the found data item as an output parameter.

Option A

Option B

Option C

Option D

This must be an environment issue. The Blue Prism environment must be consistent and persistent, and an element that worked one day and does not work the next day suggests the environment is changeable. The IT team supporting the environment needs to be contacted to fix the problem.

The Blue Prism product support team should be contacted to report the issue. This signifies an inconsistency in how the Blue Prism product is working which needs to be fixed.

This suggests that Best Practice exception handling has not been implemented in the object. A retry loop around the object stages that are using the element will probably fix the problem

It is common for consistency issues to be found during configuration/development testing. The most likely cause is that an attribute has been selected for the element that is changeable, such as a window title with a date, or a URL The developer needs to ensure that any changeable attributes are unticked.