The primary advantage of a decentralized database architecture over a centralized one is that it reduces the concentration of risk in a single location or single service point. Because data and processing are distributed, the effect of a single outage or denial of service event is generally reduced compared with a centralized architecture, where one core point of failure can disrupt the whole environment.
Option A is therefore the best answer. Decentralization improves resilience by avoiding total dependency on one central database or service node. In audit and risk terms, this lowers the impact of certain availability attacks or failures by distributing exposure.
Option B is incorrect because real-time synchronization over public networks is usually more difficult, not easier, in decentralized environments. Distributed synchronization introduces latency, consistency, and network management challenges.
Option C is incorrect because transaction consistency is generally harder to maintain in decentralized systems. Distributed databases often trade some degree of simplicity or immediacy of consistency for resilience, scalability, or local autonomy.
Option D is incorrect because uniform security policy enforcement is usually easier in centralized architectures, where governance and administration can be applied from a single control point.
So the correct answer is A, because the main architectural benefit of decentralization in this context is reduced single-point failure risk and reduced impact from centralized service disruption.
References (Official ISACA):
ISACA Glossary — control and architecture terminology reference.
ISACA COBIT resources — governance and resilience principles support reducing concentration risk through architectural design choices.