Question

Lets assume we are writing a system to backup a list of transactions: class Transaction 1 String TransactioniD: Date TranactionTime: Account account: enum Type(ADD, EDIT, ADMIN): Type type: Transactions are constantly added to the system as quickly as possible (hundreds a minute) and occasionally, your system will need to retrieve them but only if there is a error with the main system (once or twice per million transactions). Additionally, transactions may not come in order as some transactions take longer to process. What is the best way to store the transactions in your system? a) as a list sorted by transactionID b) As an unsorted list of transactions c) as a list sorted by transaction Time d) As a list sorted by a new systemiD int since they transactions are not coming into our system in order of time. Activate Windows Go to Settings to activate Windo e) As a 2d list with the columns sorted by Account and the rows sorted by date

Answer 1

The answer is "Option d"

Step-by-step explanation:

In this question, the easiest way that will save the payment on your database in such a process ID-sorting list would be to mark a payment, that's been recorded mostly on the database whenever this payment became used serial number is not transaction ID, and the wrong choice can be defined as follows:

• In choice a, It is wrong because it may be processed, however, payments aren't entered through our process, which does not help remove older.
• In choice b, the unordered list would not enable any transaction to only be retrieved, that's why it is wrong.
• In choice c, it will not be helpful because the includes video is either begin or complete the payment, it will not be helpful to hold it with transaction time.
• In choice e, this approach won't help to identify the payments since one date will have a lot of payments over a certain account.