AD01 Practice Exam Questions with Answers Blue Prism Accredited Developer Exam Certification

An Internal Exception: 'Loop stage name mismatch' will be thrown

10

31

2

1

Unlimited

10

999

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.

Control Room allows filtering of the displayed queue items using exact tags and by using wildcards

Wildcards are not allowed in the Tag Fitter property of the Work Queues business object Get Next Item action

Work Queue item Status can only be set to Completed or Exception

Tags can be used allow flexibility in the order items are worked within a single Work Queue

Data Item Output Value contains “A"

Data Item Output Value contains "B"

Data Item Output Value contains "C"

An Internal Exception will be thrown

All development and testing MUST be done using the production site. This is because the test and training websites might not mirror production exactly.

A local text file should be used to easily configure the details of the HappyWeb website to be used in each Blue Prism environment.

An Environment variable should be used to store the HappyWeb URL.

Three different versions of object that launches the HappyWeb website will need to be created and maintained, one for each environment.

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 Stop? decision stage should be removed from the process flow, as Stop time is Configured either within the Scheduler process are stopped via Control Room.

The Mam Page process flow is too high level For better visibility of the process logic the flow steps hidden m the sub-pages should al be on the main page instead.

There is no exception handling on this Main Page so any exceptions that "bubble up" will cause the process to terminate rather than exceptions being handled correctly.

The Reset Global Data page is not required because sub-page within a process should always use input parameter rather than global data items. There should be no global data to reset.

Update the 'Mouse Button' Inputs value to "ORDERS1

Using the Params button to open the Application Element Parameters window, the Window Text match value must be set to "ORDERS"

A new element is required with the Window Text value set to 'Orders' and the Match Type set to equal

The ORDERS button cannot be clicked using this Dynamic button element, because the Window Text attribute value in Application Modeller is set as EXIT

The Process will continue to the Resume 1 Stage

The Error will cause the Process to terminate

The Error will be recovered in the Recover2 Stage

The Error will cause the Process to jump to the End Stage

There is nothing wrong with this flow.

The exception handling in this flow can be removed because an Attach action in a navigate stage should always work if configured correctly

The Attach Block should be enlarged to also include the Waited Long Enough decision stage.

The flow contains a recover stage and a route from it without a resume stage. This will cause internal errors on future exceptions thrown in the same session.

The 0.5 second wait stage should be removed so that the retries can be performed at full speed.