A company wants to store monetary transaction logs in a way that remains tamper-resistant after insertion. Which approach best accomplishes this by linking each record to the previous one through cryptographic references?
Use a ledger system where each record includes the hash of the prior entry
Implement nested encryption algorithms on archived dumps for every monthly cycle
Store logs on multiple servers, rotating files in daily intervals
Create a relational table with read-only permissions that limits changes to existing rows
The correct option uses a sequence of items in which each one contains a cryptographic link to its predecessor. Changing any earlier entry disrupts the chain's integrity. Conventional read-only or append-only approaches do not employ a cryptographic mechanism to detect unauthorized modifications. Regular encryption routines also do not ensure that historical data remains verifiably unmodified over time.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a ledger system and why is it tamper-resistant?
Open an interactive chat with Bash
How does including a hash of the prior entry enhance security?
Open an interactive chat with Bash
Why are traditional methods like read-only or encryption insufficient for tamper resistance?