You have a Windows Server 2016 failover cluster that contains two servers named Server1 and Server2. The Cluster Service on Server1 fails. You need to identify the cause of the failure. What should you do?
A.
From Windows PowerShell, run the Get-ClusterNode cmdlet.
B.
From Event Viewer, review the Application event log.
C.
From Windows PowerShell, run the Get-ClusterLog cmdlet.
D.
From Event Viewer, review the System event log.
The answer is correct. And surprisingly, Coleman is wrong. A lot of good sources being posted, but surprisingly not being read thoroughly. The Get-ClusterLog cmdlet not only grabs the Cluster logs off every node, and gives you the ability to dictate where to save them and for what period of time, but also, by default, also grabs the System and other log channels! The only thing that failed in that node is the service in question. Server itself is still functional, beware the red herrings.
Remember that real-life scenarios are not exactly what this test is testing you on. It's testing you on the knowledge of a Microsoft Product: Microsoft Server 2016. Yes, you can first take a look at the System log and check out what happened there, maybe. But they want you to understand that the Get-ClusterLog command is now IMPROVED in Server 2016 to INCLUDE those system logs for you in addition to the grotesquely detailed Cluster logs.
Read towards the bottom on this reference, look for "Events from other channels" : https://techcommunity.microsoft.com/t5/failover-clustering/windows-server-2016-failover-cluster-troubleshooting/ba-p/372005
Always go the System event log first, when troubleshooting an issue, right?. Failover clusters post events in the System event log that are oftern enough to understand the nature and scope of the problem. This also gives you the specific data/time of the prob, which is useful if you do look at other event logs or dig into the cluster.log if needed.
However, bc the question states that the cluster service on SV1 fails only, you use Get-ClusterLog to generate the cluster.log on each server that is a member of the cluster and is currently running.
==> C is correct ans
from https://techcommunity.microsoft.com/t5/failover-clustering/windows-server-2016-failover-cluster-troubleshooting/ba-p/372005 :
Tip: Always go to the System event log first, when troubleshooting an issue. Failover cluster posts events in the System event log that are often enough to understand the nature and scope of the problem. It also gives you the specific date/time of the problem, which is useful if you do look at other event logs or dig into the cluster.log if needed.
Generating the Cluster.log
I think the answer is correct bcos:
Get-ClusterLog is the Windows PowerShell cmdlet that will generate the cluster.log on EACH server that is a member of the cluster. Unfortunately, Server1 needs to be currently running to generate the log. The statement says only the cluster service has fail....
I'm sorry to say, but i genuine think you are wrong, when consulting the page you name, there you can see, that they use PowerShell with Get-ClusterLog cmdlet.
Correct answer is C.
I think the answer is D.
The "Get-ClusterLog" cmdlet returns only these information, which does not provide the "Cause of the failure" and not useful.
The "System" event log provides details about cluster , disk and network information which may provide clues to identify the cause of a server failure.
upvoted 2 times
...
This section is not available anymore. Please use the main Exam Page.70-740 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
JBSPLAT
4 years, 7 months agotchau
5 years, 2 months agononoelptirobo
4 years, 11 months agolbs
5 years, 2 months agomvdb87
5 years, 6 months agoDhelailla
5 years, 4 months agocoleman
5 years, 8 months ago