ProSafe credit 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 sown below:
For each case of 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? (Choose three.)
- A . The solution is not scalable.
- B . The process does not have an end stage.
- C . The rules engine has been built in a process not an object.
- D . The process opens and closes the HotRisk system for each case.
- E . The data is too sensitive for automated processing.
- F . There is no scheduler.
MedBank have recently introduced a new Credit Card platform Cred+. There is a requirement to migrate account and card details from the existing banking platform PCBS on to Cred+.
Account IDs of the cases requiring data transfer will be held on a SQL database.
The requirement is that, for each account ID specified on the SQL database, the following data must be read from the PCBS application and input into the Cred+ application:
– Account ID
– Product Type
– Name
– Address
– Date of Birth
– Card PAN (Primary Account Number or credit card number)
– Card Issue Date
– Card Expiry Date
Once the data has been successfully input into Cred+ the correct record on the SQL database will be updated to indicate data transfer is complete. All work queues will be encrypted, however due to the sensitivity of the data, MedBank insist that a single robot account does not have access to both PCBS and CRED+ systems.
The following high level design has been proposed:
Which of the following statements about the solution design are correct? (Choose two.)
- A . If the PCBS application suffers an outage, all Blue Prism processes specified in this design must stop processing immediately.
- B . The solution enables multiple instances of the Get PCBS Data and Update Cred+ processes to run without risk of collision.
- C . There is a risk that the outcome of a data transfer will not be recorded in the SQL database.
- D . To reduce the elapsed time of the end to end process, the Get Cases process should be run across multiple machines.
- E . The Process Get PCBS Data should be stopped if the Cred+ application suffers an outage to prevent a backlog of cases in the PCBS Data work queue.
- F . Such sensitive data should not be stored in a Blue Prism work queue.
Pacific West Banking has a payments process that automatically receives pending payments from multiple regions into their payment system (Paytex).
Paytex contains a queue of cases awaiting payment. When processing the case manually an agent must use two other systems, the core banking system (DataPlus) and online account checker (FireWire).
The manual processing must perform the following steps:
– Open the next case where the status is null in Paytex
– Set the status to “In Progress” in Paytex
– Validate source account in DataPlus
– Confirm source funds in DataPlus
– Check for fraud flags in Paytex
– Confirm recipient IBAN details in Firewire
– Perform payment in Paytex
– Update case in Paytex queue. Add payment confirmation number to case and set status to “Completed”
– Where cases cannot be fulfilled due to validation errors (e.g. invalid account details, insufficient funds, suspected fraud etc.) the customers will be contacted by the agent to resolve.
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? (Choose three.)
- A . There is a risk that a payment can be duplicated.
- B . The process should not be designed to use a Blue Prism Work Queue but use Paytex as the work queue.
- C . The process will not scale i.e. you cannot run multiple instances at the same time.
- D . The solution exposes sensitive personal information.
- E . The process should not be automated as it uses a third party web application.
- F . There is a risk that a payment can be orphaned.
VivaBank have an account closure process that can take up to three days to close an account. All requests within the bank’s core system to close an account take place overnight during batch processing.
There are two scenarios:
The timings relate to the expected automation time. All requests will arrive in a Blue Prism work queue from multiple channels using either web services or other Blue Prism processes.
The following detail from the Functional Requirement Questionnaire must be considered:
– Cases must be processed on the same day if they come in between 08:00 and 22:00 Monday to Friday
– Exception cases are to be emailed to the manual team during processing as and when they occur.
– It is expected that up to 200 cases can be expected per day.
The Blue Prism solution consists of four processes and four Blue Prism Work Queues.
Cases come into the Account Closures Work Queue and are processed by the Account Closure process which determines if they are “Nil Balance” or “Balance to Transfer” scenarios. Before adding the case to the relevant work queue, a check is made to see if an identical key has been added to the work queue today. If so the case is not added. The Transfer Balance process work its queue and, for each successfully processed case, adds case to the Close Account queue. The Close Account process works its queue and, for each successfully processed case, adds a case to the Confirm Closure queue with the case deferred to 08:00 the next day.
The Confirm Closure process completes the sequence by confirming that the account is finally closed.
A scheduler has been created to start all four processes at 08:00.
Each process shall be configured to finish accordingly:
Please select from the statements below the ones you consider to be correct. (Choose two.)
- A . All processes should be merged into one process to optimize licenses.
- B . Exception cases should not be distributed whilst the processes are running and instead should be distributed when each process has completed.
- C . There should be a separate work queue for each channel feeding the process.
- D . The Confirm Closure process should work until 22:00.
- E . As an alternative the solution could use just one queue instead of four.
The following Object Design has been created for a mainframe banking application.
Which of the following statements about the Object design above are correct? (Choose two.)
- A . The Add Note action in the “BankHost C Notepad” business object does not require an input for Type as the process definition document states that ‘Information’ will always be selected for this process.
- B . The object design facilitates a scalable design that will reduce the impact of change when the object layer needs altering.
- C . The object design should be simplified by storing all BankHost actions in the same object.
- D . There is no need for attach actions to be replicated across all the objects.
- E . The design complies with Blue Prism design best practice.
Consider the following high-level design. The solution is intended to read medical data from one application in order to update another. An input file is prepared by an overnight batch run for the solution to work through each morning before patients arrive. Usually the input file is fairly small but at certain times each month the file is much larger.
Which of these options should be considered be the process solution designer to guarantee the quality of the end-to-end solution? (Choose four.)
- A . Once in production the process controller should ensure that the process is only ever run on one Resource PC.
- B . The solution should log in to the applications before starting the case working loop.
- C . The solution should split the file into pieces to distribute to each Resource PC.
- D . The solution should log out from applications after existing working loop.
- E . Each Resource PC should be set to take a different row from the others, e.g. RPC-A works rows 1, 4, 7, 10 etc., RPC-B works 2, 5, 8 etc. and RPC-C works 3, 6, 9 etc.
- F . The solution should start by loading the file data into a work queue.
- G . The file should be updated at the start of each case to prevent other RPCs from working it.
- H . Once in production the clinic should wait until the solution has completed before admitting patients.
- I . The batch run should create multiple input files so that each Resource PC has its own file to work with.
- J . The file should be updated after each case to indicate that the case has been worked.
- K . The solution should use an environment lock to ensure the file can only be accessed by one Resource PC at a time.