UiPath Automation Solution Architect Professional v1 — Question 16
A Solutions Architect is creating the Solution Design diagram for a transactional process.
The transactions represent Invoice Numbers that should be processed sequentially in two applications, and they are received and formatted as a table, in a CSV file.
A transaction should only be processed once in each application. E.g. if a System Exception occurs after Invoice ABC was processed in Application 1, when retrying the transaction Invoice ABC should only be processed in Application 2.
The following metrics are known:
Average Transaction Handling Time = 30 seconds
Average Volume per day = 3500 transactions
Which of the following approaches is the most suitable for the process described above?
Answer options
- A. Use two REFramework projects and Dispatcher – Performer model, with the following activities used in the Performer: Get Transaction Item - Set Transaction Progress - Set Transaction Status - Set the Queue Retry = True.
- B. Use two REFramework projects and Dispatcher – Performer model, with the following activities used in the Performer: Get Transaction item - Set Transaction Status - Set the Queue Retry = True.
- C. Use a single REFramework project with Transactionitem set as DataRow and TransactionData as DataTable. Use the internal REFramework retry mechanism and a Boolean variable to determine if a specific transaction was already processed in Application 1.
- D. Use a single REFramework project with TransactionItem set as DataRow and TransactionData as DataTable. Set the Queue Retry = True.
Correct answer: C
Explanation
The correct answer is C because it utilizes a single REFramework project that can effectively track whether each transaction has already been processed in Application 1 using a Boolean variable. This ensures that transactions are not redundantly processed while maintaining the sequential processing requirement. Options A and B involve two projects which complicate the process and do not effectively handle the retry logic as required. Option D lacks the necessary tracking mechanism for processed transactions.