AD01 Blue Prism Accredited Developer Exam Questions and Answers

Using the 'Internal - Global Variables' Business Object to update the value

Using a Calculation stage in the same Process to update the value

Using the Global Variables store in Environment Manager to update the value

Using System Manager to update the value

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

Refresh a Work Queue

Create a Work Queue

Encrypt a Work Queue

Rename a Work Queue

The current configuration risks creating an infinite loop.

The current configuration is missing an intelligent Wait stage after the 'Read Result Table' stage, to ensure the Action logic has worked correctly.

There is nothing wrong with the current configuration.

The Exception Block should be removed from the page so that all exceptions on that page can be recovered.

Spy Element enables you to identify an element using their attributes, and the Navigator options are used for visible elements on the screen

Spy Element enables you to identify an element to use in the Application Modeller and the Navigator options are used for debugging when a match cannot be found

Spy Element enables you to choose from a tree of possible elements to use in the Application Modeller, and the Navigator options require you to visually find and manually select the element to identify

Spy Element enables you to manually identify an element to use in the Application Modeller, and the Navigator options displays a tree of elements available to choose from

Parent Class Name

Parent Ordinal

Class Name

Ordinal

XandY

10

9

11

The loop will be infinite

Plan

Outline

Develop

Design

4

5

1

19

The Main Page flow adheres to best practice in the basic Process Template

The exception handling does not contain any consecutive exception logic

Between the Recover and Resume stages there should be logic to reset the application ready for the next case

Exception Block should be removed as exceptions should be handled in the sub-pages

Item ID < > ""

[Customer Data] < > ""

[Customer Data] < > NULL

([Customer Data].Rows) > 0

[Item ID] < > ""

Set the Mouse Button value to Close'

The Params button must be selected and the parameter configured to override the Window Text attribute value to 'Close'

It is not possible to select the Close button using the Dynamic Button element because the value is set to 'Find in the Application Modeller

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

MakeNumber([Transaction Code]) >- 50

ToNumber([Transaction Code]) >= 50

[Transaction Code] >= 50

[Customer Transactions Transaction Code] >= 50

ToNumber([Customer Transactions Transaction Code]) >= 50

MakeNumber([Customer Transactions.Transaction Code]) >= 50

Through Control Room

Through the Digital Worker Management Console

Through System Manager

Through Process Studio

Through Object Studio

Option A

Option B

Option C

Option D

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.

The flow shown in the diagram is correct, the wart stages are all adding a high level of robustness to the action

The wait stages after read and write stages should be removed they are not required and are lowing the flow down

The wait stages after read stages should be removed, the wart stages after write stages should be left because the application will have been changed

Only the first wait stage in this flow is required, all the other wait stages should be removed.

Notes Stage

Read Stage

Write Stage

Navigate Stage

Set the Maximum Attempts parameter for the Work Queue

Rename a Work Queue

Delete items from a Work Queue

Refresh Work Queue data

Create a Work Queue

Encrypt a Work Queue

Window Text

Screen Visible

Visible

Class Name

The Retry Limit data item is set to 10 when it should always be set to 3

There is a missing Resume stage on one of the routes through the flow?

There is a missing Recover stage on one of the routes through the flow

There is nothing wrong with the current configuration

1 year will be added to todays 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 'New Dale' data item value will contain todays date

Errors Only

Enabled

Preserve Screen Capture

Disabled

The 'Calculation Result' data item value will be 25

The 'Perform Calculation' Calculation stage will throw an exception

The 'Calculation Result' data item value item will be 125

None of these statements are true

Retire the Schedule for the required period. then Unretire it

Clone the Schedule and set a new start date on the clone

Set an End Date on the Schedule, then create a new Schedule to Start after 3 months

Pause the Schedule for the required period

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.

Data Item Output = &

An Internal Exception will be thrown

Data Item Output=A

A System Exception will be thrown

Application Modeller

Object Studio

Process Studio

Application Logic area of System Manager

1 only

2 and 3

1 and 3

None

Web Text

Ordinal

Web Element Type

Match Index

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

Set the Data Item exposure to Session and update the file path every time the process starts

Use a Wildcard while specifying the file path in the Data Item to enable global search on startup

Set the Data Item exposure to Environment and store the file path as an Environment Variable

Use File Management VBO to create a logic to search for the file every time the process runs

The Username and Password Data Items contains no hard-coded credentials

The BP Portal. Go to LMS action should be inside the Login Block

There is no action to retrieve the credentials from Credential Manager

The BP Portal Launch action should have a retry loop

The specified Stop time has passed

'Request Stop received from Control Room

Priority of the remaining Queue Items is 0

All the Queue Items have been processed

Immediate Stop' received from Control Room

None of these statements are correct

If the 'Result Date' data item is configured as a Text data type, then a 'data type mismatch' Internal Exception will be thrown on execution of the Calculation stage

If the 'Result Date' data item is configured as a Date data type, then the 'Result Date' data item will be set to the date of the previous day on execution of the Calculation stage

On execution of the Calculation stage, a 'Failed to evaluate expression' Internal Exception will be thrown

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.

The correct Spy mode was used to identify elements

Application Modeller has a unique match for the screen element

Wait Stages have been used effectively

The Attach page is published in the Business Object

Disable all unnecessary stage logging to reduce the amount of data logged and stored during the runtime

Use Retry loops to handle Business Exceptions on a Work Queue Items to increase resilience in the process logic

The Process logic should include alerting mechanism to notify Process Controller(s) of any critical issues

The solution should have zero Valuation Errors to avoid failures when it is run from the Control Room

The flow will pass through calculation stage "A"

The flow will pass through calculation stage "B"

The flow will pass through calculation stage "C"

An exception will be thrown

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.

Immediately

Next time a new case is taken from a WQ

Next time resource PC starts

Next time the process starts

Keypress Stage

Navigate Stage

Action Stage

Write Stage

Use an Environment Lock in the Process, so the file cannot be accessed until the Lock is released

Ensure the Object Run Mode is set to Foreground to prevent it being am by multiple Digital Workers

Use a Blue Prism Process Template to correctly set the Process to Get Next Item from the Work Queue

Use an Environment Variable to ensure only one Digital Worker can access the environment

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

10

31

2

A run mode of background will enable the business object to run at the same time as other foreground business objects

A run mode of background will enable the business object to run at the time a other background, foreground and exclusive business objects

A run mode of exclusive cannot at the same time as any other business object

The run mode of a business object has no influence on how many business objects can be run at the same time

Use an Unconditional Wan (Throttle) to allow controllers to increase or decrease the speed of the automation as it runs

Place a Block around the Navigate stage then add a Recovery Stage Connect this to a Retry Loop which Resumes and retries that Navigate stage

Add a Sleep stage before a Conditional Wait stage with a Global Timeout value which is sufficient to accommodate the system latency

Use a Conditional Wait stage with a Global Timeout value which is sufficient to accommodate the system latency

Data Item Output Value contains “A"

Data Item Output Value contains "B"

Data Item Output Value contains "C"

An Internal Exception will be thrown

If the data item "Today" is configured with a Data Type of Text, an exception will be thrown on execution of the calculation stage

If the data item "Today" is configured with a Data Type of Date, an exception will be thrown on execution of the calculation stage

If the data item "Today" is configured with a Data Type of DateTime, an exception will be thrown on execution of the calculation stage

None of these statements are correct

An Action stage with the name 'Address Type' is being referenced but it no longer exists

An internal error always indicates a problem with the Blue Prism product. The Blue Prism support team should be contacted for assistance

A data item referenced as an input parameter in the 'Get Customer Address' Action cannot be found

Whilst debugging a Process in Process Studio, the 'Reset' button was pressed whilst the process was calling the 'Get Customer Address' action

An internal error always indicates a problem with the Blue Prism product. The Blue Prism support team should be contacted f(j assistance

The 'Get Nasdaq Data' Action is not published

The Business Object containing the Action has not been associated with the application by either launching it or attaching to it

The 'Get Nasdaq Data' Action no longer exist in the Business Object, but the Process is attempting to use it

The 'Read Nasdaq Data' stage is not connected to another stage so it cannot execute

The Exception functions are used outside the recovery mode resulting in their own exception

A Block is not used for the Recovery stage causing it to catch Exceptions from all stages on the page

An Exception stage is not used to report Exceptions causing an infinite loop in the recovery logic

The Data Item names are the same as the Exception expression resulting in their own exception