You're working on a banking system where financial transactions need to be securely stored and retrieved. How would you design the database schema and implement transaction management in this scenario?
- Use ACID-compliant transactions; Separate tables for accounts, transactions, users
- Implement distributed transactions across multiple servers; Use blockchain technology
- Store transactions in flat files for faster access; Use encryption for security
- Normalize tables to reduce data redundancy
Option 1 is correct. For a banking system, ACID-compliant transactions ensure data integrity, consistency, and security. Separate tables for accounts, transactions, and users allow for efficient data management and auditing. Distributed transactions and blockchain are not typically used in traditional banking systems due to complexity and regulatory concerns. Storing transactions in flat files lacks transactional integrity and is not suitable for secure financial data. While encryption is essential, it's a security measure rather than a primary transaction management method. Normalization is important but not the primary focus when dealing with financial transactions.
Loading...
Related Quiz
- How does journaling improve the reliability of a file system?
- Explain the concept of polymorphism in OOP with an example.
- What is the difference between padding and margin in CSS?
- ___________ databases are particularly suitable for storing and managing hierarchical data structures.
- What are the different types of NoSQL databases, and how do they differ from each other?