Blue Prism AD01 Dumps PDF Free Download - Page: 7

QUESTION: 31

Refer to the exhibit.

What is wrong with the flow shown in the image?

Sub-pages should not have retry logic, exception handling should be in the object level rather than in the process.
The resume stage must also be within the exception block
The retry loop logic does not include any navigation after the resume stage to ensure the application is ready to try the 'Search Screen -Perform Search' action again.
The retry loop logic shown in the image is incorrect because it uses multiple action stages. There should be a retry loop around every action.

Answer(s): C

Explanation:

As per the process template the resume there should be another action or page after the resume stage.

Reveal Solution Next Question

QUESTION: 32

Which of the following flows can you not create in Blue Prism? (select 2 responses) A)

B)

C)

D)

Option A
Option B
Option C
Option D

Answer(s): A,B

Reveal Solution Next Question

QUESTION: 33

Study the following image showing pan: of the flow within a process:

What problems do you see with the process flow? (select 2 responses)

There is a missing Recover stage on one of the routes through the flow.
There is a missing Resume stage on one of the routes through the flow.
The Retry Count is not being incremented for each retry.
If an exception is thrown in the Cancel Reservation page and is allowed to bubble up to be caught by the Recover stage, the Create Reservation action won't be retried.

Answer(s): C,D

Reveal Solution Next Question

QUESTION: 34

Look at this flow diagram from the Main Page of a process in Process Studio:

Thinking about the standard Blue Prism Process Templates, what is wrong with how this Mam Page is handling exceptions?

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.

Answer(s): A

Reveal Solution Next Question

Consider the following flow within an Object Studio action:

The developer of this flow found that writing some credentials to the target application sometimes failed with an exception even though the element exists on the screen. He found that simply catching the exception, waiting for 2 seconds and then retrying fixed the problem.
What problems do you see within the flow? (select 2 responses)

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

Answer(s): A,B

Reveal Solution Next Question

Blue Prism Accredited Developer AD01 Dumps in PDF

Free Blue Prism AD01 Real Questions (page: 7)

QUESTION: 31

Explanation:

QUESTION: 32

QUESTION: 33

QUESTION: 34

QUESTION: 35