Can You Design a Ledger?

10 Advanced Questions on Financial Ledger Architecture

1 / 10

You are reviewing a proposed ledger architecture. The team says, “We’ll choose PostgreSQL vs. NoSQL first and define the ledger semantics afterward.” What should you challenge first?

2 / 10

A ledger entry has both a business-effective date and a database insertion timestamp. Why might the distinction matter?

3 / 10

Your internal ledger shows $10,000 of settled payments, while an external settlement file shows $9,800. What should happen?

4 / 10

A balance projection becomes corrupted after a software deployment. What should the architecture ideally allow?

5 / 10

Your ledger contains 20 billion entries. The system needs to return an account’s current balance in milliseconds. Which architecture is strongest?

6 / 10

A posted $1,000 ledger transaction is discovered to be incorrect. What is generally the safest correction model?

7 / 10

A client retries the same transfer after a timeout. The first request may already have committed, but the client doesn’t know. What is the strongest design?

8 / 10

Two withdrawals of $80 arrive concurrently against an account with $100 available. Both requests independently observe the $100 balance. What must the ledger architecture guarantee?

9 / 10

A transfer of $500 moves value from Account A to Account B. Which invariant must hold for the ledger transaction to be valid?

10 / 10

What should be the authoritative representation of a posted financial transaction?

Your score is

The average score is 0%

0%