Microsoft 70-646 Online Practice Questions and Exam Preparation

Microsoft 70-646 Online Questions & Answers

• Question 1:

  Your company has a branch office that contains a Windows Server 2008 R2 computer. The Windows Server 2008 R2 computer runs Windows Server Update Services (WSUS). The WSUS server is configured to store updates locally.

  The company opens four new satellite offices. Each satellite office connects to the branch office by using a dedicated WAN link. Internet access is provided through the branch office.

  You need to design a strategy for patch management that meets the following requirements:

  - WSUS updates are approved independently for each satellite office.

  -

  Internet traffic is minimized. What should you include in your design?

  A. In each satellite office, install a WSUS server. Configure each satellite office WSUS server as an autonomous server.
  B. In each satellite office, install a WSUS server. Configure each satellite office WSUS server as a replica of the branch office WSUS server.
  C. In each satellite office, install a WSUS server. Configure each satellite office WSUS server to use the branch office WSUS server as an upstream server.
  D. For each satellite office, create organizational units (OUs). Create and link the Group Policy objects (GPOs) to the OUs. Configure different schedules to download updates from the branch office WSUS server to the client computers in each satellite office.
  C. In each satellite office, install a WSUS server. Configure each satellite office WSUS server to use the branch office WSUS server as an upstream server.

  ---

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

  In addition, a Windows Server 2008 server running WSUS server can act as an upstream server--an update source for other WSUS servers within your organization. At least one WSUS

  server in your network must connect to the Microsoft Update Web site to get available update information. How many other servers connect directly to Microsoft Update is something you need to determine as part of your planning process,

  and depends upon network configuration and security requirements.

  

  In this deployment model, the WSUS server that receives updates from the Microsoft Update server is designated as the upstream server. A WSUS server that retrieves updates from another WSUS server is designated as a downstream server.

  Autonomous mode: The Autonomous mode, also called distributed administration, is the default installation option for WSUS. In Autonomous mode, an upstream WSUS server shares updates with downstream servers during synchronization. Downstream WSUS servers are administered separately, and they do not receive update approval status or computer group information from the upstream server. By using the distributed management model, each WSUS server administrator selects update languages, creates computer groups, assigns computers to groups, tests and approves updates, and makes sure that the correct updates are installed to the appropriate computer groups. The following image shows how you might deploy autonomous WSUS servers in a branch office environment:

  

  Replica mode: The Replica mode, also called centralized administration, works by having an upstream WSUS server that shares updates, approval status, and computer groups with downstream servers. Replica servers inherit update approvals and are not administered separately from the upstream WSUS server. The following image shows how you might deploy replica WSUS servers in a branch office environment.

  

  Branch Office

  You can leverage the Branch Office feature in Windows to optimize WSUS deployment. This type of deployment offers the following advantages:

  Helps reduce WAN link utilization and improves application responsiveness. To enable BranchCache acceleration of content that is served by the WSUS server, install the BranchCache feature on the server and the clients, and ensure that

  the BranchCache service has started. No other steps are necessary.

  In branch offices that have low-bandwidth connections to the central office but high-bandwidth connections to the Internet, the Branch Office feature can also be used. In this case you may want to configure downstream WSUS servers to get

  information about which updates to install from the central WSUS server, but download the updates from Microsoft Update.

• Question 2:

  You need to recommend a Windows Server 2008 R2 server configuration that meets the following requirements:

  -Supports the installation of Microsoft SQL Server 2008

  -Provides redundancy for SQL services if a single server fails

  What should you recommend?

  A. Install a Server Core installation of Windows Server 2008 R2 Enterprise on two servers. Configure the servers in a failover cluster.
  B. Install a full installation of Windows Server 2008 R2 Standard on two servers. Configure Network Load Balancing on the two servers.
  C. Install a full installation of Windows Server 2008 R2 Enterprise on two servers. Configure Network Load Balancing on the two servers.
  D. Install a full installation of Windows Server 2008 R2 Enterprise on two servers. Configure the servers in a failover cluster.
  D. Install a full installation of Windows Server 2008 R2 Enterprise on two servers. Configure the servers in a failover cluster.

  ---

  Fail Over Clustering, which is available on the Enterprise edition (not on standard) will provide fail over as required.

  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 Clustering I-ail over 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 3:

  You need to identify each help desk user who bypasses the new corporate security policy. What should you do?

  A. Configure Audit Special Logon and define Special Groups.
  B. Configure Audit Other Privilege Use Events and define Special Groups.
  C. Configure Audit Sensitive Privilege Use and configure auditing for the HelpDesk group.
  D. Configure Audit Object Access and modify the auditing settings for the HelpDesk group.
  A. Configure Audit Special Logon and define Special Groups.

  ---

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

  This security policy setting determines whether the operating system generates audit events when:

  A special logon is used. A special logon is a logon that has administrator-equivalent privileges and can be used to elevate a process to a higher level.

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

  Special Groups is a new feature in Windows Vista and in Windows Server 2008. The Special Groups feature lets the administrator find out when a member of a certain group logs on to the computer. The Special Groups feature lets an

  administrator set a list of group security identifiers (SIDs) in the registry. An audit event is logged in the Security log if the following conditions are true:

  Any of the group SIDs is added to an access token when a group member logs on.

  Note An access token contains the security information for a logon session. Also, the token identifies the user, the user's groups, and the user's rights.

  In the audit policy settings, the Special Logon feature is enabled.

• Question 4:

  You need to recommend the server configurations for the new failover cluster. The configurations must support the company's planned changes.

  Which two actions should you recommend? (Each correct answer presents part of the solution. Choose two.)

  A. From HyperV Manager on each node, configure one virtual network.
  B. From HyperV Manager on one node, configure two virtual networks.
  C. Install one network adapter on each node. Configure the network adapters to use multiple IP addresses.
  D. Install two network adapters on each node. Configure the network adapters to communicate on separate subnets.
  A. From HyperV Manager on each node, configure one virtual network.
  D. Install two network adapters on each node. Configure the network adapters to communicate on separate subnets.

  ---

  There's only a need for one virtual network because a virtual network is the same as a virtual switch and there is no requirement for a separate switch your requirement is to have inter cluster network traffic isolated from other network traffic by creating separate subnets you can ensure that cluster related traffic remains on one subnet while regular network traffic is carried on the other subnet

• Question 5:

  Your company has a single Active Directory domain. You have 30 database servers that run Windows Server 2008 R2.

  The computer accounts for the database servers are stored in an organizational unit (OU) named Data. The user accounts for the database administrators are stored in an OU named Admin. The database administrators are members of a global group named D_Admins.

  You must allow the database administrators to perform administrative tasks on the database servers. You must prevent the database administrators from performing administrative tasks on other servers.

  What should you do?

  A. Deploy a Group Policy to the Data OU.
  B. Deploy a Group Policy to the Admin OU.
  C. Add D_Admins to the Domain Admins global group.
  D. Add D_Admins to the Server Operators built-in local group.
  A. Deploy a Group Policy to the Data OU.

  ---

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

  Group Policy Planning and Deployment Guide You can use Windows Server 2008 Group Policy to manage configurations for groups of computers and users, including options for registry-based policy settings, security settings, software deployment, scripts, folder redirection, and preferences. Group Policy preferences, new in Windows Server 2008, are more than 20 Group Policy extensions that expand the range of configurable policy settings within a Group Policy object (GPO). In contrast to Group Policy settings, preferences are not enforced. Users can change preferences after initial deployment. For information about Group Policy Preferences, see Group Policy Preferences Overview. Using Group Policy, you can significantly reduce an organization's total cost of ownership. Various factors, such as the large number of policy settings available, the interaction between multiple policies, and inheritance options, can make Group Policy design complex. By carefully planning, designing, testing, and deploying a solution based on your organization's business requirements, you can provide the standardized functionality, security, and management control that your organization needs.

  Overview of Group Policy Group Policy enables Active Directory-ased change and configuration management of user and computer settings on computers running Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP. In addition to using Group Policy to define configurations for groups of users and computers, you can also use Group Policy to help manage server computers, by configuring many server-specific operational and security settings. By using a structure in which OUs contain homogeneous objects, such as either user or computer objects but not both, you can easily disable those sections of a GPO that do not apply to a particular type of object. This approach to OU design, illustrated in Figure 1, reduces complexity and improves the speed at which Group Policy is applied. Keep in mind that GPOs linked to the higher layers of the OU structure are inherited by default, which reduces the need to duplicate GPOs or to link a GPO to multiple containers.

  When designing your Active Directory structure, the most important considerations are ease of administration and delegation.

  

• Question 6:

  You need to recommend a tool to manage the SANs. The tool must support the company's planned changes and technical requirements.

  Which tool should you recommend?

  A. Disk Management
  B. Share and Storage Management
  C. Storage Explorer
  D. Storage Manager for SANs
  D. Storage Manager for SANs

  ---

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

  Storage Manager for SANs is a Microsoft Management Console (MMC) snap-in that helps you create and manage logical unit numbers (LUNs) on Fibre Channel and Internet SCSI (iSCSI) disk drive subsystems that support Virtual Disk Service (VDS) in your storage area network (SAN).

• Question 7:

  You are designing a monitoring solution to log performance on member servers that run Windows Server 2008 R2. The monitoring solution must meet the following requirements for members of the Operations team:

  -Create and modify Data Collector Sets.

  -

  Display log file data and real-time performance data in Performance Monitor.

  You need to design a monitoring solution that meets the requirements.

  What should you recommend? (More than one answer choice may achieve the goal. Select the BEST answer.)

  A. Add members of the Operations team to the Performance Monitor Users group. Assign the Act as part of the operating system user right to the Performance Monitor Users group
  B. Add members of the Operations team to the Performance Log Users group
  C. Add members of the Operations team to the Administrators group
  D. Add members of the Operations team to the Power Users group. Assign the Act as part of the operating system user right to the Power Users group
  B. Add members of the Operations team to the Performance Log Users group

  ---

  A Data Collector Set is the building block of performance monitoring and reporting in Windows Performance Monitor. It organizes multiple data collection points into a single component that can be used to review or log performance. A Data

  Collector Set can be created and then recorded individually, grouped with other Data Collector Set and incorporated into logs, viewed in Performance Monitor, configured to generate alerts when thresholds are reached, or used by other non-

  Microsoft applications. It can be associated with rules of scheduling for data collection at specific times. Windows Management Interface (WMI) tasks can be configured to run upon the completion of Data Collector Set collection.

  Data Collector Sets can contain the following types of data collectors:

  Performance counters

  Event trace data

  System configuration information (registry key values)

  You can create a Data Collector Set from a template, from an existing set of Data Collectors in a Performance

  Monitor view, or by selecting individual Data Collectors and setting each individual option in the

  Data Collector

  Set properties.

  http://technet.microsoft.com/en-us/library/cc722148

  You can create a Data Collector Set from counters in the current Performance Monitor display.

  Membership in the local Performance Log Users or Administrators group, or equivalent, is the minimum required to complete this procedure.

• Question 8:

  Your network consists of a single Active Directory domain. The functional level of the domain is Windows Server 2008 R2. The domain contains 200 Windows Server 2008 R2 servers.

  You need to plan a monitoring solution that meets the following requirements:

  - Sends a notification by email to the administrator if an Application error occurs on any of the servers

  -Uses the minimum amount of administrative effort

  What should you include in your plan?

  A. On one server, create event subscriptions for each server. On the server, attach tasks to the Application error events.
  B. On one server, create an Event Trace Sessions Data Collector Set. On all servers, create a System Performance Data Collector Set.
  C. On all servers, create event subscriptions for one server. On all servers, attach a task for the Application error events.
  D. On all servers, create a System Performance Data Collector Set. On one server, configure the report settings for the new Data Collector set.
  A. On one server, create event subscriptions for each server. On the server, attach tasks to the Application error events.

  ---

  http://technet.microsoft.com/en-us/library/cc749183.aspx http://technet.microsoft.com/en-us/library/cc748890.aspx http://technet.microsoft.com/en-us/library/cc722010.aspx

  Event Subscriptions Applies To: Windows 7, Windows Server 2008 R2, Windows Vista Event Viewer enables you to view events on a single remote computer. However, troubleshooting an issue might require you to examine a set of events stored in multiple logs on multiple computers.

  Windows Vista includes the ability to collect copies of events from multiple remote computers and store them locally. To specify which events to collect, you create an event subscription. Among other details, the subscription specifies exactly which events will be collected and in which log they will be stored locally. Once a subscription is active and events are being collected, you can view and manipulate these forwarded events as you would any other locally stored events.

  Using the event collecting feature requires that you configure both the forwarding and the collecting computers. The functionality depends on the Windows Remote Management (WinRM) service and the Windows Event Collector (Wecsvc) service. Both of these services must be running on computers participating in the forwarding and collecting process. To learn about the steps required to configure event collecting and forwarding computers, see Configure Computers to Forward and Collect Events.

  Additional Considerations You can subscribe to receive events from an existing subscription on a remote computer. Configure Computers to Forward and Collect Events Applies To: Windows 7, Windows Server 2008 R2, Windows Vista

  Before you can create a subscription to collect events on a computer, you must configure both the collecting computer collected (collector) and each computer from which events will be collected (source). Updated information about event subscriptions may be available online at Event Subscriptions.

  To configure computers in a domain to forward and collect events

  1.

  Log on to all collector and source computers. It is a best practice to use a domain account with administrative privileges.

  2.

  On each source computer, type the following at an elevated command prompt:

  

  

• Question 9:

  You are designing a Windows Server 2008 R2 deployment strategy for the Minneapolis campus servers. Which deployment strategy should you recommend?

  A. install from media.
  B. Use a discover image in WDS.
  C. Auto Add From Policy
  D. Use multicast image deployment
  D. Use multicast image deployment

  ---

  Requirements - Bitlocker is needed on all disks in Minneapolis and installations must be done remotely it specifically says they use WDS for deployment. WDS is all about using images so would that not rule out media install? you can do media installs that are unattended but it requirese sending a DVD and corresponding USB key with an answer file to the site and it being inserted into the server. but GDI uses PXE enabled network cards so that would emply media is not used as images would be stored centrally.

  I'm leaning toward Answer B because http://technet.microsoft.com/en-us/library/dd637996%28v=ws.10%29.aspx

  - "A client is on a different subnet and you do not have method of getting PXE to the client (for example, IP helper tables or Dynamic Host Control Protocol (DHCP))."

  I'm gonna make a huge assumption that the Minneapolis servers are on a different subnet, which makes sense because they are all different campuses for a college Multicasting. Provides the ability to transmit install images using multicasting. This includes the ability to automatically disconnect slow clients and the ability to transfer images using multiple streams of varying speeds. To locate these settings, right-click the server in the MMC snap-in, click Properties, and click the Multicast tab.

  Multicast allows organizations to use their network bandwidth more efficiently, allowing an operating system image to be transmitted over the network once to multiple installation clients. For example, if you are deploying 20 computers running Windows Server 2008 R2, you save significant bandwidth in transmitting one installation image across the network (approximately 1.5 GB of data) compared to transmitting all 20 (approximately 60 GB of data). Multicast deployment is supported only in network environments where the routers support multicast transmissions.

  The site in question has 10 servers so Multicast would be a possibility

• Question 10:

  You need to recommend changes to the DFS infrastructure that meet the company's technical requirements.

  What should you recommend implementing in each branch office? (Each correct answer presents part of the solution. Choose two.)

  A. a DFS namespace server
  B. a DFS replica
  C. a standalone DFS namespace
  D. BranchCache in Distributed Cache mode
  E. BranchCache in Hosted Cache mode
  A. a DFS namespace server
  B. a DFS replica

  ---

  When deploying domain-based namespaces, you can add additional namespace servers to host a namespace.

  This has several advantages:

  If one namespace server hosting the namespace goes down, the namespace will still be available to users who need to access shared resources on your network. Adding another namespace thus increases the availability of your namespace.

  If you have a namespace that must be available to users all across your organization but your Active Directory network has more than one site, then each site should have a namespace server hosting your namespace. That way, when users

  in a site need to contact a namespace server for referrals, they can do so locally instead of sending traffic requests to other sites. This improves performance and reduces unnecessary WAN traffic.

  Note that adding additional namespace servers is only supported for domain-based namespaces, not standalone namespaces.

  http://technet.microsoft.com/en-us/library/cc732863%28v=ws.10%29.aspx

  DFS Namespaces enables you to group shared folders located on different servers by transparently connecting them to one or more namespaces. A namespace is a virtual view of

  shared folders in an organization. When you create a namespace, you select which shared folders to add to the namespace, design the hierarchy in which those folders appear, and determine the names that the shared folders show in the

  namespace. When a user views the namespace, the folders appear to reside on a single, high-capacity hard disk. Users can navigate the namespace without needing to know the server names or shared folders hosting the data.

  The path to a namespace is similar to a Universal Naming Convention (UNC) path of a shared folder, such as \\Server1\Public\Software\Tools. If you are familiar with UNC paths, you know that in this example the shared folder, Public, and its

  subfolders, Software and Tools, are all hosted on Server1. Now, assume you want to give users a single place to locate data, but you want to host data on different servers for availability and performance purposes. To do this, you can deploy

  a namespace similar to the one shown in the following figure. The elements of this namespace are described after the figure.

  

  Namespace server. A namespace server hosts a namespace. The namespace server can be a member server or a domain controller.

  Namespace root. The root is the starting point of the namespace. In the previous figure, the name of the root is Public, and the namespace path is \\Contoso\Public. This type of namespace is known as a domain-based namespace, because it begins with a domain name (for example, Contoso) and its metadata is stored in AD DS. Although a single namespace server is shown in the previous figure, a domain-based namespace can be hosted on multiple namespace servers.

  Folder. Folders help build the namespace hierarchy. Folders can optionally have folder targets. When users browse a folder with targets in the namespace, the client computer receives a referral that directs the client computer to one of the folder targets.

  Folder targets. A folder target is a UNC path of a shared folder or another namespace that is associated with a folder in a namespace. In the previous figure, the folder named Tools has two folder targets, one in London and one in New York, and the folder named Training Guides has a single folder target in New York. A user who browses to \\Contoso\Public\Software\Tools is transparently redirected to the shared folder \\LDN-SVR-01\Tools or \\NYC-SVR-01\Tools, depending on which site the user is in.