Question 49

A distributed database is suitable for high availability during outages.

A distributed database is designed to ensure that data remains accessible even in the event of local or regional outages. This architecture allows data to be stored across multiple locations, providing redundancy and fault tolerance.

A) Flat-file

A flat-file database lacks the complexity and redundancy needed for high availability. It stores data in a single file, making it vulnerable to loss or downtime if the file becomes corrupted or if the storage location fails.

B) Cloud

While cloud databases can offer high availability, they are not inherently designed for this purpose alone. The availability depends on the specific cloud architecture and provider; thus, it may not guarantee access during all types of outages without additional configurations.

C) Relational

Relational databases can be implemented to provide high availability, but by themselves, they do not ensure data is distributed across multiple sites. Their traditional structure often relies on a central server, which can be a single point of failure if not supported by a distributed system.

D) Distributed

A distributed database is explicitly designed for high availability, as it replicates data across various locations. This architecture allows the system to continue functioning seamlessly even if one or more nodes become unavailable due to outages.

Conclusion

The distributed database is the definitive choice for ensuring high availability during outages, as it inherently provides redundancy and fault tolerance by storing data in multiple locations. In contrast, flat-file, cloud, and relational databases lack the necessary frameworks to guarantee the same level of accessibility during local or regional failures.