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:
Answer : ADF
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:
Answer : BE
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.
Answer : BCD
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:
Answer : CD
The following Object Design has been created for a mainframe banking application.
Answer : BE
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.
Answer : BEGH
Consider the following high-level design.
Answer : ABC
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.
Answer : C
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.)
Answer : BE
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.
It is imperative that notes are applied to System X and Y, regardless of whether System Z is updated or not, what could the process do? (Choose two.)
Answer : AD
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? (Choose two.)
Answer : AB
When designing business objects which of the following statements is true? (Choose three.)
Answer : ADF
You are the Lead Developer tasked with delivering four processes for the same client. You have enough developers in the team to develop all the processes in parallel. All the processes have one application in common, another application is used by two processes and one process uses an application that none of the others do.
Which of the following statements is true?
Answer : C
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?
Answer : C
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? (Choose three.)
Answer : BDE
Have any questions or issues ? Please dont hesitate to contact us