Server Pro 2016 - Chapter 15

After changing ISPs, you discover that the rate of failover increases. You suspect this may be due to latency on the new WAN link.

Increase the CrossSubnetThreshold on Cluster1.

You need to prepare the environment to create a network load balancing cluster to provide high availability for the intranet web site.

Reserve an unused valid IP address on the network to be assigned to the NLB cluster. Create an A record in DNS that maps intranet.corpnet.com to the IP address reserved for the NLB cluster.

Which solution can you use to minimize downtime for nodes during the application of updates?

Run the Add-CauClusterRole cmdlet.

How can you enable AcctRecv to run in Cluster1?

Run the Add-ClusterGenericApplicationRole cmdlet

Management would like to use SSL to secure the intranet website. During the test phase, only web1 will service ssl request. You have installed a certificate on the web1 server and modified the bindings in IIS. You need to configure network load balancing to ensure that only web1 server services ssl requests for the intranet website. What should you do? (choose three.)

Set the affinity for the new port rule to single host. On the web1 server, set the handling priority for the new port rule to 1. Create a new port rule that runs from port 443 to port 443.

Select the boxes in this dialog that must be enabled to allow failover cluster manager to monitor...

(select) virtual machine monitoring (bot)

Click the virtual machine option you would use in hyper-v manager to accomplish this task.

(Select) replication (bot)

Which replication type should be used between FS11 and FS12?

Asynchronous

After configuring the NLB cluster, you determine that the web servers in the cluster are unable to communicate with each other.

Change the cluster operation mode to multicast.

-NIC1 connects the server to the main network. clients connect to the cluster through NIC1. -NIC2 connects the server to the storage area network (SAN). the SAN is used only for access to the storage. -NIC3 is a private network used only by srv1 and srv2 for sending out heartbeat signals and performing convergence.

Choose Do not allow the cluster to use this network.

Drag the load balancing term on the left to the appropriate description on the right.

Con Heart Multi Uni

Srv1 should be the primary server used to respond to DHCP requests. if srv1 is unavailable, srv2 should take over the DHCP service. Once srv1 comes back online, the DHCP service should continue to run on Srv2 unless manually moved.

Configure srv1 and srv2 as possible owners. Configure srv1 as the preferred owner. disable failback.

-DHCP-Srv1 should continue to respond to all client requests. -If DHCP-Srv1 is down, DHCP-srv2 should be able to respond to clients. DHCP-srv2 should be aware of all leases granted by DHCP-srv1. -following a failure, when dhcp-srv1 comes back online, it should resume responding to all dhcp requests.

Configure DHCP-srv1 and DHCP-srv2 in a failover clustering cluster.

Client computers use several proxy servers to connect to the NLB cluster. You would like client connections to be directed to a cluster node based on the class c subnet address.

Configure a port rule with the filtering mode set to multiple host. configure network for the client affinity.

You want the cluster to keep operating even in the event of a failure of up to three of the nodes. if more than three nodes fail, the cluster should stop.

Configure a witness disk. Use node and disk majority for the quorum mode.

The WAN link between the main office and the branch office has occasional issues with latency, especially during normal business hours.

Configure asynchronous replication between the main office site and the branch office site. increase the crosssubnetthreshold value

-All client requests should be directed to SRv5 if it is available. -if srv5 goes down, all requests should be directed to the new server. -Both servers should use the same set of data files.

Configure both servers clustering cluster. Configure a storage area network for the application data.

-Client requests should be divided evenly between the two server. -If one server goes down, all requests should go to the other server. -All application data will be stored on internal parallel SCSI drives on each server.

Configure both servers in a Network Load Balancing (NLB) cluster.

-All client requests should be directed to srv5 if it is available. -If srv6 goes down, all requests should be directed to the new server. -Both servers should use the same set of data files.

Configure both servers in a failover clustering cluster. Configure a storage area network for the application data.

-new client requests should be directed to either of the two servers. -Because of differences in hardware between the two servers, two-thirds of the client requests should be directed to Srv5, with the remaining going to the new server. -If one server goes down, all requests should go to the other server. -If the same client computer creates multiple sessions at the same time, all sessions should be created on the same server.

Configure both servers in a network load balancing (NLB) cluster. Configure a port rule with client affinity set to Single.

-All client requests should be directed to Srv5 if it is available -If srv5 goes down, all requests should be directed to the new server. -Both servers should have a seperate copy of the website data. Website content will be managed seperately on each server.

Configure both servers with a static IP address. Configure both servers in a network load balancing (NLB) cluster. Configure a port rule with the filtering mode set to Single host. Configure srv5 with a handling priority of 1 and srv10 with a handling priority of 2.

-All client requests should be divided between both servers. -If either server goes down, client requests should be redirected to the other server. -If the application stops but the server is up, the server should automatically try to restart the application to make it available.

Configure failover clustering with node and disk majority.

-New client requests should be directed to either of the two servers. -Because of differences in hardware between the two servers, two-thirds of the client requests should be directed to srv5 with the remaining going to the new server. -Both srv5 and srv10 must be able to support peer-to-peer communications.

Configure the cluster to operate in multicast mode. Configure a port rule with the filtering mode set to Multiple host. Configure srv5 with a weight of 60 and srv10 with a wight of 30.

You need to stop the cluster, but do not want to disrupt current connections. You want the cluster to continue processing current connections, but not accept any new ones. Once all active connections are ended, the cluster should stop.

Drainstop the cluster.

-Each server has one network card installed. -Each server has its own disk storage. -Each server has the same data. -Each server has a static IP address. -Each server has the IIS role installed. -Each server has the NLB feature installed. -Each server has been added to the cluster. -The cluster has been assigned its own IP address.

Create an A record in DNS that points www.corpnet.com to the cluster's IP address.

-allocate storage to the servers as needed -Utilize the existing network infrastructure -maximize fault tolerance

Deploy the servers in a failover cluster. deploy an iSCSI storage area network (SAN).

You need the cluster to recalculate the quorum on the fly so that the cluster can continue to run even if the number of nodes remaining in the cluster is less than 50 percent.

Dynamic quorum

From the drop-down list, select the cmdlet you would now enter to enable SSD on the FileServ cluster.

Enable-ClusterStorageSpacesDirect

You begin the process of configuring continuously available shares (CAFS) on top of this general-purpose file server. The process require you to define the share location by indicating the name of the server and the share location.

FileServ

-NIC 1 connects the server to the main network. clients connect to the cluster though NIC1. -NIC2 connects the server to the storage area network (SAN). this network is also used for sending out heartbeat signals and performing convergence.

For NIC2, choose allow the cluster to use this network and clear the allow clients to connect through this network option. for NIC1, choose allow the cluster to use this network and select the allow clients to connect through this network option.

-Requests for app1 and app2 should be evenly distributed between srv5 and srv10. -Because app3 is not running on srv10, all requests for that application should be sent to srv5. requests should never be directed to srv10.

For app3, configure a port rule with the filtering mode set to multiple host. configure srv5 with a weight of 30 and srv10 with a wight of 0.

From the drop-down list, select the command you would enter to identify all storage devices that can be added to an SSD pool.

Get-PhysicalDisk -Can Pool $True

From the drop-down list, select the cmdlet you would now enter to verify that the SSD pool was created.

Get-StoragePool

What must you do before you can implement Storage Spaces Direct? (Select two.)

Install new hard drives in each server and leave the drives blank, offline and uninitialized. Install the failover clustering feature on each server.

If hv1 fails, you need the virtual machines hosted by hv1 to be migrated to hv2, and you need them to remain available during the migration.

Install the failover cluster feature on hv1 and create a failover cluster with hv2. then enable live migration.

-Each server has one network card installed. -Each server has its own disk storage. -Each server has the same data. -Each server receives an IP address dynamically from the DHCP server. -Each server has the IIS role installed. -Each server has the NLB feature installed.

No. Each server should be assigned a static IP address.

Can you implement a storage replica partnership between these two servers?

No. The disk 1 (dataD:) disks are not exactly the same size.

-begin the validation process for this configuration by selecting the two VMs as nodes in the cluster.

No. There is no shared storage device configured for the cluster nodes to use.

hv 1 has a virtual machine named vm1. you need to ensure that you can start vm1 on hv2 if hv1 fails

Open the hyper-v settings on hv1 and modify the replication settings. in the properties of vm1, enable replication.

Which plan could you follow to accomplish what your manager wants you to do?

Plan1 Plan3

-the replica virtual machine starts, which transfers the workload from the primary server to the replica server with no loss of information.

Planned

Which of the following allows you to create a failover cluster without having to purchse a SAN?

Storage Spaces Direct

-FS11 sends an acknowledgement to the user's application, letting it know the write operation was successful.

Synchronous

Which of the following must be completed before you can configure this replica partnership?

The file server role must be installed on FS1 and FS2. The storage replica feature must be installed on FS1 and FS2.

-All cluster nodes should be active and respond to client requests. -When a cluster node fails, requests should be redistributed between the remaining cluster members. -The cluster should continue to operate as long as there are more than half of the cluster members still available.

Use node majority for the quorum mode. Configure the application as a multiple-instance application.

You configure Srv1 as the preferred owner for the DHCP service. You simulate a failure of srv1 by taking it offline. The DHCP service does not switch to SRV2.

add srv2 as possible owner.

You want to use srv1 and srv2 for the DHCP service. Srv1 should be the primary server used to respond to DHCP requests. if srv1 is unavailable, srv2 should take over the DHCP service. SRV3 should never be used for the DHCP service.

configure srv1 and srv2 as possible owners. Configure srv1 as a preferred owner.

You need to ensure that each virtual machine can be moved between cs1 and cs2 independently of the other virtual machines.

enable cluster shared volumes.

What can you do to prevent cluster failover caused by automatic updates?

implement cluster-aware updating on the cluster.

You build three new server running Windows Server 2016. you install the failover cluster feature on the three new nodes and then use them to create a new failover cluster named cluster2

on a server in cluster2, click migrate roles.

drag the hypervisor type on the left to the failover that is initiated from it on the right.

replica primary replica

With the hyper-v replica broker role installed, you can configure sever types of virtual machine migrations.

storage drain live quick

-When you are finished, the temporary virtual machine must be deleted.

test

You need to ensure that cluster 1 can be a replica server for hv3 so that any virtual machines hosted on hv3 can be replicated to cluster1.

the hyper-v manager console on hv3. the failover cluster manager console on cluster 1.