HUAWEI CLOUD database HySQL supports cross-AZ high availability. If the main database fails, it will start fault detection three times and pull it up. If it cannot be pulled up, it will…

Question

Options

• ATrue
• BFalse

• A
  80% (37)
• B
  20% (9)

Explanation

Option A is correct because HUAWEI CLOUD HySQL is designed with cross-AZ high availability that follows exactly this sequence: when the primary database becomes unavailable, the system performs three fault detection attempts and tries to restart it before escalating to a failover. This staged approach (detect, attempt recovery, then failover) is a standard HA pattern that minimizes unnecessary switchovers caused by transient failures. Option B is incorrect because it would imply the described behavior is inaccurate, but this sequence -- three detection rounds, automatic promotion of the standby, and reattachment of read-only instances to the new primary -- is precisely how HySQL's cross-AZ HA mechanism works. The key detail about read-only instances being automatically rehung under the new master is important: it ensures that read traffic is not disrupted after a failover without manual intervention.

Memory tip: Remember the number three -- HySQL tries three times before giving up and promoting the standby. Think of it as "three strikes and you're out" for the primary database, after which the standby steps up and read-only nodes follow automatically.

No community discussion yet for this question.