Microsoft 70-643 Online Practice Questions and Exam Preparation

Microsoft 70-643 Online Questions & Answers

• Question 91:

  Your company has an Active Directory domain. The company has a server named Server1 that has the Remote Desktop Services server role and the RD Web Access role service installed. The company has a server named Server2 that runs ISA Server 2006. The company deploys the Remote Desktop Gateway (RD Gateway) role on a new server named Server3. The company wants to use ISA as the SSL endpoint for Remote Desktop connections. You need to configure the RD Gateway role on Server3 to use ISA 2006 on Server2.

  What should you do?

  A. Configure the RD Gateway to use SSL HTTPS-HTTP bridging.
  B. Configure the Remote Desktop Connection Authorization Policy Store on Server3 to use Server2 as the Central Network Policy Server.
  C. Export the SSL certificate from Server2 and install the SSL certificate on Server3. Configure the RD Gateway to use the SSL certificate from Server2.
  D. Export a self-signed SSL certificate from Server3 and install the SSL certificate on Server2. Configure the ISA service on Server2 to use the SSL certificate from Server3.
  A. Configure the RD Gateway to use SSL HTTPS-HTTP bridging.

  ---

  To enhance security for an RD Gateway server, you can configure Microsoft Internet Security and Acceleration (ISA) Server or a non-Microsoft product to function as a Secure Sockets Layer (SSL) bridging device. The SSL bridging device can enhance security by terminating SSL sessions, inspecting packets, and re-establishing SSL sessions. You can configure ISA Server communication with the RD Gateway server in either of the two following ways:

  HTTPS-HTTPS bridging. In this configuration, the RD Gateway client initiates an SSL (HTTPS) request to the SSL bridging device. The SSL bridging device initiates a new HTTPS request to the RD Gateway server, for maximum security. HTTPS-HTTP bridging. In this configuration, the RD Gateway client initiates an SSL (HTTPS) request to the SSL bridging device. The SSL bridging device initiates a new HTTP request to the RD Gateway server. To use HTTPS-HTTPS or HTTPS-HTTP bridging, you must enable the Use SSL Bridging setting on the RD Gateway server.

  Source: http://technet.microsoft.com/en-us/library/cc772387.aspx

• Question 92:

  Your company named Contoso, Ltd. runs Windows Server 2008 R2. You manage a Web server named Server1.

  Internet users access Server1 by using http://www.contoso.com and https://www.contoso.com. The Server1 server uses an SSL certificate from a public certification authority (CA).

  You install an additional Web server named Server2. You configure a Network Load Balancing cluster to distribute the incoming HTTP and HTTPS traffic between both Web servers.

  You need to configure an SSL certificate on Server2 to support HTTPS connections.

  You must ensure that all users can connect to https://www.contoso.com without receiving security warnings.

  What should you do?

  A. Open the Internet Information Services (IIS) Manager console on Server2. Create a self-signed certificate.
  B. Open the Internet Information Services (IIS) Manager console on Server1. Export the SSL certificate to a .pfx file. Import the .pfx file to Server2.
  C. Open the Certificates snap-in on Server1. Export the SSL certificate to a .cer file. Import the .cer file to Server2.
  D. Request a new SSL certificate from the public CA. Use Server2 as the Common Name in the request. Install the new certificate on Server2.
  B. Open the Internet Information Services (IIS) Manager console on Server1. Export the SSL certificate to a .pfx file. Import the .pfx file to Server2.

  ---

  To export a certificate in PFX format using IIS Manager:

  Start IIS Manager. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  In the console tree, click the name of the computer.

  In the IIS section of the center pane, double-click Server Certificates. Right-click the certificate (.cer file) in the center pane, and then click Export. Select the location for the exported file, type the name for the file (with the .pfx extension), and

  then type and confirm the password to encrypt the private key.

  Click OK.

  http://technet.microsoft.com/en-us/library/hh314619(v=ws.10).aspx

• Question 93:

  Your network contains a Web server named Served. Served has an application pool named ApplAppPool.

  You need to configure ApplAppPool to restart automatically when the application pool uses more than 100 MB of virtual memory.

  What should you do from Internet Information Services (IIS) Manager?

  Hot Area:

  

  

  ---

  Step #1.

  Click on the "Recycling" link in Actions pane to bring up the dialog box shown below.

  

  Step #2.

  Select the Virtual Memory check box and enter 102400 then click Next. (102400KB = 100MB).

  

  Step #3.

  Leave the default selections and click Finish.

  

• Question 94:

  Your network contains a server that runs Windows Server 2008 R2 Standard. The server is configured to native boot from a virtual hard disk (VHD). All hard disks on the server are configured as basic disks that use an MBR. A new corporate security policy states that all of the hard disks on the server must use Windows BitLocker Drive Encryption (BitLocker). You need to ensure that the server meets the corporate security policy.

  What should you do first?

  A. Configure the disks to use a GPT.
  B. Convert the disks to dynamic disks.
  C. Upgrade the server to Windows Server 2008 R2 Enterprise.
  D. Back up the server and restore the server to a physical volume.
  D. Back up the server and restore the server to a physical volume.

  ---

  Applies To: Windows 7, Windows Server 2008 R2

  Configuring native VHD boot if the host volume is protected by BitLocker. You can save a VHD file on a file system that is protected by BitLockerTM, but you cannot use the VHD for native boot or enable Bitlocker on the volume(s) that are contained inside a VHD. Source: http://technet.microsoft.com/en-us/library/dd440865(WS.10).aspx

• Question 95:

  You install a new server named Server1 that runs Windows Server 2008 R2. The server has the Streaming Media Services server role installed. You install and activate all Windows Media Services control protocols.

  Users connect to Server1 locally and remotely through a firewall. You need to ensure that the protocol rollover will occur only if the users are accessing Server1 from the Internet.

  What should you do?

  A. Install the Reliable Multicast Protocol on Server1.
  B. Install the Quality of Service (QoS) service on the network adapter.
  C. Configure the firewall to forward incoming port 1755 traffic to Server1.
  D. Use announcements to enable users to access the streaming media.
  D. Use announcements to enable users to access the streaming media.

  ---

  You can force your Windows Media server to use a specific protocol by identifying the protocol to be used in the announcement file (for example, rtspu:// server/publishing_point/file). However, to provide an optimal streaming experience for all client versions, we recommend that the URL use the general MMS protocol. If clients connect to your stream using a URL with an MMS URL moniker, any necessary protocol rollover occurs automatically. Be aware that users can disable streaming protocols in the property settings of Windows Media Player. If a user disables a protocol, it is skipped during rollover. For example, if HTTP is disabled, then URLs will not roll over to HTTP.

  Source: http://technet.microsoft.com/en-us/library/ee126137.aspx

• Question 96:

  Your network contains a single Active Directory domain. The domain contains a server named Server1 that runs Windows Server 2008 R2.

  Server1 has an iSCSI host bus adapter that connects to an iSCSI target. You install an additional iSCSI host bus adapter on Server1. You need to ensure that Server1 can access the iSCSI target if a host bus adapter fails.

  What should you do first?

  A. At the command prompt, run mpclaim.exe -l m 6.
  B. Install the Multipath I/O feature.
  C. Bridge the iSCSI host bus adapters.
  D. Install the Internet Storage Name Server (iSNS) feature.
  B. Install the Multipath I/O feature.

  ---

  About MPIO

  Microsoft Multipath I/O (MPIO) is a Microsoft-provided framework that allows storage providers to develop multipath solutions that contain the hardware-specific information needed to optimize connectivity with their storage arrays. These

  modules are called device-specific modules (DSMs). The concepts around DSMs are discussed later in this document. MPIO is protocol-independent and can be used with Fibre Channel, Internet SCSI (iSCSI), and Serial Attached SCSI

  (SAS) interfaces in Windows ServerR 2008 and Windows Server 2008 R2.

  Multipath solutions in Windows Server 2008 R2

  When running on Windows Server 2008 R2, an MPIO solution can be deployed in the following ways:

  By using a DSM provided by a storage array manufacturer for Windows Server 2008 R2 in a Fibre Channel, iSCSI, or SAS shared storage configuration.

  By using the Microsoft DSM, which is a generic DSM provided for Windows Server 2008 R2 in a Fibre Channel, iSCSI, or SAS shared storage configuration.

  High availability through MPIO MPIO allows WindowsR to manage and efficiently use up to 32 paths between storage devices and the Windows host operating system. MPIO provides fault tolerant connectivity to storage. By employing MPIO

  users are able to mitigate the risk of a system outage at the hardware level. MPIO provides the logical facility

  for routing I/O over redundant hardware paths connecting server to storage.

  These redundant hardware paths are made up of components such as cabling, host bus adapters (HBAs), switches, storage controllers, and possibly even power.

  MPIO solutions logically manage these redundant connections so that I/O requests can be rerouted if a component along one path fails.

  As more and more data is consolidated on storage area networks (SANs), the potential loss of access to storage resources is unacceptable. To mitigate this risk, high availability solutions, such as MPIO, have now become a requirement.

  Source: http://technet.microsoft.com/en-us/library/ee619734(WS.10).aspx

• Question 97:

  Your network contains a server named Server1 that has the Remote Desktop Services (RDS) server role installed and all of the RDS role services installed.

  You plan to distribute Remote Desktop Connection (.rdp) files to users on the network.

  You need to ensure that the Remote Desktop Connection (.rdp) files cannot be used if the content of the files changes after you distribute them.

  Which tool should you use?

  A. Rdpsign
  B. Dism
  C. Netsh
  D. Regedit
  E. Remote Desktop Connection Manager
  F. Rdpinit
  G. Windows System Resources Manager (WSRM)
  H. Remote Desktop Session Host Configuration
  I. Remote Desktop Services Manager
  J. Mstsc
  A. Rdpsign

  ---

  Rdpsign

  Enables you to digitally sign a Remote Desktop Protocol (.rdp) file.

  Syntax:

  rdpsign /sha1 [/q | /v |] [/l]

  Source: http://technet.microsoft.com/en-US/library/cc753982(v=ws.10).aspx

• Question 98:

  Your network contains a Web server that runs Windows Server 2008 R2. You need to generate a report for each Active Server Page (ASP) that takes more than two seconds to process. What should you use?

  A. Reports in Performance Monitor
  B. Data Collector Sets (DCSs) in Performance Monitor
  C. Logging in Internet Information Services (IIS) Manager
  D. Failed Request Tracing Rules in Internet Information Services (IIS) Manager
  D. Failed Request Tracing Rules in Internet Information Services (IIS) Manager

  ---

  

• Question 99:

  You have two servers that run Windows Server 2008 named Server1 and Server2. Both servers have the Windows Server visualization role service installed.

  You need to remotely manage the visualization settings of Server2 from Server1.

  What should you do?

  A. From the command prompt, run vmconnect.exe server2.
  B. From the command prompt, run vmconnect.exe server1 server2.
  C. Open the Visualization Management Console. From the left-hand pane, right-click Server1, point to New and then click Virtual machine.
  D. Open the Virtualization Management Console. From the left-hand pane, right-click Virtualization Services and then click Connect to Server.
  D. Open the Virtualization Management Console. From the left-hand pane, right-click Virtualization Services and then click Connect to Server.

  ---

  To remotely manage the virtualization settings of Server2 from Server1, you need to right-click Virtualization Services from the Virtualization Management Console and then click Connect to Server.

  You can manage multiple Hyper-V server instances in the management console's left pane. Selecting a server instance displays that server's VMs in the center Virtual Machines pane. You can manage the VMs by right-clicking them and selecting the desired commands on the context menu. The Connect command allows you to connect to a running VM, which starts the Virtual Machine Connection window. Reference: A First Look at Windows Server 2008 Hyper-V http://windowsitpro.com/Windows/Articles/ArticleID/97857/pg/2/2.html

• Question 100:

  Your network contains two servers that have the Hyper-V server role installed.

  You install the Failover Clustering feature on both servers. You add both servers as nodes in the cluster.

  You need to ensure that you can perform live migrations of individual virtual machines (VMs) between the nodes.

  The solution must minimize the number of volumes required to host the VMs.

  What should you do first?

  A. From Failover Cluster Manager, enable Cluster Shared Volumes.
  B. From Failover Cluster Manager, modify the quorum settings of the cluster.
  C. From Hyper-V Manager on each server, modify the default location for the virtual hard disks (VHDs).
  D. From Hyper-V Manager on each server, modify the default location for the virtual machine configuration files.
  A. From Failover Cluster Manager, enable Cluster Shared Volumes.

  ---

  Cluster Shared Volumes, a feature available with some versions of failover clustering, simplifies the configuration and management of clustered virtual machines.

  With Cluster Shared Volumes, multiple clustered virtual machines can use the same LUN (disk) while still being able to fail over (or move from node to node) independently of one another.

  Note In Windows ServerR 2008 R2, the Cluster Shared Volumes feature included in failover clustering is only supported for use with the Hyper-V server role. The creation, reproduction, and storage of files on Cluster Shared Volumes that

  were not created for the Hyper-V role, including any user or application data stored under the ClusterStorage folder of the system drive on every node, are not supported and may result in unpredictable behavior, including data corruption or

  data loss on these shared volumes. Only files that are created for the Hyper-V role can be stored on Cluster Shared Volumes. An example of a file type that is created for the Hyper-V role is a Virtual Hard Disk (VHD) file.

  Before installing any software utility that might access files stored on Cluster Shared Volumes (for example, an antivirus or backup solution), review the documentation or check with the vendor to verify that the application or utility is

  compatible with Cluster Shared Volumes.

  Overview of Cluster Shared Volumes

  Cluster Shared Volumes is available in versions of Windows ServerR 2008 R2 and of MicrosoftR Hyper-VTM Server 2008 R2 that include the Failover Clustering feature. Volumes that are configured as Cluster Shared Volumes can be

  accessed by all nodes of a failover cluster. Each node can open and manage files on the volumes. Therefore, different nodes can host different virtual machines that all have files on the same volume.

  This design has many advantages, including the following:

  Easier storage management: When virtual machines share volumes, fewer LUNs need to be configured and managed to host the same number of virtual machines. Independent failover of virtual machines : Although multiple virtual machines

  are sharing the same volume, each virtual machine can fail over, or be moved or migrated, independently of other virtual machines. No drive letter restrictions: Cluster Shared Volumes do not need to be assigned a drive letter, so you are not

  restricted by the number of available drive letters, and you do not have to manage volumes using GUIDs.

  Enhanced availability: The Cluster Shared Volumes feature is designed to detect and handle many problems that would otherwise cause the storage to be unavailable to virtual machines. This includes detecting and handling storage

  connection problems (Cluster Shared Volumes reroutes the storage access through another node).

  Efficient use of storage: You can make better use of disk space, because you do not need to place each Virtual Hard Disk (VHD) file on a separate disk with extra free space set aside just for that VHD file. Instead, the free space on a Cluster

  Shared Volume can be used by any VHD file on that LUN. This reduces the total amount of space that must be set aside for expansion, and simplifies capacity planning

  Source: http://technet.microsoft.com/en-us/library/dd630633(WS.10).aspx