Q: 3
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might
have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You have a failover cluster named Cluster1 that hosts an application named App1.
The General tab in App1 Properties is shown in the General exhibit. (Click the General tab.)
The Failover tab in App1 Properties is shown in the Failover exhibit. (Click the Failover tab.)
Server1 shuts down unexpectedly.
You need to ensure that when you start Server1, App1 continues to run on Server2.
Solution: From the Failover settings, you select Prevent failback.
Does this meet the goal?
The Failover tab in App1 Properties is shown in the Failover exhibit. (Click the Failover tab.)
Server1 shuts down unexpectedly.
You need to ensure that when you start Server1, App1 continues to run on Server2.
Solution: From the Failover settings, you select Prevent failback.
Does this meet the goal?Options
Discussion
Its A, seen similar questions in official practice tests and docs. Prevent failback leaves App1 running on Server2 after Server1 recovers.
Had something like this in a mock exam. It's A since choosing Prevent failback means App1 stays on Server2 even when Server1 comes back online. This avoids unnecessary movement of the resource and minimizes potential downtime or disruption. Pretty sure that's what they want here, but let me know if I'm missing anything.
Its A. Prevent failback keeps App1 on Server2 even after Server1 is back up.
Be respectful. No spam.
