Online Access Free ASD01 Practice Test
| Exam Code: | ASD01 |
| Exam Name: | Designing Blue Prism Process Solutions (EN) |
| Certification Provider: | Blue Prism |
| Free Question Number: | 30 |
| Posted: | Jul 16, 2026 |
It's technically possible for one business object to call another. Outside of using utility objects are any of the following valid reasons why you would want to do this?
Consider the following steps for a theoretical manual process.
* Check in input folder 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 System 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 System 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 possible that there are long intervals between files arriving, what are the alternatives the process should take to control System X, System Y and System Z? (Choose two.)
Which of the following statements about using Work Queue designs to split a business process into a multi part robotic solution is correct?
1. Using multiple Work Queues and Processes for the different stages of the business process is a valid design option to split a business process into a multi part robotic solution.
2. Using a single Work Queue and deferring cases for future processing is a valid design option to split a business process into a multi part robotic solution.
3. Using an item's status to control when to work it is a valid design option to split a business process into a multi part robotic solution.
4. You cannot split a business process into a multi part robotic solution.
A process is required for a telecoms company to work cases supplied via a daily Excel file. Although the file will only contain around 1000 rows, the average case time is such that the workload is far too big for one machine to complete in a day, so the solution has been designed with multiple machines in mind. One machine will load the work queue while the others wait, then once the queue is ready all machines will work it together.
The requirements state that the input file is machine generated, has a known format, is generally clean but may contain exceptions - rows with an empty cell, partial phone numbers, or accounts that don't exist.
What should the solution do to combat this problem?