Administering Microsoft SQL Server 2012 Databases: Clustering and AlwaysOn
- 7/15/2012
Answers
This section contains the answers to the lesson review questions and solutions to the case scenarios in this chapter.
Lesson 1
Correct Answer: C
Incorrect: Windows 7 Enterprise edition cannot be used as the host operating system for a multi-site failover cluster instance.
Incorrect: Windows Server 2008 Enterprise edition does support failover clustering but does not support multi-site failover clusters.
Correct: Windows Server 2008 R2 Enterprise edition supports multi-site failover clustering.
Incorrect: Windows Vista Ultimate edition cannot be used as the host operating system for a multi-site failover cluster instance.
Correct Answer: A
Correct: The Move-ClusterGroup cmdlet enables you to move a clustered service or application from one node to another in a failover cluster. You can use this cmdlet to perform manual failover of a SQL Server clustered instance from one node to another.
Incorrect: The Move-ClusterResource cmdlet enables you to move a clustered resource from one clustered application to another but not to move a clustered service or application from one node to another.
Incorrect: The Move-ClusteredSharedVolume cmdlet enables you to move the ownership of a clustered shared volume from one node to another. You cannot use this cmdlet to perform failover on a SQL Server clustered instance.
Incorrect: The Move-ClusterVirtualMachineRole cmdlet enables you to move a clustered virtual machine to a different cluster node. You cannot use this cmdlet to perform failover on a SQL Server clustered instance.
Correct Answer: A
Correct: You should evict the failed node. After this is done, you can repair the server, join it back to the cluster, and then reinstall SQL Server.
Incorrect: You should not evict the new primary node; you should instead evict the failed node from the cluster.
Incorrect: You should not reinstall SQL Server on the failed node until you have evicted the node, repaired the failure, and joined the node back to the cluster.
Incorrect: You should not join the failed node back to the cluster until you have evicted and repaired the node.
Correct Answers: A, B, and D
Correct: You must run advanced cluster preparation on all nodes that will participate in the failover cluster instance.
Correct: You must run advanced cluster preparation on all nodes that will participate in the failover cluster instance.
Incorrect: You run advanced cluster completion only on the node that has control of the shared disk resource. Because SQL-B has control of this resource, you should not run this process on SYD-A.
Correct: You run advanced cluster completion only on the node that has control of the shared disk resource.
Lesson 2
Correct Answer: C
Incorrect: You can enable AlwaysOn Availability Groups by using either SQL Server Configuration Manager or PowerShell. You cannot perform this task by using SQL Server Management Studio.
Incorrect: You can enable AlwaysOn Availability Groups by using either SQL Server Configuration Manager or PowerShell. You cannot perform this task by using SQL Server Installation Center.
Correct: You can enable AlwaysOn Availability Groups by using either SQL Server Configuration Manager or PowerShell.
Incorrect: You can enable AlwaysOn Availability Groups by using either SQL Server Configuration Manager or PowerShell. You cannot perform this task by using SQL Server Data Tools.
Correct Answer: A
Correct: You use the Switch-SqlAvailabilityGroup cmdlet to perform manual availability group failover.
Incorrect: You use the New-SqlHadrEndpoint cmdlet to create a mirroring endpoint for AlwaysOn Availability Groups. You use the Switch-SqlAvailabilityGroup cmdlet to perform manual availability group failover.
Incorrect: You use the New-SqlAvailabilityGroupListener cmdlet to create a new availability group listener. You use the Switch-SqlAvailabilityGroup cmdlet to perform manual availability group failover.
Incorrect: You use the Enable-SqlAlwaysOn cmdlet to enable AlwaysOn on an instance. You use the Switch-SqlAvailabilityGroup cmdlet to perform manual availability group failover.
Correct Answer: D
Incorrect: You use the New-SqlAvailabilityGroupListener cmdlet to create a new availability group listener.
Incorrect: You use the Switch-SqlAvailabilityGroup cmdlet to perform manual availability group failover.
Incorrect: You use the Enable-SqlAlwaysOn cmdlet to enable AlwaysOn on an instance.
Correct: You use the New-SqlHadrEndpoint cmdlet to create a mirroring endpoint for AlwaysOn Availability Groups.
Correct Answers: B and D
Incorrect: To support automatic failover to any available secondary replica, all replicas must use synchronous-commit mode. Automatic failover cannot occur if the primary replica uses asynchronous-commit mode.
Correct: To support automatic failover to any available secondary replica, all replicas must use synchronous-commit mode. Automatic failover cannot occur if the primary replica uses asynchronous-commit mode.
Incorrect: To support automatic failover to any available secondary replica, all replicas must use synchronous-commit mode. Automatic failover cannot occur if the primary replica uses asynchronous-commit mode.
Correct: To support automatic failover to any available secondary replica, all replicas must use synchronous-commit mode. Automatic failover cannot occur if the primary replica uses asynchronous-commit mode.
Case Scenario 1
You must deploy SQL Server 2012 Enterprise edition to support the proposed cluster configuration because this is the only edition that supports four nodes.
You must support multi-subnet failover clustering, which requires either Windows Server 2008 R2 Enterprise or Datacenter editions. Windows Server 2008 does not support multi-subnet failover clustering.
You can use either the Failover Cluster manager or the Move-ClusterGroup PowerShell cmdlet to perform manual failover.
Case Scenario 2
You can use the Enterprise or Datacenter editions of Windows Server 2008 R2 to support the proposed configuration.
Because the SQL Server service uses local accounts, you must use certificate-based authentication for the endpoints.
You must configure the synchronous-commit availability mode, given the requirement for automatic failover.