Which statement is true about using Microsoft Windows Cluster as a platform for MySQL?

Question

Options

• AIt relies on the shared disk architecture being visible to both servers.
• BIt is provided by means of IP-level disk replication.
• CIt implements High Availability by using the NET Connector's load balancing capabilities.
• DIt is a shared-nothing architecture.

• A
  90% (46)
• B
  2% (1)
• C
  2% (1)
• D
  6% (3)

Explanation

Microsoft Windows Server Failover Clustering uses a shared disk architecture, where both cluster nodes have visibility to the same physical storage (typically a SAN), but only the active node accesses it at any given time - when that node fails, the passive node takes over using the same shared disk. This is precisely what option A describes.

Why the distractors are wrong:

• B describes DRBD-style IP-level block replication, which is a Linux-based HA solution (not Windows Cluster), and is actually closer to how MySQL Replication or DRBD works.
• C confuses two unrelated features - the .NET Connector's load balancing is a client-side connection feature and plays no role in cluster-level High Availability.
• D describes MySQL NDB Cluster, which genuinely is a shared-nothing architecture - this is the most common trap, since "MySQL Cluster" and "Windows Cluster for MySQL" sound similar but are fundamentally different technologies.

Memory tip: Pair the opposites - Windows Failover Cluster = shared disk; MySQL NDB Cluster = shared nothing. If you remember that one pair, you can eliminate both B and C as irrelevant mechanisms, leaving A as the only accurate description.

No community discussion yet for this question.