Blue Prism ASD01 Test Dumps

The status of a Work Queue can be used as a method of recording what work has been done so far on a Work
Queue item
Please consider the following statements:
1. For Ml, to easily see how far an item has been worked
2 To aid manual working of exceptions, providing the Item Status can inform staff what work is still
outstanding on an item that needs manually completing
3. To enable Work Queue items to be safely retried, a process can use the item status to know which updates
have already been performed so that they are not repeated
4 To record the Customer's Surname
Which of the statements are valid reasons for updating a case status?

ProSafe credil reference agency retrieves data from bank and other credit providers where customers have
missed payments or gone into default. The data is very sensitive and fed directly into a Blue Prism work queue
via a web service. Blue Prism process must process the data within 4 hours. The Blue Prism solution runs
continuously and each case takes approximately 30 seconds to process. It is expected that an average of 10,000
cases per day will be required and up to 10 Blue Prism robots are available. The Blue Prism solution is shown
below:

For each case the process will access the customer account in the HotRisk system and, where an account
exists, harvest the data which will be fed along with the Work Queue data into a rules engine. The rules engine
is a Blue Prism process that does not interact with any target system. It merely consumes data and. via a
complicated series of decision and choice stages, determines the new customer risk factor.
There is to be no scheduler used. Instead the Process Controllers who work in shifts to provide 24 hour support
will stop and start process instances in line with Work Queue volumes.
As a Blue Prism process solution designer, who is reviewing the solution, which of the following would
concern you? (select 3 responses)

The following Object Design has been created for a mainframe banking application

Which of the following statements about the Object design above are correct? (select 2 responses)

A process is required for a client in the banking sector that involves using an application to transfer funds
between accounts A strong security model is in place to prevent any malicious activity but the client is nervous
about the risk of external problems, like a power cut leaving a case in an incomplete state or a fault in the
source data causing a case to be duplicated or an excessively large transfer to be made.
What should be included in the solution design? (select 3 responses)

Imagine you are designing the application integration logic for a solution. One of the applications involved is
one you have not automated before but it is widely used and the project is the first in a series for this client. Which of the following are valid considerations when designing business objects? (select 2 responses)

Consider the following high-level design:

The application concerned is prone to being sluggish or even unresponsive at times. As the solution designer
you should anticipate that there will be system exceptions and that after an exception case the application
might not be in arNdea1 state. What should you do? (select 3 responses).

A process definition document has been produced for a process that interfaces with two applications FirstApp
and Customer Information (CI) The
process requirement is to perform data extraction from FirstApp before performing a number of steps in the CI
application.
It is estimated that to perform the daily case volume within SLA's will require 10 robots Average license time
is approximately 10 minutes, with the
FirstApp steps requiring only 1 minute to perform.
The client has a limited number of licences for the FirstApp application and is reluctant to use 10 of these
licenses to automate the process.
Which of the below is a valid design option for the project?

When designing business objects which of the following statements is true? (select 3 responses)?

Consider the following steps for a theoretical manual process
• Check in input folder for any new files.
• If there are no files check again later as files can arrive anytime, and there is no limit to the number of files
that may come
• Open the next available file.
• Take the first case
• Start System X and find the case details.
• If the case can't be found., move to the next one.
• After finding the case in System X. fetch additional case details from System Y.
• Again if the case can't be found, move to the next one.
• Analyse all the data to see if System Z should be updated
• If the data does not meet the requirements, add notes indicating this to Systems X and Y and move to the
next case
• If the data does meet the requirements, update the case in System Z
• Add notes to Systems X and Y and move to the next case.
• At the end of the file, go back and look for another
• Stop checking for new files at 16:00 and finish any remaining cases.
• When all work is complete create a report of the day's exception cases.
• Close down Systems X, Y and Z.
If it is imperative that notes are applied to System X and Y, regardless of whether System 2 is updated or not,
what could the process do? (select 2 responses)

A proposed Blue Prism solution with the following properties has been created to automate the payment
processing:
• There will be one Blue Prism process that will perform the steps described above.
• Where a case is an exception the status will be set in Paytex to "Manual Review" in order that the manual
team can pick up the case from Paytex and contact the customer and conclude the case.
• It is anticipated that to meet the SLAs of the expected volumes up to 5 instances of the Blue Prism process
will be required to run concurrently.
• A Blue Prism work queue will be used to host the payments. The queue will be configured for only 1 attempt
per case and the key will be {region} & {source account number}.
• The process will be started by the scheduler at 06:00 and will stop at 05:50

Which of the following are correct? (select 3 responses).
There is a risk that a payment can be duplicated.