1Y0-301 · Question #147
When testing SQL Server resiliency in a SQL cluster, which two actions will trigger a failover event? (Choose two.)
The correct answer is A. Stop SQL Services. B. Turn off SQL Server. You've hit your Sonnet limit · resets Jun 1, 9am (UTC)
Question
When testing SQL Server resiliency in a SQL cluster, which two actions will trigger a failover event? (Choose two.)
Options
- AStop SQL Services.
- BTurn off SQL Server.
- CTake the SQL database offline.
- DAdd a node to the SQL Cluster.
How the community answered
(35 responses)- A91% (32)
- C6% (2)
- D3% (1)
Explanation
You've hit your Sonnet limit · resets Jun 1, 9am (UTC)
Topics
Community Discussion
6
Yusuf A.May 24, 2026The correct answers are A and B. My senior had me test this exact scenario last month, and what clicked for me is that the Windows Server Failover Cluster is constantly watching whether the SQL Server resource is healthy, so stopping the SQL service or powering off the node both look like failures to the cluster health monitor, which is exactly what kicks off the failover to the other node. Taking the database offline with option C is just a database-level operation, and the service itself is still running fine, so the cluster never sees a problem and just sits there. Adding a node like in option D is a planned administrative change, not a failure condition, so that one is out too.
Mei-Ling H.May 26, 2026Yusuf covered the main idea well, but worth being precise on option B, powering off the node, because that triggers failover through a different path than stopping the SQL service, specifically the cluster losing heartbeat contact with that node rather than the resource health check detecting a stopped service, so the mechanism is distinct even if the end result looks the same.
Mei-Ling H.May 21, 2026I saw this exact question, chose A and B, passed. Stop service or kill the server, cluster panics and moves over. C tricks you because "offline" sounds dramatic but the service still runs fine, no failover happens.
Yusuf A.May 23, 2026Exactly right, and a senior here told me to think of "offline" as just pulling a node out of rotation, the process is still heartbeating so the cluster sees nothing wrong and sits tight.
Hiroshi T.May 20, 2026Taking the SQL database offline triggers a cluster failover, per Microsoft docs.
Yusuf A.May 21, 2026Hey Hiroshi, I thought the same thing at first, but my senior clarified that taking a database offline keeps the SQL Server service itself running on the node, so the cluster health check still sees the resource as up and no failover kicks off. The triggers that actually cause a failover are A (SQL Server service failure) and B (node failure), because those are what the Windows Server Failover Cluster monitor is watching for.