Microsoft 70-646 Online Practice Questions and Exam Preparation

Microsoft 70-646 Online Questions & Answers

• Question 251:

  You need to recommend an automated deployment solution for the new servers in the finance department. What should you include in the recommendation?

  A. Microsoft Hyper-V Server 2008 R2
  B. Microsoft System Center Virtual Machine Manager (VMM)
  C. Windows Deployment Services (WDS)
  D. Windows Server Migration Tools
  C. Windows Deployment Services (WDS)

  ---

  Windows Deployment Services is a server role that was included with Windows Server 2008 and now includes various updates for Windows Server 2008 R2. The information in this section is specific to the Windows Server 2008 R2 release and does not apply to the initial release of Windows Server 2008.

  In Windows Server 2008 R2, you can deploy virtual hard disk (.vhd) images of Windows Server 2008 R2 to a physical (not virtual) computer using Windows Deployment Services. In general, you deploy .vhd images in the same way that you deploy .wim images. However, using WDSUTIL at the command line is the only supported method of adding and configuring the images

• Question 252:

  Your network consists of a single Active Directory forest. The sales department in your company has 600 Windows Server 2008 R2 servers.

  You need to recommend a solution to monitor the performance of the 600 servers.

  Your solution must meet the following requirements:

  -

  Generate alerts when the average processor usage is higher than 90 percent for 20 minutes.

  -

  Automatically adjust the processor monitoring threshold to allow for temporary changes in the workload.

  What should you recommend?

  A. Install Windows System Resource Manager (WSRM) on each server.
  B. Deploy Microsoft System Center Operations Manager (OpsMgr).
  C. Deploy Microsoft System Center Configuration Manager (SysMgr).
  D. Configure Reliability and Performance Monitor on each server
  B. Deploy Microsoft System Center Operations Manager (OpsMgr).

  ---

  MCITP Self-Paced Training Kit Exam 70-646 Windows Server Administration: Microsoft System Center Operations Manager 2007 When planning the centralized monitoring and management of large numbers of Windows Server 2008 computers, you should consider implementing Microsoft System Center Operations Manager 2007. System Center Operations Manager 2007 was touched on briefly during Chapter 4, "Application Servers and Services."Microsoft System Center Operations Manager 2007 allows you to centrally manage and monitor thousands of servers and applications and provides a complete overview of the health of your network environment. System Center Operations Manager 2007 is the most recent version of Microsoft Operations Manager 2005 (MOM). System Center Operations Manager 2007 provides the following features: Proactive alerts that recognize conditions that are likely to lead to failure of critical services, applications, and servers in the future The ability to configure tasks to automatically execute to resolve problems when given events occur

  The collection of long-term trend data from all servers and applications across the organization with the ability to generate comparison reports against current performance.

  Correlation of auditing data generated across the organization, allowing the detection of trends that might not be apparent when examining server auditing data in isolation.

• Question 253:

  You need to recommend a solution for managing Group Policy that meets the company's technical requirements. What should you recommend?

  A. Implement a central store.
  B. Upgrade DC3 to Windows Server 2008 R2.
  C. Create starter Group Policy objects (GPOs).
  D. Deploy Advanced Group Policy Management (AGPM).
  A. Implement a central store.

  ---

  http://msdn.microsoft.com/en-us/library/bb530196.aspx Create a Central Store The central store is a folder structure created in the sysvol directory on the domain controllers in each domain in your organization. You will need to create the central store only once on a single domain controller for each domain in your

  organization. The File Replication service then replicates the central store to all domain controllers. It is recommended that you create the central store on the primary domain controller because the Group Policy Management Console and

  Group Policy Object Editor connect to the primary domain controller by default.

  The central store consists of a root-level folder containing all language-neutral ADMX files and subfolders containing the language-specific ADMX resource files.

• Question 254:

  You need to recommend a solution for managing all of the servers. The solution must meet the company's technical requirements. What should you include in the recommendation?

  A. Remote Server Administration Tools (RSAT)
  B. the Administration Tools Pack (adminpak.msi)
  C. the Remote Desktop Gateway (RD Gateway) role service
  D. the Remote Desktop Web Access (RD Web Access) role service
  A. Remote Server Administration Tools (RSAT)

  ---

  http://support.microsoft.com/kb/941314

  Microsoft Remote Server Administration Tools (RSAT) enables IT administrators to remotely manage roles and features in Windows Server 2008 from a computer that is running Windows Vista with Service Pack 1 (SP1). It includes support for remote management of computers that are running either a Server Core installation option or a full installation option of Windows Server 2008. It provides similar functionality to the Windows Server 2003 Administration Tools Pack.

• Question 255:

  You need to recommend a BitLocker recovery method that meets the company's technical requirements.

  Which recovery method should you recommend?

  A. a data recovery agent
  B. a recovery key
  C. a recovery password printed and stored in a secure location
  D. a recovery password stored in Active Directory
  A. a data recovery agent

  ---

  http://technet.microsoft.com/en-us/library/dd875560%28WS.10%29.aspx

  Data recovery agents are accounts that are able to decrypt BitLocker-protected drives by using their smart card certificates and public keys. Recovery of a BitLocker-protected drive can be accomplished by a data recovery agent that has been configured with the proper certificate.

  Before a data recovery agent can be configured for a drive, you must add the data recovery agent to Public Key Policies\BitLocker Drive Encryption in either the Group Policy Management Console (GPMC) or the Local Group Policy Editor. You must also enable and configure the Provide the unique identifiers for your organization policy setting to associate a unique identifier to a new drive that is enabled with BitLocker. An identification field is a string that is used to uniquely identify a business unit or organization. Identification fields are required for management of data recovery agents on BitLocker-protected drives. BitLocker will only manage and update data recovery agents when an identification field is present on a drive and is identical to the value configured on the computer.

• Question 256:

  A company has servers that run Windows Server 2008 R2 and client computers that run 32-bit Windows 7 Enterprise. The environment includes Microsoft Application Visualization (App-V).

  You plan to deploy a 64-bit only Application.

  You need to ensure that users can run the Application. The Application must be automatically available on the client computers.

  Which actions should you perform in sequence?

  To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. (Use only actions that Apply.)

  Select and Place:

  

  

  ---

  You have a 64bit application to be installed on 32 bit client PCs, the app is incompatible with these clients for this reason. So you create a remote desktop server (formally terminal server) and install the 64 bit version on this (step 1 of the

  answer) you then create a RemoteApp that os compatable to the 32bit clients (step 2) and finally you assign that using GPO to those clients that need it (step 3)

  What are RemoteApp programs?

  RemoteApp programs are programs that are accessed remotely through Terminal Services and appear as if they are running on the end user's local computer. Instead of being presented to the user in the desktop of the remote terminal

  server, the RemoteApp program is integrated with the client's desktop, running in its own resizable window with its own entry in the taskbar. Users can run RemoteApp programs side-by-side with their local programs. If a user is running more

  than one RemoteApp program on the same terminal server, the RemoteApp programs will share the same Terminal Services session.

  In Windows Server 2008, users can access RemoteApp programs in several ways, depending on the deployment method that you choose. They can:

  Access a link to the program on a Web site by using TS Web Access.

  Double-click a Remote Desktop Protocol (.rdp) file that has been created and distributed by their administrator.

  Double-click a program icon on their desktop or Start menu that has been created and distributed by their administrator with a Windows Installer (.msi) package.

  Double-click a file where the file name extension is associated with a RemoteApp program. This can be configured by their administrator with a Windows Installer package.

  The .rdp files and Windows Installer packages contain the settings that are needed to run RemoteApp programs. After opening a RemoteApp program on their local computer, the user can interact with the program that is running on the

  terminal server as if it were running locally.

  How should I deploy RemoteApp programs?

  Before you configure TS RemoteApp, you should decide how you want to distribute RemoteApp programs to users. You can use either of the following deployment methods:

  You can make RemoteApp programs available on a Web site by distributing the RemoteApp programs through TS Web Access.

  You can distribute RemoteApp programs as .rdp files or Windows Installer packages through a file share, or through other distribution mechanisms such as Microsoft Systems Management Server or Active Directory software distribution.

  Deploying RemoteApp programs through a file share or other distribution mechanism

  

  You can also deploy RemoteApp programs through .rdp files or Windows Installer packages that are made available through file sharing, or through other distribution mechanisms such as Microsoft Systems Management Server or Active Directory software distribution. These methods enable you to distribute RemoteApp programs to users without using TS Web Access.

  1. Configure the server that will host RemoteApp programs. This includes installing Terminal Server, installing programs, and verifying remote connection settings.

  2. Use TS RemoteApp Manager to add RemoteApp programs and to configure global deployment settings.

  3. Use TS RemoteApp Manager to create .rdp files or Windows Installer packages from RemoteApp programs.

  Group Policy settings to control client behavior when opening a digitally signed .rdp file You can use Group Policy to configure clients to always recognize RemoteApp programs from a

  particular publisher as trusted. You can also configure whether clients will block RemoteApp programs and remote desktop connections from external or unknown sources. By using these policy settings, you can reduce the number and

  complexity of security decisions that users face.

  This reduces the chances of inadvertent user actions that may lead to security vulnerabilities.

  The relevant Group Policy settings are located in the Local Group Policy Editor at the following location, in both the Computer Configuration and in the User Configuration node:

  Administrative Templates\Windows Components\Terminal Services\Remote Desktop Connection Client

  The available policy settings are:

  Specify SHA1 thumbprints of certificates representing trusted .rdp publishers This policy setting allows you to specify a list of Secure Hash Algorithm 1 (SHA1) certificate thumbprints that represent trusted .rdp file publishers. If you enable this

  policy setting, any certificate with an SHA1 thumbprint that matches a thumbprint on the list will be considered trusted.

  Allow .rdp files from valid publishers and user's default .rdp settings This policy setting allows you to specify whether users can run .rdp files from a publisher that signed the file with a valid certificate. This policy setting also controls whether

  the user can start an RDP session by using default .rdp settings, such as when a user directly opens the RDC client without specifying an .rdp file.

  Allow .rdp files from unknown publishers

  This policy setting allows you to specify whether users can run unsigned .rdp files and .rdp filesfrom unknown publishers on the client computer.

• Question 257:

  You need to recommend a security solution for the documents in the finance department. The solution must meet the company's security requirements. What should you include in the recommendation?

  A. accessbased enumeration (ABE) and Encrypted File System (EFS)
  B. accessbased enumeration (ABE) and Windows BitLocker Drive Encryption (BitLocker)
  C. Active Directory Rights Management Services (AD RMS)
  D. File Server Resource Manager (FSRM) file screens
  C. Active Directory Rights Management Services (AD RMS)

  ---

  http://technet.microsoft.com/en-us/library/dd996658%28WS.10%29.aspx

  Rights policy templates are used to control the rights that a user or group has on a particular piece of rightsprotected content. Active Directory Rights Management Services (AD RMS) stores rights policy templates in the configuration database. Optionally, it may maintain a copy of all rights policy templates in a shared folder that you specify.

• Question 258:

  Your network consists of a single Active Directory domain. The network contains 20 file servers that run Windows Server 2008 R2. Each file server contains two volumes. One volume contains the operating system.

  The other volume contains all data files.

  You need to plan a recovery strategy that meets the following requirements:

  -

  Allows the operating system to be restored

  -

  Allows the data files to be restored

  -Ensures business continuity

  -Minimizes the amount of time to restore the server

  What should you include in your plan?

  A. Windows Deployment Services (WDS)
  B. Windows Automated Installation Kit (Windows AIK) and folder redirection
  C. the Multipath I/O feature and Volume Shadow Copies
  D. the Windows Server Backup feature and System Image Recovery
  D. the Windows Server Backup feature and System Image Recovery

  ---

  MCITP Self-Paced Training Kit Exam 70-646 Windows Server Administration:

  Windows Server Backup Windows Server Backup provides a reliable method of backing up and recovering the operating system, certain applications, and files and folders stored on your server.

  This feature replaces the previous backup feature that was available with earlier versions of Windows.

  Windows Server Backup

  The Windows Server Backup tool is significantly different from ntbackup.exe, the tool included in Windows Server 2000 and Windows Server 2003. Administrators familiar with the previous tool should study the capabilities and limitations of

  the new Windows Server Backup utility because many aspects of the tool's functionality have changed.

  Exam Tip: What the tool does

  The Windows Server 2008 exams are likely to focus on the differences between NTBACKUP and Windows Server Backup.

  The key points to remember about backup in Windows Server 2008 are:

  Windows Server Backup cannot write to tape drives.

  You cannot write to network locations or optical media during a scheduled backup.

  The smallest object that you can back up using Windows Server Backup is a volume.

  Only local NTFS-formatted volumes can be backed up.

  Windows Server Backup files write their output as VHD (Virtual Hard Disk) files. VHD files can be mounted with the appropriate software and read, either directly or through virtual machine software such as Hyper-V.

  MORE INFO Recovering NTbackup backups

  You cannot recover backups written using ntbackup.exe. A special read-only version of ntbackup.exe that is compatible with Windows Server 2008 can be downloaded from

  http://go.microsoft.com/fwlink/?LinkId=82917.

  Windows Server Backup is not installed by default on Windows Server 2008 and must be installed as a feature using the Add Features item under the Features node of the Server Manager console.

  When installed, the Windows Server Backup node becomes available under the Storage node of the Server Manager Console. You can also open the Windows Server Backup console from the Administrative Tools menu. The wbadmin.exe

  command-line utility, also installed during this process, is covered in "The wbadmin Command-Line Tool" later in this lesson. To use Windows Server Backup or wbadmin to schedule backups, the computer requires an extra internal or

  external disk. External disks will need to be either USB 2.0 or IEEE 1394 compatible. When planning the deployment of disks to host scheduled backup data, you should ensure that the volume is capable of holding at least 2.5 times the

  amount of data that you want to back up. When planning deployment of disks for scheduled backup, you should monitor how well this size works and what sort of data retention it allows in a trial before deciding on a disk size for wider

  deployment throughout your organization.

  When you configure your first scheduled backup, the disk that will host backup data will be hidden from Windows Explorer. If the disk currently hosts volumes and data, these will be removed to store scheduled backup data. Note that this only

  applies to scheduled backups and not to manual backups. You can use a network location or external disk for a manual backup without worrying that data already stored on the device will be lost. The format and repartition only happens when

  a device is first used to host scheduled backup data.

  It does not happen when subsequent backup data is written to the same location.

  It is also important to remember that a volume can only store a maximum of 512 backups. If you need to store a greater number of backups, you will need to write these backups to a different volume. Of course given the amount of data on

  most servers, you are unlikely to find a disk that has the capacity to store so many backups.

  So that scheduled backups can always be executed, Windows Server Backup will automatically remove the oldest backup data on a volume that is the target of scheduled backups. You do not need to manually clean up or remove old backup

  data.

  Performing a Scheduled Backup

  Scheduled backups allow you to automate the backup process. After you set the schedule, Windows Server Backup takes care of everything else. By default, scheduled backups are set to occur at 9:00 P.M. If your organization still has

  people regularly working on documents at that time, you should reset this. When planning a backup schedule you should ensure that the backup occurs at a time when the most recent day's changes to data are always captured. Only

  members of the local Administrators group can configure and manage scheduled backups.

  To configure a scheduled backup, perform the following steps:

  1.

  Open Windows Server Backup. Click Backup Schedule in the Actions pane ofWindows Server Backup. This will start the Backup Schedule Wizard. Click Next.

  2.

  The next page of the wizard asks whether you want to perform a full server backup or a custom backup.

  Select Custom and click Next. As you can see in Figure 12-3, volumes that contain operating system components are always included in custom backups. Volume E is excluded in this case, because this is the location where backup data will be written.

  

  Figure 12-3Selecting backup items

  3.The default backup schedule is once a day at 9:00 P.M. You can configure multiple backups to be taken during the day. You are most likely to do this in the event that data on the server that you are backing up changes rapidly. On servers

  where data changes a lot less often, such as on a Web server where pages are only updated once a week, you would configure a more infrequent schedule.

  4.On the Select Destination Disk page, shown in Figure 12-4, you select the disk that backups are written to. If multiple disks are selected, multiple copies of the backup data are written. You should note that the entire disk will be used. All

  existing volumes and data will be removed and the backup utility will format and hide the disks prior to writing the first backup data.

  5.On the Label Destination Disk page, note the label given to the disk you have selected to store backups. When you finish the wizard, the target destination is formatted and then the first backup will occur at the scheduled time.

  An important limitation of Windows Server Backup is that you can only schedule one backup job.

  In other words, you cannot use Windows Server Backup to schedule jobs that you might be used to scheduling in earlier versions of Windows, such as a full backup on Monday night with a series of incremental backups every other day of the

  week. You can configure Windows Server Backup to perform incremental backups, but this process is different from what you might be used to with other backup applications.

  

  Figure 12-4Selecting a destination disk

  Performing an Unscheduled Single Backup

  Unscheduled single backups, also known as manual backups, can be written to network locations, local and external volumes, and local DVD media. If a backup encompasses more than the space available on a single DVD media, you can

  span the backup across multiple DVDs. Otherwise, if the calculated size of a backup exceeds the amount of free space available on the destination location, the backup will fail. You will perform a manual backup in a practice exercise at the

  end of this lesson.

  When performing a manual backup, you must choose between using one of the following two types of Volume

  Shadow Copy Service backup:

  VSS Copy BackupUse this backup option when another backup product is also used to back up applications on volumes in the current backup. Application log files are retained when you perform this type of manual backup. This is the default

  when taking a backup.

  VSS Full BackupUse this backup option when no other backup products are used to back up the host computer. This option will update each file's backup attribute and clears application log files.

  When performing a single backup, you can also back up a single volume without having to back up the system or boot volumes. This is done by clearing the Enable System Recovery option when selecting backup items.

  You might use this option to back up a specific volume's data when you are going to perform maintenance on the volume or suspect that the disk hosting the volume might fail, but do not want to wait for a full server backup to complete.

  Full Server and Operating System Recovery

  Also known as Bare Metal Recovery, full server recovery allows you to completely restore the server by booting from the Windows Server 2008 installation media or Windows Recovery

  Environment. See the note on building a recovery solution for more information on how to set up a local Windows Recovery Environment on a Windows Server 2008 computer. Full server recovery goes further than the Automated System

  Recovery (ASR) feature that was available in Windows Server 2003 because full server recovery will restore all operating system, application, and other data stored on the server. ASR did not provide such a complete recovery and it was

  necessary to further restore data from backup after the ASR process was complete.

  An operating system recovery is similar to a full server recovery except that you only recover critical volumes and do not recover volumes that do not contain critical data. For example, if you have a file server where the disks that host critical

  operating system volumes are separate from the disks that host shared folder volumes and the disks that host the critical operating system volumes fail, you should perform an operating system recovery.

  

  Figure 12-13Select Windows Complete PC Restore

• Question 259:

  You need to design a Windows Server Update Services (WSUS) infrastructure that meets the following requirements:

  -The updates must be distributed from a central location.

  -All computers must continue to receive updates in the event that a server fails.

  What should you include in your design?

  A. Configure two WSUS servers in a Microsoft SQL Server 2008 failover cluster. Configure each WSUS server to use a local database.
  B. Configure a single WSUS server to use multiple downstream servers. Configure each WSUS server to use a RAID 1 mirror and a local database.
  C. Configure a single WSUS server to use multiple downstream servers. Configure each WSUS server to use a RAID 5 array and a local database.
  D. Configure a Microsoft SQL Server 2008 failover cluster. Configure two WSUS servers in a Network Load Balancing cluster. Configure WSUS to use the remote SQL Server 2008 database instance.
  D. Configure a Microsoft SQL Server 2008 failover cluster. Configure two WSUS servers in a Network Load Balancing cluster. Configure WSUS to use the remote SQL Server 2008 database instance.

  ---

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

  WSUS database

  WSUS 3.0 SP2 requires a database for each WSUS server. WSUS supports the use of a database that resides on a different computer than the WSUS server, with some restrictions. For a list of supported databases and remote database

  limitations, see WSUS database requirements.

  The WSUS database stores the following information:

  

  WSUS server configuration information

  

  Metadata that describes each update

  

  Information about client computers, updates, and interactions

  If you install multiple WSUS servers, you must maintain a separate database for each WSUS server, whether it is an autonomous or a replica server. (For more information about WSUS server types, see Design the WSUS Server Layout.)

  You cannot store multiple WSUS databases on a single instance of SQL Server, except in Network Load Balancing (NLB) clusters that use SQL Server failover. For more about this configuration, see Configure WSUS for Network Load

  Balancing.

  SQL Server, SQL Server Express, and Windows Internal Database provide the same performance characteristics for a single server configuration, where the database and the WSUS service are located on the same computer. A single server

  configuration can support several thousand WSUS client computers.

  Windows Server 2008 Enterprise Edition

  Windows Server 2008 Enterprise Edition is the version of the operating system targeted at large businesses.

  Plan to deploy this version of Windows 2008 on servers that will run applications such as SQL Server 2008 Enterprise Edition and Exchange Server 2007. These products require the extra processing power and RAM that Enterprise Edition

  supports. When planning deployments, consider Windows Server 2008 Enterprise Edition in situations that require the following technologies unavailable in Windows Server 2008 Standard

  Edition:

  Failover ClusteringFailover clustering is a technology that allows another server to continue to service client requests in the event that the original server fails. Clustering is covered in more detail in Chapter 11, "Clustering and High

  Availability." You deploy failover clustering on mission-critical servers to ensure that important resources are available even if a server hosting those resources fails.

• Question 260:

  Your company has 250 branch offices. Your network contains an Active Directory domain. The domain controllers run Windows Server 2008 R2. You plan to deploy Readonly Domain Controllers (RODCs) in the branch offices.

  You need to plan the deployment of the RODCs to meet the following requirements:

  -Build each RODC at the designated branch office.

  -

  Ensure that the RODC installation source files do not contain cached secrets.

  -

  Minimize the bandwidth used during the initial synchronization of Active Directory Domain Services (AD?DS).

  What should you include in your plan?

  A. Use Windows Server Backup to perform a full backup of an existing domain controller. Use the backup to build the new RODCs.
  B. Use Windows Server Backup to perform a custom backup of the critical volumes of an existing domain controller. Use the backup to build the new RODCs.
  C. Create a DFS namespace that contains the Active Directory database from one of the existing domain controllers. Build the RODCs by using an answer file.
  D. Create an RODC installation media. Build the RODCs from the RODC installation media.
  D. Create an RODC installation media. Build the RODCs from the RODC installation media.

  ---

  http://technet.microsoft.com/en-us/library/cc770654%28WS.10%29.aspx

  Installing AD DS from Media

  Applies To: Windows Server 2008, Windows Server 2008 R2

  You can use the Ntdsutil.exe tool to create installation media for additional domain controllers that you are creating in a domain. By using the Install from Media (IFM) option, you can minimize the replication of directory data over the network.

  This helps you install additional domain controllers in remote sites more efficiently.

  Ntdsutil.exe can create four types of installation media, as described in the following table.

  You must use read-only domain controller (RODC) installation media to install an RODC. For RODC installation media, the ntdsutil command removes any cached secrets, such as passwords.

  You can create RODC installation media either on an RODC or on a writeable domain controller.

  You must use writeable domain controller installation media to install a writeable domain controller. You can create writeable domain controller installation media only on a writeable

  domain controller.

  If the source domain controller where you create the installation media and the destination server where you plan to install ActiveDirectory Domain Services (ADDS) both run Windows Server2008 with Service Pack2 or later or Windows

  Server2008R2, and if you are using Distributed File System (DFS) Replication for SYSVOL, you can run the ntdsutil ifm command with an option to include the SYSVOL shared folder in the installation media. If the installation media includes

  SYSVOL, you must use Robocopy.exe to copy the installation media from the source domain controller to the destination server. For more information, see Installing an Additional Domain Controller by Using IFM.