For the database layer, which configuration ensures only one database server is used at a time while sharing data and configurations?

For the database layer, which configuration ensures only one database server is used at a time while sharing data and configurations?

• A. Active-active cluster
• B. Active-passive cluster
• C. Shared-disk failover
• D. Distributed read-write cluster

Answer: (B)

The main idea here is having a single database server actively handling requests at any moment, with other servers ready to take over if that active node fails. An active-passive cluster does exactly this: one primary database instance is actively used, while one or more standby instances share the same data and configuration and stay synchronized so they can quickly assume control. This setup keeps data consistency simple because only the active server performs writes, and failover to the standby preserves ongoing access with minimal downtime. In contrast, an active-active arrangement would have multiple database servers processing writes at the same time, which can complicate data consistency and conflict resolution. A shared-disk failover describes how storage is shared rather than how database access is managed, and a distributed read-write cluster implies distributing writes across nodes, which contradicts the requirement that only one database server is used at a time.

The main idea here is having a single database server actively handling requests at any moment, with other servers ready to take over if that active node fails. An active-passive cluster does exactly this: one primary database instance is actively used, while one or more standby instances share the same data and configuration and stay synchronized so they can quickly assume control. This setup keeps data consistency simple because only the active server performs writes, and failover to the standby preserves ongoing access with minimal downtime.

In contrast, an active-active arrangement would have multiple database servers processing writes at the same time, which can complicate data consistency and conflict resolution. A shared-disk failover describes how storage is shared rather than how database access is managed, and a distributed read-write cluster implies distributing writes across nodes, which contradicts the requirement that only one database server is used at a time.