AD01 Blue Prism Accredited Developer Exam Questions and Answers

Update the data item exposure to 'Statistic'

Update the data item exposure to 'Environment'

Update the data item exposure to 'Session'

Update the data item exposure to 'Shared'

Option A

Option B

Option C

Option D

There is nothing wrong with the Main Page flow shown in the image, it is a copy of Blue Prism's standard Process Template.

The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.

It would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.

The exception handling in the image does not contain any concurrent exception logic. This means there is nothing stopping every item in the Work Queue being marked with the exact same System Exception.

Between the Recover and Resume stages there should be logic to reset the application ready for the next case to be worked For example, this could call the Close Down and Start Up pages.

The process will work all stages in the "Access Customer Account page until the error is thrown and then focus would move to the breakpoint at "Get Customer Details" stage.

The process will work all stages in the 'Access Customer Account1 page until the error is thrown and then focus would move to the "Recover 1 stage

The process will work all stages in the "Access Customer Account' page until the error is thrown and then focus would move to the stage containing the error on the "Access Customer Account" page,

The process will work all stages in the "Access Customer Account" page until the error is thrown and then focus would move to the "Exception 1 stage.

1,2, 3 and 4

3 only

4 only

2 and 4

A Blue Prism work queue is not required for simple linear processes that do not work multiple cases.

A Blue Prism work queue should always be used. It eliminates the risk of contention and allows you to gracefully pause the queue at any time.

A Blue Prism work queue is not required if the business process interfaces with a Work List system with in-built capability to ensure multiple users cannot work the same case at the same time

A Blue Prism Work Queue decreases the scalability of the solution and therefore should only be used for complex scenarios such as multi-day processing.

5 days will be added to today's date and the result stored in the New Date data item.

1 month will be added to today's date and the result stored in the New Date data item.

1 week will be added to today's date and the result stored in the New Date data item.

The process will throw an exception as the New Date data item is null.

The diagram will flow through the Calculation stage named 'A'

The diagram will flow through the Calculation stage named 'B'

The diagram will flow to the Exception stage which will raise a new exception

The diagram will flow through the Calculation stage named 'C

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.

There just needs to be a wait stage after the start stage to correct this action.

There should be a wait stage after every stage in this flow (i.e. after the navigate, read, write stages.

If during testing in object studio this flow works, no additional wait stages should be added as they will slow the interface down.

There should be an intelligent wait stage after the start stage and after any stage that cause the application we are interfacing with to change