Evernote Flashcards
You are using the Windows Automated Installation Kit (Windows AIK) to deploy Microsoft Windows 7 in your organization. You configure a technician computer and install the Windows AIK.
You need to create an automated answer file that you can use to perform an automated installation on your reference computer.
What should you do first?
- Copy a Windows image (WIM) file to the reference computer.
- Copy a Windows image (WIM) file to the technician computer.
- Launch Windows System Image Manager (SIM) on the technician computer.
- Run Sysprep on the reference computer.
Copy a Windows image (WIM) file to the technician computer.
You need to copy a WIM file to the technician computer. After you do this, you will use Windows SIM to create an answer file based on that image. You can then copy the answer file to a USB flash drive (UFD) to control the installation on the reference computer. Installation on the reference computer will require the Windows installation DVD and automated answer file.
You should not copy a WIM file to the reference computer. You will install from an image to create the reference computer, but you must first create the answer file.
You should not launch Windows SIM on the technician computer. You will use Windows SIM to create the answer file, but not until after you have copied an image to the technician computer.
You should not run Sysprep on the reference computer. You would not need to do this until after you have installed and configured the reference computer to prepare it for image creation.
You are configuring a small number of remote client computers running Microsoft Windows 7. The client computers are configured to use IPv6 for communication over the Internet. Your local network is configured to use IPv4 and IPv6.
You need to configure end-to-end DirectAccess to give remote clients access to resources on your intranet. Some devices do not support IPv6. You need to ensure that DirectAccess clients can access these devices.
What should you do?
- Configure the remote clients to use IPv4 only.
- Configure the remote clients to use IPv4 and IPv6.
- Deploy multiple DirectAccess servers.
- Deploy a Network Address Translation-Protocol Translation (NAT-PT) device.
Deploy a Network Address Translation-Protocol Translation (NAT-PT) device.
You should deploy a NAT-PT device. This provides DirectAccess clients access to the IPv4-only devices without having to make other changes to the network, clients, or resource servers. The NAT-PT device provides a gateway between the DirectAccess server and the IPv4-only resources.
DirectAccess clients connect to the network using IP Security (IPSec) through one or more DirectAccess servers. If the target network is not configured to support IPv6 traffic, you must use the 6to4 and Teredo IPv6 transition technologies to support DirectAccess traffic across an IPv4 network. Because the network is configured to support both IPv4 and IPv6, this is not required in this situation.
You should not configure remote clients to use IPv4 only or IPv4 and IPv6. This does nothing to get you closer to a solution. DirectAccess requires client computers running Windows 7 and connecting to the target network using IPv6.
You should not deploy multiple DirectAccess servers. Even if you deploy multiple servers, each would provide the same service to the network, providing IPv6 connections for DirectAccess clients. It does nothing to add support for resources that support IPv4 only.
You manage client computers for your organization.
You need to upgrade a computer running Microsoft Windows Vista to Windows 7. The target computer exceeds the minimum hardware requirements for Windows 7. You need to keep the requirements to complete the upgrade to a minimum. You insert the Windows 7 installation DVD.
What should you do next?
- Run Windows Easy Transfer.
- Run a custom installation.
- Run a default installation.
- Run the User State Migration Tool (USMT).
Run a default installation.
You should run a default installation. Setup should launch automatically when you insert the installation DVD. When you run the installation, you will be prompted to upgrade the computer by default.
You should not run Windows Easy Transfer. Windows Easy Transfer is used to transfer files and settings between computers. This is not necessary in this scenario.
You should not run a custom installation. A custom installation is more complicated to run than a default installation and is not required.
You should not run USMT. USMT is used to migrate user profiles, application settings, operating system settings, and so forth to a computer after a clean installation.
You upgraded a computer to Microsoft Windows 7. Several folders on the computer were configured to use Encrypted File System (EFS) encryption. Group Policy allows for self-signed certificates if a certificate authority (CA) is not available.
You need to ensure that all files and folders are encrypted using elliptic curve cryptography (ECC). In the Group Policy Public Key Policies, you configure the Elliptic Curve Cryptography policy to Require.
What else should you do?
- Configure the Elliptic Curve Cryptography policy to Allow.
- Deny the use of self-signed certificates.
- Decrypt encrypted files and folders and re-enable encryption.
- Shut down and reboot the computer.
Decrypt encrypted files and folders and re-enable encryption.
You should decrypt encrypted files and folders and then re-enable encryption. Setting Elliptic Curve Cryptography to Require requires ECC encryption for all new encryption, but files and folders encrypted under an earlier Windows version are still encrypted under RSA encryption.
You should not configure the Elliptic Curve Cryptography policy to Allow. This would allow the use of both ECC and RSA encryption for new encryption.
You should not deny the use of self-signed certificates. Self-signed certificates can be used for ECC encryption. Windows 7 supports 256-bit, 384-bit, and 531-bit ECC certificates.
You should not shut down and reboot the computer. This would force application of new Group Policy settings, but it does not change the existing files.
You have a computer running Microsoft Windows 7. Users access the computer using an account that is a member of the Users group.
SueS attempts to execute an application, but she receives access denied errors.
You need to enable SueS to execute the application.
What should you do?
- Select Run this program as an administrator on the Compatibility tab of the program.
- Add SueS to the Administrators group. Select Run this program as an administrator on the Compatibility tab of the program.
- Set the Compatibility mode to Windows XP on the Compatibility tab of the program.
- Create a shim and install it in the compatibility database.
Add SueS to the Administrators group. Select Run this program as an administrator on the Compatibility tab of the program.
You should add SueS to the Administrators group and select Run this program as an administrator on the Compatibility tab of the program. Windows 7 imposes stricter application security than earlier Windows operating systems. If an application needs administrator permission, you will need to enable the Run this program as an administrator option on the Compatibility tab of the program. However, a program can only run as an administrator if the user who is executing it is a member of the Administrators group. Therefore, you will need to add SueS to the Administrators group.
You should not only select Run this program as an administrator on the Compatibility tab of the program. You also need to add SueS to the Administrators group to permit permission elevation.
You should not set the Compatibility mode to Windows XP on the Compatibility tab of the program. The Compatibility mode allows you to configure an environment that emulates an older version of Windows when executing an application. However, it does not circumvent security restrictions.
You should not create a shim and install it in the compatibility database. You can create a shim and install it in the compatibility database to act as a layer of abstraction between an incompatible program feature and Windows 7. For example, if the program did not really require administrative permission, but checked for it, you could create a shim for the function that checks permission that always returns true. However, in this case, the application actually requires administrative permission, so you cannot correct the problem with a shim. You cannot use a shim to circumvent Windows 7 User Account Control (UAC).
A user complains of system problems after a printer device driver is updated on a computer running Microsoft Windows 7. The user did not notice any problems with the original printer driver. You have the user restart the computer, but the problem continues.
You need to correct the problem as quickly as possible. The user needs access to the printer.
What should you do?
- Disable the device through the Device Manager.
- Open the device properties and roll back the device driver.
- Manually reinstall the original device driver.
- Restart the computer and choose the Last Known Good Configuration.
Open the device properties and roll back the device driver.
You should open the device properties and roll back the device driver. This will force the computer to revert to the previous version of the device driver. Because the user did not notice any problems with the original device driver, this should correct the problem and leave the printer available to the user.
You should not disable the device through the Device Manager. This will leave the printer unavailable. You may be prompted to restart the computer after disabling a device driver.
You should not manually reinstall the original device driver. If the original device driver shipped with Windows 7, you might not have the file available for manual installation. Also, this option is more time-consuming than rolling back the driver.
You should not restart the computer and choose the Last Known Good Configuration. This would not make any difference in this situation. Because the computer was able to successfully restart with the new device driver, the last known good configuration has been updated to include that device driver.
Your network is configured as a central office and two remote branch offices. Each office is configured as two subnetworks. You want to implement Hosted Cache mode BranchCache to reduce communication over remote links.
You need to determine the minimum number of Hosted Cache servers required to implement BranchCache throughout the network. You need to deploy only required servers.
What should you do?
- Deploy one Hosted Cache server.
- Deploy two Hosted Cache servers.
- Deploy four Hosted Cache servers.
- Deploy five Hosted Cache servers.
Deploy two Hosted Cache servers.
You should deploy two Hosted Cache servers, one for each remote office. The content server (or servers) will be deployed in the central office. Each branch office requires its own Hosted Cache server. The Hosted Cache server can provide content for all of the subnets configured in the remote office.
You should not deploy one Hosted Cache server. You must have at least one in each remote office.
You should not deploy four or five Hosted Cache servers. There is no need to deploy multiple Hosted Cache servers in each of the remote offices. There is also no need to deploy one in the central office.
You set up a computer running Microsoft Windows 7 and custom applications. You plan to use the computer for testing applications.
You need to be able to restore back to the custom installation quickly if problems occur. You need to be able to control the recovery through the Windows Recovery Environment (RE) using Windows RE manual tools.
First, you need to create the recovery image.
What should you do?
- Run ImageX from a command prompt.
- Use Windows Backup.
- Open the Windows RE menu during startup.
- Launch Windows RE from the installation DVD.
Use Windows Backup.
You should create a full backup using Windows Backup. You need to create the backup on a disk partition other than the system’s startup partition. For example, you can create the backup on an external hard disk or in a network location.
You should not run ImageX from a command prompt. ImageX is used to create a Windows installation image (WIM) file. In this scenario, you need a backup file rather than an image file.
You should not launch Windows RE. You use Windows Backup, not Windows RE, to create the copy. When you need to restore the computer, you would then launch Windows RE (from the hard disk or installation DVD) and run a complete PC restore from the manual tools menu.
You have a computer running Microsoft Windows Vista Ultimate.
You are planning to upgrade the computer to Windows 7.
Which edition or editions of Windows 7 support a direct upgrade from Windows Vista Ultimate?
- Professional and Ultimate
- Enterprise and Ultimate
- Professional, Enterprise, and Ultimate
- Ultimate
Ultimate
You can only directly upgrade from Windows Vista Ultimate to Windows 7 Ultimate. Supported upgrade paths do not affect the availability of upgrade pricing. You can purchase Windows 7 for an upgrade price even if your current edition of Windows Vista does not support an upgrade to the edition of Windows 7 you purchase. However, you would need to migrate settings and perform a Custom installation instead of performing an upgrade.
You cannot directly upgrade to Windows 7 Professional. Only Windows Vista Business can be directly upgraded to Windows 7 Professional.
You cannot directly upgrade to Windows 7 Enterprise. Only Windows Vista Business and Windows Vista Enterprise can be directly upgraded to Windows 7 Enterprise.
You are configuring a computer running Microsoft Windows 7 for use as a public terminal.
The computer is configured to log on automatically as a local standard user. You want to prevent users from being able to run administrative programs and make changes to the computer.
What should you do?
- Disable User Account Control (UAC).
- Disable Secure Desktop.
- Configure local security policies for standard users to automatically deny elevation requests.
- Configure User Account Control (UAC) prompts to elevate without prompting.
Configure local security policies for standard users to automatically deny elevation requests.
You should configure local security policies for standard users to automatically deny elevation requests. This policy is used to prevent user privilege escalation when a standard user attempts to run an administrator application, effectively preventing standard users from running administrator applications. An administrator application is one that requires administrator privileges to make changes to a computer.
You should not disable UAC. You can disable UAC by setting the UAC Control Panel slider to Never notify. Users or applications would be able to make changes to the computer without any notification displaying.
The UAC Control Panel slider supports four settings:
* Always notify on every system change (High) - Secure desktop notification is displayed if changes are attempted by a user or application.
* Notify me only when programs try to make changes to my computer (Medium) - User changes, such as changing Windows settings, do not generate notifications. Attempts made by applications by computers do generate a Secure Desktop notification.
* Notify me only when programs try to make changes to my computer, without using the Secure Desktop (Low) - This is the same as the medium setting, except prompts appear on the normal desktop instead of using Secure Desktop.
* Never notify (Off) - UAC is disabled.
You should not disable Secure Desktop. This causes notifications to display on the normal desktop instead of secure desktop, but users can still choose to make modifications.
You should not configure UAC prompts to elevate without prompting. This is a local security policy setting and applies only when a user is logged on as a local administrator. The setting causes administrator applications and setup programs to automatically run under the administrator security context, without being blocked or displaying any warning notification, when the user is logged on as a local administrator.
You are defining application restriction policies for computers running Microsoft Windows 7.
You create application execution rules through AppLocker. You need to determine how these rules will impact standard users. You need to have minimal impact on users’ access to applications while testing your application rules.
What should you do?
- Configure rule enforcement mode as Not configured.
- Create and apply default application rules.
- Create publisher rules for each of the applications tested.
- Configure rule enforcement mode as Audit only.
Configure rule enforcement mode as Audit only.
You need to configure rule enforcement mode as Audit only. This lets you determine what the impact of the rules will be without directly affecting users’ access to applications. After you have determined if the rules work as expected, you can change the rule enforcement mode to Enforce rules.
You should not configure rule enforcement mode as Not configured. This is the default rule enforcement mode. This setting does not audit the impact of the rules on users. Also, if any linked Group Policy object (GPO) already exists, it will apply instead of the AppLocker rules.
You should not create and apply default application rules. Default rules enable all users to run the programs in the default Program Files folder and in the Windows folder. They are not used for testing custom rules.
You should not create publisher rules for each of the applications tested. A publisher rule is used to enable rules to apply to an application after an upgrade rather than having to create a new rule each time you upgrade an application.
Your environment includes several Windows 7 computers that have WS-Management protocol enabled. Your technician computer is also running Windows 7.
You need to execute a PowerShell command on all the computers from your technician computer.
What should you do?
- Run Enter-PSSession.
- Run Invoke-Command.
- Run Enable-PSRemoting.
- Run Invoke-Expression.
Run Invoke-Command.
You should run Invoke-Command. The Invoke-Command PowerShell cmdlet allows you to list the computers on which to run a specific command. The command is then executed on the computers in a “fan-out” configuration. Invoke-Command requires that WS-Management protocol be enabled. You enable WS-Management by running the Enable-PSRemoting cmdlet.
You should not run Enter-PSSession. The Enter-PSSession cmdlet is used to initiate an interactive PowerShell session with one computer. During an interactive session, you can execute multiple commands.
You should not run Enable-PSRemoting. You use Enable-PSRemoting to enable WS-Management on a computer. The computers already have WS-Management enabled.
You should not run Invoke-Expression. The Invoke-Expression cmdlet can only be used to execute commands on a local computer.
You create a weekly system image backup of a Microsoft Windows 7 computer and store the backup on a DVD.
The computer boots, but Windows 7 will not start.
You need to restore the system image.
What should you do?
- Boot from the DVD that contains the system image backup.
- Boot from a DVD that contains Windows Preinstallation Environment (PE)
- Press the F8 key as the computer restarts and select Repair your system.
- Start the computer by using Recovery Console.
Press the F8 key as the computer restarts and select Repair your system.
You should press the F8 key as the computer restarts and select Repair your system. Pressing the F8 key during startup causes the Advanced Boot Menu to be displayed. You can select Repair your system to display the System Recovery options menu. One choice on this menu is to restore the computer using the system image backup. All changes made since the backup will be lost unless they can be recovered from other backups. Another option is to boot from the installation DVD or a system repair disc.
You should not boot from the DVD that contains the system image backup. The system image backup is not bootable. If you want to create a bootable DVD that can be used for recovery, you need to create a system repair disc.
You should not boot from a DVD that contains Windows PE. Windows PE is used when installing Windows 7 from an installation image, not when recovering to a system image backup.
You should not start the computer by using Recovery Console. Recovery Console was used in Windows XP to allow you to run certain commands. It has been replaced by the System Recovery options, which provide more robust tools for troubleshooting and resolving a problem.
You have a Microsoft Windows 7 computer.
You need to prevent the Recycle Bin from being displayed on the desktop.
What should you do?
- Right-click the Recycle Bin icon and choose Properties.
- Right-click the Desktop and choose Personalize.
- Right-click the Desktop and display View options.
- Right-click the Desktop and choose Gadgets.
Right-click the Desktop and choose Personalize.
You should right-click the Desktop and choose Personalize to open Personalization in the Control Panel. From the Personalization window, you can select Change desktop icons to display a dialog box that lets you check and uncheck default desktop icons, such as Recycle Bin.
You should not right-click the Recycle Bin icon and choose Properties. The Recycle Bin Properties dialog box allows you to configure the amount of disk space the Recycle Bin can use and whether a confirmation dialog box should be displayed when a user empties the Recycle Bin.
You should not right-click the Desktop and display View options. The View menu allows you to change how the desktop icons are arranged and the icon size. You cannot remove individual icons by using the View menu.
You should not right-click the Desktop and choose Gadgets. Gadgets are mini-programs, such as Weather and Calendar, that you can display on the Desktop. In Windows Vista, gadgets could only appear on the Sidebar. The Recycle Bin is not a gadget.
You are configuring your network to support both IPv4 and IPv6. You are currently documenting assigned addresses.
A computer running Windows 7 has the following address:
FE80::2AA:FF:FE3F:2A1C
How is this address used?
- To communicate between subnets on the same network
- To provide a globally unique unicast address
- To provide loopback communications for testing
- To communicate with other hosts on the same subnet
To communicate with other hosts on the same subnet
The address is used to communicate with other hosts on the same subnet. This is an example of a link-local address, which is used like an Automatic Private IP Addressing (APIPA) IPv4 address and is used for local communication only. You can recognize the address as a link local address by the FE80 prefix. The remaining address values are taken from the computer’s Media Access Control (MAC) address.
The address is not used to communicate between subnets on the same network. This would require a site-local address, which would have a prefix of FEC0.
The address is not used to provide a globally unique unicast address. This would be an address in a format similar to the following:
2001:DB8:2A3C:F282:2AA:FF:FE3F:2A1C
The value 2001:DB8:2A3C is a global routing address for the site. F282 represents a subnet on that site. The remaining address value, 2AA:FF:FE3F:2A1C, identifies a unique host on that subnet, based on the MAC address.
The address is not used to provide loopback communications for testing. An address of ::1 is used for IPv6 loopback testing.
Your Microsoft Windows 7 computer is a domain member that has a wireless network adapter.
Your wireless router is configured to use Temporal Key Integrity Protocol (TKIP) encryption. It is not configured to use a pre-shared key.
You need to configure the computer’s wireless connection to use the strongest possible security.
Which security type should you use?
- WPA2-Personal
- WPA2-Enterprise
- 802.1x
- WPA-Personal
WPA2-Enterprise
You should use WPA2-Enterprise. The Wi-Fi Protected Access (WPA2) Enterprise security type supports either TKIP or Advanced Encryption Standard (AES) for an encryption protocol. When you use WPA2, you have the choice of using either an 802.1x server or a pre-shared key for authentication. In this scenario, you know that the access point does not have a pre-shared key. Therefore, the network must have an 802.1x server. WPA-Enterprise is another security type that supports 802.1x authentication and both TKIP and AES encryption. WPA2 is more secure than WPA, but it is not supported by older wireless access points.
You should not use WPA2-Personal or WPA-Personal. These security types require authentication using a pre-shared key.
You should not use 802.1x as the security type. The 802.1x security type only supports Wired Equivalent Privacy (WEP) encryption. It can use Microsoft Protected Extensible Authentication Protocol (PEAP) or certificate authentication, so it does not require a pre-shared key.
You upgrade a computer running Microsoft Windows XP to Windows 7. You use Windows Easy Transfer to transfer files and settings to the new installation.
You need to make the applications that were running on the computer before you installed Windows 7 available to the computer’s user.
What should you do?
- Run User State Migration Tool (USMT).
- Reinstall the user applications.
- Reboot the computer.
- Run the BCDedit command.
Reinstall the user applications.
You should reinstall the user applications. Windows 7 does not support a direct upgrade path from Windows XP. After installing Windows 7, you must reinstall any applications that you still want to have available.
You should not run USMT. USMT is used to migrate user profiles, application settings, operating system settings, and so forth to a computer after a clean installation. In this situation, it does not migrate user applications.
You should not reboot this computer. This does not do anything to make the applications available.
You should not run the BCDedit command. BCDedit lets you manage the boot options in a multiple-boot installation and has nothing to do with migrating application support.
A Microsoft Windows 7 computer is configured to use IPv6. The computer receives its IP configuration from a Dynamic Host Configuration Protocol (DHCP) server.
The router normally used to reach a branch office fails. You need to configure the computer to use a different route.
Which utility should you use?
- Ipconfig
- Netsh
- Pathping
- Tracert
Netsh
You should use Netsh. The Netsh interface ipv6 command can be used to view and modify the IPv6 routing table.
You should not use Ipconfig. The Ipconfig utility can be used to view IPv4 and IPv6 configuration settings, to release and renew IPv4 or IPv6 addresses, and to flush the Domain Name System (DNS) cache. It cannot be used to modify the routing table.
You should not use Pathping. The Pathping utility is used to test connectivity. It returns the addresses of each router along the path to a destination.
You should not use Tracert. The Tracert utility is used to test connectivity. It returns information about the time it takes to traverse each hop to a destination, as well as the IP address of each router along the path.
You have a Windows 7 computer in a homegroup. There is also one Windows Vista computer on the network. The Windows 7 computer contains files that should be accessible for Read access by all other users in the homegroup. The files are located in the FamilyInfo folder in your My Documents folder.
You need to enable other users in the homegroup to access the folder.
What should you do?
- Select the FamilyInfo folder and choose Share with | Homegroup (Read).
- Move the FamilyInfo folder to the Public Documents library.
- In Advanced Sharing, grant Everyone Read access.
- In Advanced Sharing, grant Homegroup Read access.
Select the FamilyInfo folder and choose Share with | Homegroup (Read).
You should select the FamilyInfo folder and choose Share with | Homegroup (Read). When a computer belongs to a homegroup, users can access files in any Public folder by default. You can allow users who log on to other computers in the homegroup to access other files by using the Share with command. To allow users Read-only access, select Share with | Homegroup (Read).
You should not move the FamilyInfo folder to the Public Documents library. The Public Documents library allows Read/Write access by default.
You should not grant Everyone Read access in Advanced Sharing. Advancing Sharing is used to configure file share permissions for resources shared through traditional file sharing methods. When Everyone is granted Read access, any authenticated user can access the files, not just members of the homegroup.
You should not grant Homegroup Read access in Advanced Sharing. Homegroup is not accessible through Advanced Sharing. To grant permission to a homegroup, you need to use the Share with menu item.
You are managing several computers running Microsoft Windows 7. Several users have removable USB hard disks to provide additional storage.
You need to ensure that data on removable hard disks is encrypted. The data on the hard disks should be readable by computers running Windows XP or Windows Vista, as well as Windows 7.
What should you do?
- Format the removable disks as NTFS and require BitLocker on the disks through Group Policy.
- Format the removable disks as NTFS and require Encrypting File System (EFS) on the disks through Group Policy.
- Format the removable disks as FAT32 and require BitLocker on the disks through Group Policy.
- Format the removable disks as FAT32 and require Encrypting File System (EFS) on the disks through Group Policy.
Format the removable disks as FAT32 and require BitLocker on the disks through Group Policy.
You should format the removable disks as FAT32 and require BitLocker on the disks through Group Policy. You can require the use of BitLocker on removable disks, referred to as BitLocker To Go in this use, through Group Policy. To make the data accessible to older versions of Windows, you must format the disk as FAT or FAT32 and must include the BitLocker To Go Reader on the hard disk.
You should not format the removable disks as NTFS. When you apply BitLocker To Go to removable hard disks formatted as NTFS, it cannot be read by older versions of Windows.
You cannot require EFS encryption through Group Policy.
Client computers running Microsoft Windows 7 are configured to support BranchCache in Hosted Cache mode. BranchCache is configured through linked Group Policy objects (GPOs).
You need to convert the clients to support BranchCache in Distributed Cache mode. You run the following on each of the client computers:
netsh branchcache set service mode=DISTRIBUTED
You need to finish configuring Distributed Cache mode support.
What should you do?
- Configure each client’s firewall to enable WS-Discovery protocol.
- Manually start the BranchCache service on each computer.
- Enable the BranchCache for remote files feature.
- Unlink the GPOs configuring clients for hosted mode.
Unlink the GPOs configuring clients for hosted mode.
You should unlink the GPOs configuring clients for hosted mode. Configuration settings applied through linked GPOs take precedence over configuration changes made when you run netsh.
You should not configure each client’s firewall to enable WS-Discovery protocol. Windows Firewall is configured automatically when you run netsh.
You should not manually start the BranchCache service on each computer. There is no need to do this manually.
You should not enable the BranchCache for remote files feature. This feature is available only on server computers configured as file servers and is only necessary on files servers also supporting BranchCache.
A computer is running Microsoft Windows Vista Home Premium.
You need to install Windows 7 Professional on the computer. You must preserve user configuration settings and applications. You must perform the installation using the least amount of effort.
What should you do first?
- Start the computer in Windows Vista. Insert the installation DVD and choose Upgrade.
- Start the computer from the DVD. Choose Custom.
- Start the computer in Windows Vista. Insert the installation DVD and run Migsetup.exe.
- Start the computer from the DVD. Choose Upgrade.
Start the computer in Windows Vista. Insert the installation DVD and run Migsetup.exe.
You should start the computer in Windows Vista, insert the installation DVD, and run Migsetup.exe. You cannot directly upgrade a computer running Windows Vista Home Premium to Windows 7 Professional by performing an upgrade installation. You must perform a custom installation. However, because you need to preserve settings, you will need to first migrate them using Easy Transfer (Migsetup.exe). You will need to store the files on an external hard drive, such as a Universal Serial Bus (USB) flash drive, or you will need to use an Easy Transfer Cable.
You should not start the computer in Windows Vista, insert the installation DVD, and choose Upgrade. You would complete these steps if this upgrade path were supported. You can only directly upgrade to either Windows 7 Home Premium or Windows 7 Ultimate from Windows Vista Home Premium edition by performing an upgrade installation.
You should not start the computer from the DVD and choose Custom. You need to migrate the settings before you perform the installation.
You should not start the computer from the DVD and choose Upgrade. You can only directly upgrade to either Windows 7 Home Premium or Windows 7 Ultimate from Windows Vista Home Premium by performing an upgrade installation.
You upgrade several computers to Microsoft Windows 7. All of the computers are part of the same Active Directory domain.
You must support an application with a known compatibility problem after upgrading the computers. You need to create and deploy a custom compatibility mode to correct the problem. You need to keep the effort needed to correct the problem to a minimum.
What should you do first?
- Run Sdbinst on each of the upgraded computers.
- Run the Standard User Analyzer (SUA) wizard on each of the upgraded computers.
- Launch the Create a Custom Compatibility Mode Wizard.
- Create a new compatibility database.
Create a new compatibility database.
You should create a new compatibility database. Before you can create and distribute a custom compatibility mode, you must first create a custom compatibility database as a destination. You then distribute the fixes contained in the compatibility mode as part of the custom database.
A compatibility mode is a set of compatibility fixes. You can create a compatibility mode by copying an existing compatibility mode and then modifying it or by creating a new mode and adding individual fixes.
You should not run Sdbinst on each of the upgraded computers. The Sdbinst command is used to distribute the custom compatibility database after it is completed.
You should not run the SUA wizard on each of the upgraded computers. The SUA wizard is used to detect User Account Control (UAC)-related compatibility issues. The scenario states that you are working with a known compatibility issue.
You should not launch the Create a Custom Compatibility Mode Wizard. You must create the custom compatibility database first. You will then select the compatibility database before launching the Create a Custom Compatibility Mode Wizard.
You are configuring a computer to boot from a virtual hard disk (VHD). The VHD must be installed using an image located on a network share.
You create a VHD and configure it with a primary partition.
What should you do next?
- Start the computer by using Windows PE.
- Detach the VHD.
- Run ImageX with the /apply option.
- Run Bcdboot.
Run ImageX with the /apply option.
You should run ImageX with the /apply option. After you configure the partitions, you need to apply the image. You can apply the image by running ImageX with the /apply option.
You do not need to start the computer using Windows Preinstallation Environment (PE). Windows PE is used when applying an image to a physical hard disk. You can apply an image to a virtual hard disk when you are booted to Windows 7.
You should not detach the VHD. The VHD needs to be attached to apply the image.
You should not run Bcdboot. You will run Bcdboot on the target computer after you apply the image on the VHD, copy the VHD to the target computer, and attach the VHD. The Bcdboot command copies the boot files in the VHD to the system partition on the target computer.
You upgrade a computer from Microsoft Windows Vista to Windows 7.
You try to run one of the applications and it terminates unexpectedly.
You need to resolve the problem.
What should you try first?
- Set the Compatibility mode to Windows Vista.
- Uninstall and reinstall the application.
- Set the Run this program as an administrator option.
- Set the Disable visual themes option.
Set the Compatibility mode to Windows Vista.
You should set the Compatibility mode to Windows Vista. The Compatibility mode option on the Compatibility tab of an application’s properties dialog box allows you to configure an application to run in an environment that emulates an earlier version of Windows. In this case, because you know the program operated under Windows Vista, you should try to set the Compatibility mode to Windows Vista.
You should not uninstall and reinstall the application as the first thing to try. Upgrading Windows preserves application settings. You should not need to reinstall the application.
You should not set the Run this program as an administrator option. The Run this program as an administrator option is used when you need to support an application that requires administrative permissions. You would also need to add users who need to run the application to the Administrators group.
You should not set the Disable visual themes option. You would set this compatibility option if you were experiencing problems with the title bar or menu bar of an application.
You are deploying Microsoft Windows 7 on your network. Computers running Windows 7 will initially run the same applications as other clients already deployed on your network.
You need to ensure that existing Software Restriction Policies continue to be applied to computers running Windows 7 as you define and deploy AppLocker rules. Software Restriction Policies should continue to apply to any client running Windows Vista that you upgrade to Windows 7, along with new AppLocker rules. You plan to manage AppLocker rules through Group Policy objects (GPOs). You need to keep the administrative effort necessary to a minimum.
What should you do?
- Define AppLocker rules in the same GPO as existing Software Restriction Policies.
- Define AppLocker rules in a new GPO, separate from Software Restriction Policies.
- Unlink any GPOs containing Software Restriction Policies before defining AppLocker rules, and then relink when finished.
- Replace the Software Restriction Policies with AppLocker rules.
Define AppLocker rules in a new GPO, separate from Software Restriction Policies.
You should define AppLocker rules in a new GPO, separate from Software Restriction Policies. You can have both AppLocker rules and Software Restriction Policies, but if you define the AppLocker rules in the same GPO, only the AppLocker rules will apply. Software Restriction Policies must be maintained in a separate GPO.
In most network environments, you will likely want to define both Software Restriction Policies and AppLocker rules. AppLocker rules provide more detailed control over applications, but currently apply to Windows Server 2008 and Windows 7 only. Older versions of Windows require Software Restriction Policies.
You should not define AppLocker rules in the same GPO as existing Software Restriction Policies. If you do this, only AppLocker rules will apply, even if there is no conflict with the Software Restriction Policies.
You should not unlink any GPOs containing Software Restriction Policies before defining AppLocker rules, and then relink when finished. This is not necessary and will not change the final result.
You should not replace the Software Restriction Policies with AppLocker rules. While this is possible, it would be more work than necessary to meet your application restriction management requirements.
Your company has a large number of computers running Microsoft Windows 7.
When troubleshooting a problem on any of the computers, you want to be able to easily view a log of application errors, hangs, and service control events that have occurred in the past 24 hours.
What should you do?
- Use Event Viewer to create a filter on the System log and save the filter to a custom view.
- In Event Viewer, choose View | Show Analytic and Debug Logs.
- Use Event Viewer to create and export a custom view.
- In System Information, choose Windows Error Reporting.
Use Event Viewer to create and export a custom view.
You should use Event Viewer to create and export a custom view. You can create a custom view that contains events from one or more event logs. These events can be filtered by source, user, date, and event type. You can export a custom view and import it into another computer.
You should not use Event Viewer to create a filter on the System log and save the filter to a custom view. The System log does not contain Application Hang or Application Error events.
You should not launch Event Viewer and choose View | Show Analytic and Debug Logs. The Analytic and Debug logs provide extremely detailed event information for advanced troubleshooting and application debugging.
You should not choose Windows Error Reporting in System Information. Although application hangs and errors are displayed in this report, service control events are not. Also, you cannot limit the information shown to only the past 24 hours.
You try to start a Windows 7 computer and receive an error that a system file is damaged. You cannot access the Advanced Boot Options.
You need to recover from the failure.
What should you try first?
- Start the computer by using the installation DVD. Select Repair your computer. Select Startup Repair.
- Start the computer by using a system repair disc. Select System Restore.
- Start the computer by using a system repair disc. Select System Image Recovery.
- Start the computer by using the installation DVD. Perform a custom installation.
Start the computer by using the installation DVD. Select Repair your computer. Select Startup Repair.
You should start the computer by using the installation DVD, select Repair your computer, and select Startup Repair. The Startup Repair tool scans your system and locates missing or damaged operating system files. It can automatically correct problems caused by missing or damaged system files. You can access the Startup Repair tool from the System Recovery options menu, which is available by pressing the F8 key during startup and choosing Repair your computer, starting from the installation DVD and choosing Repair your computer, or starting from a system repair disc.
You should not start the computer by using a system repair disc and select System Restore. System Restore allows you to restore the operating system to a restore point. A restore point is created when a driver or application is installed. You can also create restore points manually. In this case, you do not know when the problem occurred or if a restore point was created before the change that caused the problem. Therefore, you should first try Startup Repair. If Startup Repair does not resolve the problem, the next step is to try System Restore.
You should not start the computer by using a system repair disc and selecting System Image Recovery. This option allows you to restore the system using a system image backup. All changes made since the backup will be lost, so this option should be used only if Startup Repair and System Restore fail to correct the problem.
You should not start the computer by using the installation DVD and performing a custom installation. A custom installation is a clean installation. All system configuration settings and applications will be lost.
You are using a manual network migration to migrate a computer from Microsoft Windows XP to Windows 7.
The computer is currently configured for Internet Connection Sharing (ICS). You need to ensure that the computer can be used to share its Internet connection to the network after migration. You need to keep the procedures necessary to accomplish this to a minimum.
What should you do?
- Use Windows Easy Transfer to transfer computer settings.
- Use User State Migration Tool (USMT) to run a default transfer.
- Use User State Migration Tool (USMT) with a custom Config.xml file.
- Use User State Migration Tool (USMT) and manually configure ICS after migration.
Use User State Migration Tool (USMT) and manually configure ICS after migration.
You need to use USMT and manually configure ICS after migration. The USMT ScanState and LoadState commands do not migrate ICS configuration settings from Windows XP to Windows 7 because of the potential security risk. ICS is supported, but it must be configured manually after migration.
You should not use Windows Easy Transfer to transfer computer settings. A manual network migration refers to using ScanState to transfer settings to a network server and LoadState to retrieve the settings from the server. Windows Easy Transfer is not used in this scenario, and even if it were used, it would not migrate ICS settings.
You should not use USMT to run a default transfer as your only action. You will still need to manually configure ICS.
You should not use USMT with a custom Config.xml file. A custom Config.xml file is used to identify components that you do not want to migrate.
You are configuring a Microsoft Windows 7 computer for a user who telecommutes. The user needs to be able to access the corporate network through a DirectAccess server.
The wireless network adapter driver settings are shown in the exhibit.
What change must you make to support a DirectAccess connection?
- Enable Internet Protocol Version 6 (TCp/IPv6).
- Enable QoS Packet Scheduler.
- Disable Virtual Machine Network Services.
- Disable File and Printer Sharing for Microsoft Networks.
Enable Internet Protocol Version 6 (TCp/IPv6).
You should enable IPv6. DirectAccess relies on IPv6. With a DirectAccess connection, packets are tunneled through an Internet connection and secured using IP Security (IPSec).
You do not need to enable the Quality of Service (QoS) Packet Scheduler. The QoS Packet Scheduler provides prioritized delivery for packets that require guaranteed delivery time. DirectAccess does not depend on QoS.
You do not need to disable the Virtual Machine Network Service. The Virtual Machine Network Service is used to establish network communication with a Virtual PC. It is not related to DirectAccess.
You do not need to disable File and Printer Sharing for Microsoft Networks. There are no limitations on sharing files or printers when connected to a DirectAccess server.
You have a computer running Microsoft Windows 7.
You want to perform a weekly backup that stores the latest configuration settings, files, and installed applications. The screen to configure the backup is shown in the exhibit.
Which option or options should you select?
- Program Files
- Local Disk (C:)
- Program Files and ProgramData.
- Include a system image of drives: System Reserved, (C:).
Include a system image of drives: System Reserved, (C:).
You should select Include a system image of drives: System Reserved, (C:). The only option that allows you to back up program files is to create a system image. The drawback to creating a system image is that you cannot selectively restore files. Therefore, you might want to supplement a system image backup with periodic full backups of data files.
You should not select Program Files. Even if the Program Files folder is selected, executable files within the Program Files folder or subfolders are ignored during backup.
You should not select Local Disk (C:). Selecting this option would cause all data files on volume C or any subfolder of volume C to be backed up. However, executable files will not be backed up.
You should not select Program Files and ProgramData. Even if the Program Files folder is selected, executable files within the Program Files folder or subfolders are ignored during backup.
You use a computer that was migrated from Microsoft Windows XP to Windows 7. A full backup of the computer was created by using Ntbackup before migration.
You need to recover data files that were backed up using Ntbackup. You need to recover the files as quickly as possible. You have copied the backup file to the local hard disk.
What should you do first?
- Launch Windows Backup and Restore.
- Install Windows Removable Storage Management (RSM).
- Install the Ntbackup utility.
- Launch System Recovery.
Install Windows Removable Storage Management (RSM).
You need to install RSM first. You must use Ntbackup to restore the files, but you must first install RSM before the computer will support Ntbackup.
You should not launch Windows Backup and Restore. Windows Backup and Restore cannot be used to restore from a backup made with Ntbackup.
You should not install the Ntbackup utility as your first action. You will need Ntbackup, but you need to install RSM before you install Ntbackup.
You should not launch System Recovery. System Recovery cannot be used to restore from a backup made with Ntbackup.
You are preparing to deploy Microsoft Windows 7 to a small number of computers. You plan to use a network share as your installation source.
You plan to use a custom unattended answer file to configure most of the installation settings. You need to be able to select the destination volume when you apply the image to the destination computer. You will use bootable Windows PE media to boot the destination computers.
What should you do?
- Create and apply an image using ImageX.
- Create an image using ImageX and apply the image using Windows Setup.
- Use the Windows 7 installation DVD distribution image and apply the image using ImageX.
- Use the Windows 7 installation DVD distribution image and apply the image using Windows Setup.
Create an image using ImageX and apply the image using Windows Setup
You should create an image using ImageX and apply the image using Windows Setup. You can boot the destination in Windows PE and then run Setup. By using Setup to apply the image, you have the option of selecting the destination volume.
You should not create and apply an image using ImageX. This would require you to install to the volume from which the image was created.
You should not use the DVD image for distribution through a network share. A DVD image is not designed for distribution in this manner.
You manage computers in a Microsoft Windows Active Directory domain.
You are setting up your network to support device driver installation on client computers running Microsoft Windows 7. You have configured client computers to search a shared network folder for device drivers in that folder. You configure a device setup class for the driver in the Allow limited users to install drivers for these device classes policy.
When new hardware is distributed to the users, they complain that they still cannot install the device drivers. You need to enable the users to install the appropriate drivers. You need to minimize the potential impact on network and local computer security.
What should you do?
- Add the users to the Domain Admins group.
- Add each user to the computer’s local Administrators group.
- Provide users with a password to let them execute a command as an administrator.
- Sign the driver package with a certificate present in the computer’s Trusted Publishers certificate store.
Sign the driver package with a certificate present in the computer’s Trusted Publishers certificate store.
You should sign the driver package with a certificate present in the computer’s Trusted Publishers certificate store. For a user to be able to install a driver from a network share, the computer must be configured to search that share for the driver, you must configure a device setup class for the driver in the Allow limited users to install drivers for these device classes policy, and you must sign the driver with a trusted certificate.
You should not add the users to the Domain Admins group or the local Administrators group. Either action would grant the users more permissions than necessary and could result in a security risk.
You should not provide users with a password to let them execute a command as an administrator. This would not enable them to automatically install the device driver. It would also let them run utilities in an administrator context, which is a security risk.
You have a computer running Microsoft Windows 7 Professional.
You need to browse an Internet Web site without storing any data locally.
What should you do?
- Turn on SmartScreen Filter.
- Turn on InPrivate Filtering.
- Turn on Work Offline.
- Turn on InPrivate Browsing.
Turn on InPrivate Browsing.
You should turn on InPrivate Browsing. When InPrivate Browsing is enabled, no information about your activity browsing the Internet is stored on the local computer. This includes cookies, history, and temporary Internet files.
You should not turn on SmartScreen Filter. The SmartScreen Filter sends information about the Web site you are visiting to Microsoft. Microsoft then checks the site against its database to determine if it is a phishing site. A phishing site is one that looks like a legitimate site to trick users into providing their authentication credentials. For example, a phishing site might impersonate an online banking site to obtain a username, password, or account number.
You should not turn on InPrivate Filtering. InPrivate Filtering allows you to block information about your browsing patterns from being sent to certain providers.
You should not turn on Work Offline. When Work Offline is enabled, updated content is not downloaded from the Internet. Only cached content can be viewed.
You install Microsoft Windows 7 on a computer that you want to use as a reference computer for creating Windows image (WIM) files.
You need to remove any computer-specific information from the installation before creating an image.
What should you do?
- Run OCSetup.
- Run DSIM.
- Run Sysprep.
- Run ImageX.
Run Sysprep.
You should run Sysprep. Specifically, you need to run Sysprep /generalize to remove unique computer information so that the image can be used for installation on one or more different computers.
You should not run OCSetup. The OCSetup command is used to add system components to an online Windows image. It does not generalize the image for distribution.
You should not run Deployment Image Servicing and Management (DISM). DISM is used to service offline Windows images, such as to add drivers to an image. It is not used to prepare a computer for imaging.
You should not run ImageX. The ImageX command is used to create and manage images, but it requires that you first prepare the computer using Sysprep.
A computer is running Microsoft Windows 7 Ultimate. The computer has one internal hard disk configured as a simple volume.
The computer stores confidential files on the internal hard disk. The files are protected with NTFS permissions. You need to ensure that the files cannot be read if the hard disk is removed and installed in a different computer.
What should you do?
- Create a FAT32 partition and enable BitLocker.
- Encrypt the files using EFS.
- Enable BitLocker To Go.
- Create an NTFS partition and enable BitLocker.
Create an NTFS partition and enable BitLocker.
You should enable BitLocker. BitLocker is used to secure data on a drive so that it cannot be accessed if the drive is removed and inserted in a different computer, unless the necessary password is provided. You should also create an NTFS partition. BitLocker requires the computer to have a separate system partition that is formatted as NTFS and unencrypted. The partition must be at least 200 MB. If you do not create the partition, BitLocker will create it when you enable it.
You should not create a FAT32 partition. The system partition must be an NTFS partition, not a FAT32 partition.
You should not enable BitLocker To Go. BitLocker To Go is used to secure removable drives, such as a Universal Serial Bus (USB) flash drive.
Encrypting the files with Encrypting File System (EFS) will not meet the requirements. EFS is per-user encryption enforced by Windows, so if the user can access the operating system drive, that user can potentially compromise the encrypted files.
A user’s computer is running Microsoft Windows 7. System Protection is enabled.
The user accidentally deletes a file named ProjectFile.doc from the Projects folder in her Documents library. The Recycle Bin has already been emptied.
You need to recover the file for the user.
What should you do?
- Open the Previous Versions tab of the Documents library.
- Open the Previous Versions tab of the Projects folder.
- Open Recovery in the Control Panel and select Restore your files.
- Open Recovery in the Control Panel and select Open System Restore.
Open the Previous Versions tab of the Projects folder.
You should open the Previous Versions tab of the Projects folder. When System Protection is on, shadow copies of files are created each time a restore point is saved. If a file is deleted, the previous version of the file is listed on the Previous Versions tab of the folder that contained the file. You can copy or restore the file from this tab.
You should not open the Previous Versions tab of the Documents library. To recover a file, you need to open Previous Versions on the folder that contained the file, not the library.
You should not open Recovery in the Control Panel and select Restore your files. You use this option to restore files from backup, not to restore a deleted file that was saved in a restore point.
You should not open Recovery in the Control Panel and select Open System Restore. You use this option to restore the operating system settings to a restore point, not to restore a data file.
A user who has a computer running Microsoft Windows 7 needs assistance setting up Parental Controls.
You want to see the steps she is performing and the result of each step.
What should you do?
- Log onto her computer through Remote Desktop and view the Parental Controls log in Event Viewer.
- Ask her to save the Operational Log for Parental Controls and e-mail it to you.
- Ask her to repeat the steps using the Problem Steps Recorder and e-mail the output.
- Log onto her computer through Remote Desktop and view the Application log in Event Viewer.
Ask her to repeat the steps using the Problem Steps Recorder and e-mail the output
You should ask her to repeat the steps using the Problem Steps Recorder and e-mail the output. The Problem Steps Recorder takes a screen shot of each step a user takes when performing a task. The user can add comments to the steps, save the output, and e-mail a compressed version of the saved output to a technician.
You should not log onto her computer through Remote Desktop and view the Parental Controls log in Event Viewer. The Parental Controls Operational log stores setting changes related to Parental Controls, but it does not record each step a user takes.
You should not ask her to save the Operational Log for Parental Controls and e-mail it to you. The Parental Controls Operational log stores setting changes related to Parental Controls, but it does not record each step a user takes.
You should not log onto her computer through Remote Desktop and view the Application log in Event Viewer. Applications can write messages to the Application log. It is not used to troubleshoot problems related to a user’s inability to configure Parental Controls.
You are configuring your home network. The network will include:
* Desktop computer used at home only with a shared Internet connection
* Two mobile computers used at home and at public WiFi sites
* One mobile computer that you use at home and work
All of the computers will run Microsoft Windows 7. You need to minimize the administration and management necessary to share resources between home computers, with the exception of the computer that is also used at work.
Your computer is part of an Active Directory domain at work. You want to be able to access shared resources at home, but you do not want to have any resources shared automatically from your computer.
What should you do?
- Configure your home network as an Active Directory domain and give all users permission to share resources from their computers.
- Configure your home network manually as a peer-to-peer network and give all users permission to share resources from their computers.
- Configure your home network as a HomeGroup and choose to share resources automatically.
- Configure your home network as a HomeGroup and choose to not share resources automatically.
Configure your home network as a HomeGroup and choose to share resources automatically.
You should configure your home network as a HomeGroup and choose to share resources automatically. Resources, such as music, printers, videos, and so forth will be shared as libraries. You can choose the resource categories to be shared automatically when you set up the network. Because your computer is configured as a domain member at work, it will be able to access resources as part of the HomeGroup, but it will not be able to share resources to other computers.
You should not configure your home network as an Active Directory domain and give all users permission to share resources from their computers. This would require you to set up a computer as an Active Directory domain controller and would carry extensive management and administrative overhead. It would also force you to change domain membership between work and home.
You should not configure your home network manually as a peer-to-peer network and give all users permission to share resources from their computers. Resource sharing and network management would require significant more effort than setting up a HomeGroup.
You should not configure your home network as a HomeGroup and choose to not share resources automatically. This would require you to manually share resources from each of the member computers.
A domain member computer running Microsoft Windows XP is shared by multiple users. All users store documents in their My Documents folder.
You are planning to install Windows 7 on the computer. You need to ensure that application settings, user profile settings, and user documents for all users who have logged on in the last 90 days are migrated. Settings and documents for users who have not logged on in the last 90 days should not be migrated. The setting store is located at \fs1\migration.
What command should you use?
- Scanstate /i:migapp.xml /i:migdocs.xml \fs1\migration /ue:90
- Scanstate /i:migapp.xml /i:miguser.xml \fs1\migration /uel:90
- Scanstate /config:migapp.xml /config:migdocs.xml \fs1\migration /uel:90
- Scanstate /config:miguser.xml \fs1\migration /ue:90
Scanstate /i:migapp.xml /i:miguser.xml \fs1\migration /uel:90
You should use the following command:
Scanstate /i:migapp.xml /i:miguser.xml \fs1\migration /uel:90
The ScanState command is used to migrate user settings to a store. The /i option allows you to specify an Extensible Markup Language (XML) script that contains specifications for finding files to migrate. Migapp.xml is a default script that migrates application settings. MigUser.xml is a default script that migrates user profile data, including user settings and documents stored in a user’s My Documents folder. The /uel option allows you to filter the users whose settings are migrated. By including an integer after /uel, you limit the users migrated to those who have logged in within that number of days.
You should not use the following command:
Scanstate /i:migapp.xml /i:migdocs.xml \fs1\migration /ue:90
MigDocs.xml includes rules that locate documents on the computer that are not stored in My Documents and are not located by the rules in MigUsers.xml. The /ue option allows you to exclude a user by specifying a username or a domain name and a wildcard character.
You should not use the following command:
Scanstate /config:migapp.xml /config:migdocs.xml \fs1\migration /uel:90
The /config option allows you to specify a custom XML file generated by running Scanstate /genConfig. Also, the MigUsers.xml script needs to be included if you want to migrate user settings and documents.
You should not use the following command:
Scanstate /config:miguser.xml \fs1\migration /ue:90
The /config option allows you to specify a custom XML file generated by running Scanstate /genConfig. Also, the MigApp.xml script needs to be included if you want to migrate application settings.
You recently created a Microsoft Windows 7 image (WIM) file for deployment. The image is currently offline and staged for deployment.
You need to add an application to the image. The application is distributed as a Windows Installer (MSI) file.
What should you do?
- Use Deployment Image Servicing and Management (DISM) to service the image offline.
- Use Deployment Image Servicing and Management (DISM) to service the image online
- Use Windows Optional Component Setup (OCSetup) to service the image offline.
- Use Windows Optional Component Setup (OCSetup) to service the image online.
Use Windows Optional Component Setup (OCSetup) to service the image online.
You should use OCSetup to service the image online. You need to boot the image into audit mode. You must also prepare an unattended installation file for the application that specifies the path to the installation files. OCSetup calls the Windows Installer to run the actual installation.
Audit mode lets you make changes to a Windows installation without requiring you to activate the installation or finalize the computer for end-user use. After making necessary changes to the image, you can then recapture the image and use it as a source for deploying Windows 7.
You should not use DISM to service the image offline or online. DISM is not used to install applications that are distributed using an MSI file. When installing a Component-Based Servicing (CBS) package online, you will use OCSetup to initiate the installation, but OCSetup will internally invoke DISM to run the actual installation.
You should not use OCSetup to service the image offline. The image must be online when installing a Windows Installer application.
You have a computer running Windows 7.
You access a company Web site when you are traveling. The Web site is configured to use Integrated authentication.
You do not want to be prompted for credentials when you access the Web site.
What should you do?
- Use User Accounts to change your password to match the password specified on the Web site.
- Use Windows CardSpace to add a card that contains your credentials.
- Use Internet Options to configure InPrivate Filtering settings.
- Use Credential Manager to add a Windows credential to the vault.
Use Credential Manager to add a Windows credential to the vault.
You should use Credential Manager to add a Windows credential to the vault. The vault stores credentials for Web sites, file servers, and other resources you access. You can add Windows credentials, certificates, and generic credentials to the vault. Because Integrated authentication uses Windows credentials, you should add a Windows credential to the vault.
You should not use User Accounts to change your password to match the password specified on the Web site. Although the browser first sends the log on credentials for authentication when Integrated Security is used, both username and password must match. You should not create a separate user account that matches the credentials of the Web sites you need to access. Instead, you should use Credential Manager to store the authentication information securely.
You should not use Windows CardSpace to add a card that contains your credentials. Windows CardSpace allows you to store personal information that can be sent to Web sites. It is not used to manage authentication credentials.
You should not use Internet Options to configure InPrivate Filtering settings. InPrivate Filtering settings allow you to identify the Web sites you will allow to receive data about the Web sites you visit.
You have a computer running Microsoft Windows XP Professional. The computer has several applications that store custom settings.
You need to install Windows 7 on the computer.
What should you do?
- Perform an upgrade install of Windows 7
- Run ScanState
- Perform a custom install of Windows 7
- Run LoadState
- Run ScanState
- Perform a custom install of Windows 7
- Run LoadState
- Install the applications
- Run ScanState
- Perform a custom install of Windows 7
- Install the applications
- Run LoadState
Run ScanState
Perform a custom install of Windows 7
Install the applications
Run LoadState
You should do the following:
* Run ScanState
* Perform a custom install of Windows 7
* Install the applications
* Perform LoadState
You must perform a custom (clean) installation when migrating from Windows XP to Windows 7. To preserve application and user settings, you need to first run ScanState and save the settings to an external drive or a network share. Next, you need to install Windows 7 and the applications. Finally, you need to run LoadState to configure the computer with the saved settings. ScanState and LoadState are User State Migration Tool (USMT) commands. USMT migrates settings and data files, but not applications. Because the applications have custom settings, they must be installed before you restore the settings.
You cannot perform an upgrade install of Windows 7 from Windows XP.
You have installed Microsoft Windows 7 on a reference computer. The computer is partitioned as shown in the exhibit. Partitions C and D are primary partitions.
You need to capture images for only the required volumes.
What should you do next?
- Use ImageX to capture partitions C and D.
- Use ImageX to capture partition C only.
- Use Diskpart to assign a drive letter to volume 1.
- Use Diskpart to format volume 3 as NTFS
Use ImageX to capture partitions C and D.
You should use ImageX to capture partitions C and D. Both C and D are primary partitions. You must capture all primary partitions except the System Reserved partition and (optionally) the System partition. You capture partitions using ImageX with the /capture option.
You should not use ImageX to capture partition C only. You must also capture partition D. You must capture all primary partitions except the System Reserved partition and (optionally) the System partition.
You should not use Diskpart to assign a drive letter to volume 1. Volume 1 is the System Reserved partition created by default during an installation of Windows 7. You should not create an image of the System Reserved partition.
You should not use Diskpart to format volume 3 as NTFS. You can create an image of either NTFS or FAT32 partitions.
You recently upgraded a computer to Windows 7. As part of the process, you migrated the applications that were already running on the computer.
You need to determine if problems with an existing application are caused by potential compatibility issues due to the User Account Control (UAC) feature. You need to collect detailed information for analysis.
What should you do?
- Run the Setup Analysis Tool (SAT).
- Run the User State Migration Tool (USMT).
- Run the Standard User Analyzer (SUA) tool.
- Run Windows AppLocker.
Run the Standard User Analyzer (SUA) tool
You should run the SUA tool. The SUA tool lets you monitor specific applications for problems relating to the UAC feature. The SUA tool collects detailed data for analysis to help you fix any detected problems. There is also a SUA Wizard that steps you through potential fixes for UAC problems, but it does not perform detailed analysis.
You should not run the SAT. The SAT is used to automate application installation and monitor the activities of the application’s installer.
You should not run USMT. USMT would be used to migrate user profile and application setting information. It is not used for troubleshooting compatibility problems.
You should not run Windows AppLocker. AppLocker is used to create and manage rules to control user access to applications and files. AppLocker replaces the Software Restriction Policies feature in earlier versions of Windows.
You are responsible for managing several computers running Microsoft Windows 7. Your network is configured as a wide area network (WAN) with multiple routed subnets.
You need to facilitate remote support for computers running Windows 7. Your support solution should minimize the changes necessary on target computers.
What should you do?
- Use Remote Server Administration Tools (RSAT).
- Use PowerShell scripts.
- Use Remote Desktop Services Manager.
- Use Remote Desktop Gateway (RD Gateway).
Use PowerShell scripts.
You should use PowerShell scripts to manage remote computers running Windows 7. You can use PowerShell Windows Management Interface (WMI) scripts to perform most management tasks that might be automated.
Before you can use PowerShell to manage a remote computer, PowerShell must be installed on the computer. Because PowerShell is installed by default with Windows 7, you do not need to make changes to the target computer.
You should not use RSAT. RSAT can be used to remotely manage a computer running Windows 2008 Server and, in many circumstances, Windows 2003 server from a computer running Windows 7. RSAT cannot be used to manage a computer running Windows 7.
You should not use RD Gateway. RD Gateway enables Remote Desktop clients to access resources on remote servers and run applications remotely. RD Gateway is used to provide remote clients with a connection to RD Session Host resources and applications.
You should not use Remote Desktop Services Manager. Remote Desktop Services replaces the Terminal Services support provided with earlier Windows releases. Remote Desktop Services Manager lets you view users, sessions, and processes on a Remote Desktop Session Host (RD Session Host) server. You can manage client connections to the RD Session Host, but you cannot directly manage client computers.
You are planning to install Microsoft Windows 7 on a new computer using the distribution media. You want the installation to complete without displaying a user interface unless an error occurs. You want to limit the components that are installed.
What should you do?
- Use the Windows System Image Manager (SIM) to create a file named Unattend.txt. Save the file to a network share.
- Use ImageX to create a file named Sysprep.inf. Save the file to the root of drive C.
- Use the Windows System Image Manager (SIM) to create a file named Autounattend.xml. Save the file to a Universal Serial Bus (USB) flash drive.
- Use Package Manager to create a file named Winbom.ini. Save the file to a network share.
Use the Windows System Image Manager (SIM) to create a file named Autounattend.xml. Save the file to a Universal Serial Bus (USB) flash drive.
You should use the Windows SIM to create a file named Autounattend.xml and save the file to a USB flash drive. The Windows SIM utility is part of the Windows Automated Installation Kit (AIK). It allows you to create answer files that can be used to limit the components installed and the features enabled during an automated installation. The answer file is an Extensible Markup Language (XML) file that is normally named Autounattend.xml. You can store the file on a USB flash drive (UFD) or in another location. If you use a different filename or store the file in a location not included in the implicit search path, you will need to specify the path to the file when you run Setup using the following command:
setup.exe /unattend:filename
You should not use the Windows System Image Manager (SIM) to create a file named Unattend.txt and save the file to a network share. Older versions of Windows used an answer file named Unattend.txt. Windows 7 uses an XML file.
You should not use ImageX to create a file named Sysprep.inf and save the file to the root of drive C. ImageX is used to create an image, not to create an answer file. The Sysprep.inf file was used when creating a Windows XP installation image. It has been replaced by the Unattend.xml file in Windows 7. Also, Sysprep.inf was used with the Sysprep tool, not with Setup.exe.
You should not create a file named Winbom.ini and save the file to a network share. The Winbom.ini file was another answer file used during Windows XP Setup.
You have a computer running Microsoft Windows 7.
You need to ensure that only device drivers that have been approved by an administrator can be installed on the computer.
What should you do? (Each correct answer presents part of the solution. Choose two.)
- In Local Security Policy, enable the Only elevate permission for executables that are signed and validated policy.
- In System Properties, select Never install driver software from Windows Update.
- Run Dism on the computer.
- Run Pnputil on the computer.
- In Local Security Policy, enable the Only elevate UIAccess applications that are installed in secure locations policy.
- Run Pnputil on the computer.
- In System Properties, select Never install driver software from Windows Update.
You should run Pnputil on the computer. Windows 7 allows you to stage device drivers to a driver store on a computer. You use the Pnputil command to add a driver to a staged location.
You should also enable Never install driver software from Windows Update in System Properties. By default, Windows searches the driver store, any paths specified in the DevicePath registry key, and Windows Update. If you prevent Windows from using Windows update, only device drivers in the store or in a path listed in the DevicePath registry key will be searched. The search order can be modified through the Specify search order for device driver source locations Group Policy setting.
You should not enable the Only elevate permission for executables that are signed and validated policy. This policy affects whether an unsigned executable can execute with elevated permission. It does not affect which device drivers can be installed.
You should not run Deployment Image Servicing and Management (Dism) on the computer. Dism is a command-line utility that is used to mount and modify installation images and create Windows PE images.
You should not enable the Only elevate UIAccess applications that are installed in secure locations policy. This setting determines whether applications that request User Interface Accessibility access permissions can run if they are installed in a location that is not considered secure. Secure locations are:
\Program Files\Windows\System32\Program Files (x86)
You recently backed up system state information for a computer running Microsoft Windows 7. You backed up system state information to the local computer.
You need to restore system state information from that backup.
What should you do?
- Use the System Restore application.
- Use the Windows Backup tool.
- Use the Wbadmin command.
- Use Windows Recovery Environment (RE).
Use the Wbadmin command.
You should use the Wbadmin command. You must use the Wbadmin command to restore system state information for Windows 7. To restore the system state, you would run the following from a command prompt run with administrator privileges:
wbadmin start systemstaterecovery
You should not use the System Restore application. System Restore lets you restore a computer to an established restore point or to a complete PC backup that was created earlier.
You should not use the Windows Backup tool. You cannot use the Backup tool to back up or restore system state information. You must use Wbadmin to back up or restore system state.
You should not use Windows RE to restore system state. Windows RE includes system recovery options, including recovering from a complete backup or a Windows system image, but it does not support system state recovery.
You maintain client computers on your network. Scheduled client backups are configured to be stored on network file servers.
You need to periodically back up selected files from a computer running Microsoft Windows 7 to a DVD for offsite storage. You need to minimize the effort needed to accomplish this.
What should you do? (Each correct answer presents a complete solution. Choose two.)
- Use the Backup tool to back up to a network location and copy the backup file to DVD.
- Use Windows Recovery Environment (RE) to back up the files to DVD.
- Use Ntbackup to back up to a network location and copy the backup file to DVD.
- Use Backup to back up directly to DVD.
- Use Wbadmin to back up directly to DVD.
- Use Wbadmin to back up directly to DVD.
- Use Backup to back up directly to DVD.
In Windows 7, you can use Wbadmin or the Backup tool to back up directly to DVD as your backup destination. The disk can then be removed and stored in an offsite location.
You should not use the Backup tool to back up to a network location and copy the backup file to DVD. This would work, but it requires more steps than necessary to accomplish the backup.
You should not use Windows RE to back up the files to DVD. Windows RE provides several options for recovering a system, but not for producing a backup.
You should not use Ntbackup to back up to a network location and copy the backup file to DVD. Windows 7 does not include Ntbackup. There is a version of Ntbackup available for download that will run on Windows 7, but it can only be used to restore files from a backup created using an earlier Windows version of the Ntbackup command.
You have a computer running Microsoft Windows 7. The computer is used by 20 different users.
One application does not operate correctly. It operates correctly on a computer running Windows XP.
You need to ensure that all users can run the application. Your solutions should require the least amount of effort.
What should you do?
- On the application’s Compatibility tab, select Windows XP as the Compatibility mode.
- On the application’s Compatibility tab, click Change settings for all users. Select Windows XP as the Compatibility mode.
- Modify the program’s settings in Programs and Features.
- Modify the Application Compatibility settings in local Group Policy.
On the application’s Compatibility tab, click Change settings for all users. Select Windows XP as the Compatibility mode.
You should open the application’s Compatibility tab, click Change settings for all users, and select Windows XP as the Compatibility mode. You can configure application-specific compatibility settings through the Compatibility tab. The settings affect the user who is logged on. To access settings for all users, you need to click Change settings for all users. Because the application ran fine under Windows XP, the first setting you should try is to set the Compatibility mode to Windows XP.
You should not select Windows XP as the Compatibility mode on the application’s Compatibility tab. Doing so would affect the compatibility settings only for the user who is currently logged on.
You should not modify the program’s settings in Programs and Features. You can use Programs and Features to change installation options and uninstall a program. You cannot configure compatibility settings there.
You should not modify the Application Compatibility settings in local Group Policy. The Application Compatibility settings in local Group Policy allow you to enable or disable application compatibility features, such as the Program Compatibility Assistant. It does not allow you to configure compatibility settings for a specific application.
Your network is configured as an Active Directory domain. Encrypting File System (EFS) is configured to use self-signed certificates for encryption.
You need to give members of the DataSet group access to an encrypted file on a domain member computer running Microsoft Windows 7. Access should be limited to that file only. You want to minimize the administrative effort necessary to accomplish this.
What should you do?
- Run the cipher command with the /r option to export the recovery certificate and private key.
- Modify Group Policy to identify DataSet members as recovery agents.
- Add the DataSet group through the file’s Advanced properties.
- Add each user individually through the file’s Advanced properties.
Add each user individually through the file’s Advanced properties.
You should add each user individually through the file’s Advanced properties. This will grant these specific users access to the file. Access must be granted on a user-by-user basis when limiting access to a single file.
You should not run the cipher command with the /r option to export the recovery certificate and private key. This would not be necessary in this scenario. You would do this if you were creating a new recovery agent. A recovery agent enables you to recover all of a user’s encrypted files.
You should not modify Group Policy to identify DataSet members as recovery agents. This would provide access to all encrypted files and cannot be limited to a single file.
You should not add the DataSet group through the file’s Advanced properties. Users must be added individually.
A user has a Microsoft Windows 7 computer.
The user reports slow performance when accessing data on a Universal Serial Bus (USB) hard disk drive. The data access performance has not always been poor, but has gotten worse over time. The drive is formatted as NTFS.
You need to optimize performance.
What should you tell the user to do?
- Defragment the volume.
- Convert the volume to FAT32.
- Convert the volume to a dynamic disk.
- Update the USB controller driver.
Defragment the volume.
You should tell the user to defragment the volume. Like an internal hard disk volume, a USB hard disk drive can become fragmented over time. You can defragment the volume by displaying the volume’s properties, selecting the Tools tab, and clicking Defragment now.
You cannot convert the volume to FAT32. You cannot convert from NTFS to FAT32. You must reformat, which will result in losing data. Also, NTFS provides better performance than FAT32.
You cannot convert the volume to a dynamic disk. You can only convert an internal hard disk to a dynamic disk. Also, the advantage to using a dynamic disk is the ability to create spanned and striped disks, not to provide better performance.
You should not update the USB controller driver. The problem is not related to the USB controller driver. If it were, the problem would not have gradually gotten worse. When disk access performance gradually worsens, the problem is most likely caused by fragmentation.
You are configuring Internet Explorer on Microsoft Windows 7. Internet Explorer is configured as your default Web browser.
A recently configured add-on is causing Internet Explorer to crash every time you launch it from the Start menu. You need to disable support for that add-on. You need to minimize other changes made to the computer’s configuration.
What should you do first?
- Launch Add/Remove programs from the Control Panel.
- Right-click Internet Explorer in the Start menu and click Properties.
- Run Internet Explorer (No Add-ons) from All Programs > Accessories > System Tools.
- Revert to a system recovery point from before installation of the add-on.
Run Internet Explorer (No Add-ons) from All Programs > Accessories > System Tools
You should run Internet Explorer (No Add-ons) from All Programs > Accessories > System Tools. You need to disable the add-on that is causing the problem. To do this, you need to run the Manage Add-on utility. Unlike earlier Internet Explorer versions, Internet Explorer version 8, which ships with Windows 7, lets you manage add-ons after launching Internet Explorer without add-ons. You can disable the add-on causing the problem and then start Internet Explorer normally. You can also run iexplore -extoff from a command line to disable add-ons.
You should not launch Add/Remove programs from the Control Panel. This does not necessarily give you access to the add-on you need to disable.
You should not right-click Internet Explorer in the Start menu and click Properties. This lets you access the properties of the shortcut, but it does not let you manage add-ons.
You should not revert to a system recovery point from before installation of the add-on. This could result in other changes to the computer.
Your company has 50 salespeople who have portable computers. Thirty of them are running Windows 7 and 20 are running Windows Vista. The firewall between the Internet and your company’s network does not allow Layer 2 Tunneling Protocol (L2TP) or Point-to-Point Tunneling Protocol (PPTP) traffic.
You need to enable the salespeople to connect to servers on the corporate network while they are away from the office.
What should you do?
- Configure a Routing and Remote Access server to use Secure Sockets Tunneling Protocol (SSTP).
- Configure a Routing and Remote Access server to use Network Access Protection (NAP).
- Configure a DirectAccess server in an end-to-edge configuration.
- Configure a DirectAccess server in an end-to-end configuration.
Configure a Routing and Remote Access server to use Secure Sockets Tunneling Protocol (SSTP).
You should configure a Routing and Remote Access server to use SSTP. SSTP is a virtual private network (VPN) protocol supported by Windows Server 2008, Windows Vista, and Windows 7. It uses port 443, so it can pass through firewalls that do not support other VPN protocols.
You should not configure a Routing and Remote Access server to use NAP. NAP is a system health verification and quarantine service, not a VPN protocol. It can be used for VPN connections and other connections to ensure that clients have a supported configuration, including Windows updates and antivirus software.
You should not configure a DirectAccess server in an end-to-edge configuration. Windows Vista computers cannot connect using DirectAccess. An end-to-edge configuration can be used to allow Windows 7 clients to access both Windows Server 2008 and Windows Server 2003 servers on the intranet.
You should not configure a DirectAccess server in an end-to-end configuration. Windows Vista computers cannot connect using DirectAccess. An end-to-end configuration is the most secure because data is encrypted from the client to the server. However, Windows Server 2003 servers cannot be accessed in an end-to-end configuration.
You are configuring application restrictions for computers running Windows 7.
You need enable users to run only applications signed with digital signatures from the application manufacturers.
What should you do first?
- Use AppLocker to create a new executable rule for each signed application.
- Use AppLocker to create default executable rules for all users.
- Use AppLocker to create a new executable rule for all signed applications.
- Use AppLocker to create a publisher rule for each signed application.
Use AppLocker to create default executable rules for all users.
You should use AppLocker to create default executable rules for all users. You must create a default rules set before creating the rules to limit users to running signed applications only. Default rules enable all users to run the programs in the default Program Files folder and in the Windows folder.
You should not use AppLocker to create a new executable rule for each signed application. This is not necessary. After creating default rules, you would create a new executable rule for all signed applications.
You should not use AppLocker to create a publisher rule for each signed application. A publisher rule is used to enable rules to apply to an application after an upgrade rather than having to create a new rule each time you upgrade an application.
You manage a computer running Windows 7. It connects to your company’s intranet by using DirectAccess.
You need to ensure that the computer automatically downloads only approved updates. Users must still be able to manually install updates from the Microsoft Web site.
What should you do?
- Enable the Give me recommended updates the same way I receive important updates option in Windows Update.
- Enable the Turn on recommended updates via Automatic Update policy in Group Policy.
- Enable the Specify intranet Microsoft Update Service location policy in Group Policy.
- Disable the Allow all users to install updates on this computer option in Windows Update.
Enable the Specify intranet Microsoft Update Service location policy in Group Policy.
You should enable the Specify intranet Microsoft Update Service location policy in Group Policy. This policy allows you to identify a Windows Software Update Service (WSUS) computer to use for downloading Windows updates. Updates on a WSUS computer can be selectively approved. You cannot identify a WSUS server through Windows Update.
You should not enable the Give me recommended updates the same way I receive important updates option in Windows Update. Enabling this option causes recommended updates to be downloaded using the same settings as for important or critical updates.
You should not enable the Turn on recommended updates via Automatic Update policy in Group Policy. Enabling this policy causes recommended updates to be downloaded using the same settings as for important or critical updates.
You should not disable the Allow all users to install updates on this computer option in Windows Update. This setting prevents users from manually installing updates, but it does not affect automatic updates.
You are planning to install Microsoft Windows 7 on computers at several different branch offices. You need to be able to install by booting from a Universal Serial Bus (USB) flash drive.
What should you do first?
- Use ImageX to create an image and copy the image to the USB flash drive.
- Use Windows System Image Manager (SIM) to create an image and copy the image to the USB flash drive.
- Use diskpart to create an active primary partition on the USB flash drive and format it as NTFS.
- Use diskpart to create an active primary partition on the USB flash drive and format it as FAT32.
Use diskpart to create an active primary partition on the USB flash drive and format it as FAT32.
You should use diskpart to create an active primary partition on the USB flash drive and format it as FAT32. You need to first prepare the USB drive. To do so, you run diskpart, clean the disk, and then create an active primary partition. You should format the partition as a FAT32 partition. After the partition is prepared, you can copy the installation files from the DVD to the USB flash drive.
You should not use ImageX to create an image and copy the image to the USB flash drive. Images are created using ImageX. However, you must boot using Windows Preinstallation Environment (Windows PE) to apply an image.
You should not use Windows SIM to create an image. Windows SIM is used to create an answer file, not an image.
You should not use diskpart to create an active primary partition on the USB flash drive and format it as NTFS. You must format the partition as FAT32.
Your company has a corporate office and three branch offices. All client computers at the branch offices run Microsoft Windows 7.
Flash presentations used for training are located on a server running Windows Server 2008 at the corporate office.
You decide to use BranchCache in Distributed Cache mode to reduce traffic over the Wide Area Network (WAN).
You need to configure the Windows Firewall settings on the Windows 7 computers.
What should you do?
- Allow incoming WS-Discovery and outgoing Hypertext Transfer Protocol (HTTP) traffic.
- Allow incoming Hypertext Transfer Protocol (HTTP) and Server Message Block (SMB) traffic.
- Allow incoming Hypertext Transfer Protocol (HTTP) and WS-Discovery traffic.
- Allow incoming Hypertext Transfer Protocol (HTTP) traffic only.
Allow incoming Hypertext Transfer Protocol (HTTP) and WS-Discovery traffic.
You should allow incoming HTTP and WS-Discovery traffic. BranchCache uses HTTP to transmit data in both Distributed Cache and Hosted Cache mode. In Distributed Cache mode, content can be cached on any client on which BranchCache is enabled. A client uses the WS-Discovery protocol to locate cached content. With Hosted Cache mode, clients are configured with the address of the host, so there is no need to use the WS-Discovery protocol.
You should not allow incoming WS-Discovery and outgoing HTTP traffic. Clients must accept incoming HTTP traffic if they are to receive data.
You should not allow incoming HTTP and SMB traffic. Although BranchCache can be used to cache file share data transmitted over SMB, the data is sent to and retrieved from the cache server using HTTP.
You should not allow incoming HTTP traffic only. If you were using Hosted Cache mode, you would only need to allow incoming HTTP traffic. However, you need to allow WS-Discovery traffic in Distributed Cache mode.
You are planning to deploy Microsoft Windows 7 to 500 new computers.
You need to select the most efficient deployment option.
What should you do?
- Use Windows System Image Manager (SIM) to create an image.
- Use Package Manager to create a package.
- Use Microsoft Deployment Toolkit (MDT) to create a deployment point.
- Use Windows Automated Installation Kit (AIK) to create a deployment point.
Use Microsoft Deployment Toolkit (MDT) to create a deployment point.
You should use MDT to create a deployment point. MDT is most suitable for high-volume installations. Clients access the deployment point using Windows Preinstallation Environment (PE), which you can create on removable media or share using Windows Deployment Service (WDS). You can install all necessary customizations in the deployment point.
You cannot use Windows SIM to create an image. Windows SIM is used to create an unattended installation file. Windows SIM is part of the Windows AIK, which is more suitable for creating images to support medium-sized deployments.
You should not use Package Manager to create a package. A package is a feature that can be referenced by an unattended installation file. It is not a full deployment of Windows 7.
You cannot use Windows AIK to create a deployment point. AIK is used to create unattended installation files and images for medium-sized deployments.
You are using a public computer that is running Microsoft Windows 7.
You need to visit several locations on the Internet. You need to ensure that the computer you are using does not record your browsing history.
What should you do?
- Enable InPrivate filtering.
- Enable SmartScreen filter.
- Enable InPrivate browsing.
- Enable Phishing filter.
Enable InPrivate browsing.
You should enable InPrivate browsing. You can do this by choosing InPrivate browsing when you open a new browser window or tab. This prevents the computer from maintaining your browsing history. No record of made of addresses and links visited, form data, or passwords used. Any new cookies are treated as session cookies and are not stored. Temporary Internet files are deleted when the private browsing window is closed.
You should not enable InPrivate filtering. InPrivate filtering does not prevent recording of browser history information. Instead, it warns you about third-party content that can view your browsing history and lets you block this access.
You should not enable SmartScreen filter for this purpose, though you will typically want to have the SmartScreen filter enabled. The SmartScreen filter helps block malware and indentify potentially hazardous Web sites.
You should not enable Phishing filter. Phishing filter was replaced by the SmartScreen filter in Windows 7 and Internet Explorer 8.
You created a Microsoft Windows 7 image file to support the complete retail edition family. The image is currently configured to install Windows 7 Ultimate by default. You are using Windows Deployment Services (WDS) to distribute the image to the destination computers.
You need to install Windows 7 Professional on two target computers from the custom image. You need to accomplish this with minimal effort. The reference computer originally used to create the image is available.
What should you do?
- Use Deployment Image Servicing and Management (DISM) to modify the image.
- Boot the image on the reference computer and use Windows Optional Component Setup (OCSetup) to modify the image.
- Create a new image from the reference computer.
- Use Windows System Image Manager (SIM) to create a custom unattended installation file.
Create a new image from the reference computer.
You should create a new image from the reference computer. When you create an image, it will contain the editions supported by that edition family, in this case, the retail family. The editions available in the retail and consumer families are:
* Windows 7 Starter
* Windows 7 Home Premium
* Windows 7 Professional
* Windows 7 Ultimate
You can modify an image to have it install a higher edition by default, such as increasing from Windows 7 Home Premium to Windows 7 Professional, but you cannot modify an image to support a lower edition if it is already set to install a higher edition.
You should not use DISM to modify the image. You can use DISM to raise the edition installed by the image, but not lower it. Because the image is set to Windows 7 Ultimate, you cannot drop the edition back to Windows 7 Professional.
You should not boot the image on the reference computer and use OCSetup to modify the image. OCSetup can be used to modify an online image, but not to change the default edition installed by the image.
You should not use Windows SIM to create a custom unattended installation file. This does not give you a way to install a lower Windows 7 edition.
You have a Microsoft Windows 7 computer.
Users sometimes need to be able to access resources on the computer across the network.
You need to ensure that only users who have a user account and password on the computer can access resources.
What should you do?
- Create a homegroup.
- Disable Simple file sharing.
- Turn off Network Discovery.
- Turn on password protected file sharing.
Turn on password protected file sharing.
You should turn on password protected file sharing. When password protected file sharing is enabled, a user can only access shared resources on a computer if that user has a user account and password on that computer. You enable password protected file sharing through Advanced sharing settings in the Network and Sharing Center.
You should not create a homegroup. When you create a homegroup, you can share files that can be accessed only by other computers that are joined to the homegroup.
You cannot disable Simple file sharing. Simple file sharing was a Windows XP file sharing method and is not supported by Windows 7.
You should not turn off Network Discovery. Network Discovery allows your computer to locate and be located by other computers on the network.
You are preparing to deploy Microsoft Windows 7 from the network. Thirty computers have a 32-bit processor, 20 have an x64 processor, and 10 have an Itanium processor.
You need to deploy Windows 7 using the least number of .wim files.
What should you do?
- Create a .wim file that has both a 32-bit image and an x64 image. Create a separate .wim file that has an Itanium image.
- Create a separate .wim file for each processor.
- Create a .wim file that has a 32-bit image. Create a separate .wim file that has an x64 and an Itanium image.
- Create one .wim file that has an image for each processor.
Create a .wim file that has both a 32-bit image and an x64 image. Create a separate .wim file that has an Itanium image.
You should create a Windows image (.wim) file that has both a 32-bit image and an x64 image and create a separate .wim file that has an Itanium image. You can store a 32-bit image and an x64 image in the same .wim file. To do so, you first create the 32-bit image and then use the /append option of ImageX to append the x64 image. However, you must have a separate .wim file to deploy the Itanium processor installation.
You do not need to create a separate .wim file for each processor. You can store the 32-bit image and the x64 image in the same file.
You should not create a .wim file that has a 32-bit image and create a separate .wim file that has an x64 and an Itanium image. You cannot store an x64 image and an Itanium image in the same file.
You should not create one .wim file that has an image for each processor. The Itanium image must be stored in a separate .wim file.
You manage a domain. All client computers in the domain are running Microsoft Windows 7.
You need to allow certain client computers to accept File Transfer Protocol (FTP) requests, but only when they are connected to the domain. All FTP communication must be encrypted.
You need to enable FTP to meet requirements.
What tool should you use?
- IP Security Policy Microsoft Management Console (MMC)
- Netsh firewall
- Windows Firewall with Advanced Security
- Default Programs
Windows Firewall with Advanced Security
You should use Windows Firewall with Advanced Security. Windows Firewall with Advanced Security allows you to create rules that limit traffic by protocol or port. It also allows you to configure security requirements for the connection, including requiring authentication and encryption. Windows Firewall with Advanced Security combines firewall rule definition and IP Security (IPSec) rule definition into one integrated tool.
You should not use the IP Security Policy MMC. This tool can be used to configure more limited rules than Windows Firewall with Advanced Security. It does not allow you to segregate the rule so that it is only applied to the domain network location.
You should not use Netsh firewall. You can configure a limited set of firewall configuration settings by using Netsh firewall. However, you could not configure the necessary rule by using Netsh advfirewall.
You should not use Default Programs. Default Programs allows you to select the program that should be used for specific types of activities, such as browsing or e-mail. It is not used to configure security restrictions on network traffic.
Your company has an Active Directory domain. The company’s network is shown in the exhibit.
A number of users have portable computers running Microsoft Windows 7. These users need to be able to connect to a selected set of servers on the corporate intranet from any location that has an Internet connection. Users need to be able to access Internet resources without going through the intranet. You add a server named RA-Srv running Windows Server 2008 R2 to the perimeter network.
You need to configure the client computers to meet requirements.
What should you do? (Each correct answer presents part of the solution. Choose two.)
- Run the DirectAccess Setup Wizard on RA-Srv. Add IntranetUsers to the DirectAccess Client Setup list.
- Add the laptop computers to a security group named IntranetUsers.
- Create a Group Policy object (GPO) that enables the Client (Respond only) IP Security (IPSec) policy.
- Configure a Virtual Private Network (VPN) connection on each computer.
- Enable a Virtual Private Network (VPN) endpoint on RA-Srv.
- Add the laptop computers to a security group named IntranetUsers.
- Run the DirectAccess Setup Wizard on RA-Srv. Add IntranetUsers to the DirectAccess Client Setup list.
You should do the following:
* Add the laptop computers to a security group named IntranetUsers.
* Run the DirectAccess Setup Wizard on RA-Srv. Add IntranetUsers to the DirectAccess Client Setup list.
DirectAccess allows client computers running Windows 7 or Windows Server 2008 R2 to connect to intranet resources. Connections to Internet resources can be made directly instead of passing through the intranet. A DirectAccess server must be a domain member running Windows Server 2008 R2 and must be located on the perimeter network. It must have two network adapters: a public network adapter and a private network adapter. Both network adapters must be configured for IPv6. The public network adapter must be assigned two publicly-accessible consecutive IPv4 addresses. You configure clients by adding them to a security group and adding that security group to the client list using the DirectAccess Setup Wizard. The necessary GPO containing the client settings is created by the wizard.
You should not create a GPO that enables the Client (Respond only) IPSec policy. Configuring clients to use IPSec is not sufficient to enable them as DirectAccess clients. Other policies must be set so that they can find a network location server and connect to the intranet automatically.
You should not configure a VPN connection on each computer or enable a VPN endpoint on RA-Srv. A VPN connection is used to connect to a VPN endpoint. When a user who is connected to a VPN endpoint attempts to connect to an Internet resource, the request is routed through the intranet.
You have a computer running Microsoft Windows 7.
Users report poor performance when executing a specific program with a Windows Experience Index of 3. You run the Performance tool. A portion of the results are shown in the exhibit.
You need to recommend the change that will have the most positive impact on the user’s experience.
What should you recommend?
- Add more RAM.
- Upgrade to the 64-bit version of Windows 7.
- Upgrade the graphics adapter.
- Upgrade to Windows 7 Enterprise edition
Upgrade the graphics adapter.
You should upgrade the graphics adapter. The performance tool analyzes each component and identifies a Windows Experience Index subscore. It then creates a base score based on the lowest subscore. The base score indicates the Windows Experience Index at which applications will run efficiently. Upgrading hardware that already has a higher Windows Experience Index than the base score will not affect the way applications run. In this case, the graphics adapter has the lowest subscore, so the best upgrade would be to replace the graphics adapter with a more efficient one.
You should not add more RAM. The 1 GB of RAM is sufficient for running Windows 7. The system would be faster with more RAM, but the RAM is not the biggest bottleneck in this case.
You should not upgrade to the 64-bit version of Windows 7. Although the computer has a 64-bit processor, it does not have enough RAM to support an upgrade to the 64-bit version of Windows 7. The 64-bit version requires 2 GB of RAM.
You should not upgrade to Windows 7 Enterprise. Windows 7 Enterprise includes additional features suitable for use in an Active Directory domain environment. There is no performance difference between Windows 7 Ultimate and Windows 7 Enterprise.
Your company’s network is configured as a workgroup. You have a Microsoft Windows 7 computer that is configured with the networks shown in the exhibit. Your network has a wireless adapter named Belkin_N_Wireless_BF327F.
The user can connect to the Internet but cannot access other computers on the local network.
You need to resolve the problem while maintaining the best possible security.
What should you do?
- Enable Network Discovery for Public networks.
- Enable File sharing for Public networks.
- Change the network location to Work.
- Change the address of the Domain Name System (DNS) server.
Change the network location to Work.
You should change the network location to Work. By default, a Public network does not permit a user to connect to computers on the local network. It only allows limited access, such as browsing Web pages.
You should not enable Network Discovery for Public networks. When Network Discovery is enabled, a computer can locate and be located by other computers on the local network. Network Discovery is enabled by default for Work and Home networks, but not for Public networks. If you enable Network Discovery for Public networks, you will be able to access other computers on the network, but this setting will affect all Public networks. Therefore, if you connect to a network at a Wi-Fi hotspot, other computers connected to that hotspot will be able to see the computer.
You should not enable File sharing for Public networks. When file sharing is enabled, you can share files with other computers on the network. However, this setting would apply to all public networks, so it would negatively affect the computer’s security.
You should not change the address of the DNS server. The problem is not caused by incorrect DNS settings. The problem is caused by the fact that the network location is set to Public. DNS is used to resolve host names to IP addresses. If you had the wrong DNS setting, you would be unable to access resources on the Internet.
Your company has a corporate office and a branch office. The network is configured as an Active Directory domain. All client computers are domain members running Microsoft Windows 7.
You install BranchCache on a server named BC-Srv in the branch office.
You discover that files are being cached to the Windows 7 computers in the branch office instead of to BC-Srv. You run netsh on one of the Windows 7 computers and receive the output shown in the exhibit.
You need to ensure that all files are cached on BC-Srv.
What should you do?
- Enable the Configure BranchCache for network files policy in the Group Policy object (GPO).
- Execute the following command on each Windows 7 client: netsh branchcache set service mode=HOSTEDCLIENT location=BC-Srv
- Execute the following command on each Windows 7 client: netsh branchcache set cachesize = 0
- Enable the Set BranchCache Hosted Cache mode policy in the Group Policy object (GPO).
Enable the Set BranchCache Hosted Cache mode policy in the Group Policy object (GPO).
You should enable the Set BranchCache Hosted Cache mode policy in the GPO. BranchCache can be configured to operate in either Hosted Cache mode or Distributed Cache mode. Group Policy currently configures the client computers to operate in Distributed Cache mode. However, the scenario requires that all data be cached to a service, which is the way Hosted Cache mode works. Therefore, you need to modify the GPO by enabling Hosted Cache mode.
You should not enable the Configure BranchCache for network files policy in the GPO. This policy affects the latency that can be supported when using Distributed Cache mode.
You should not execute the following command on each Windows 7 client:
netsh branchcache set service mode=HOSTEDCLIENT location=BC-Srv
While this command can be used to configure a client for Hosted Cache mode, it cannot be used in this scenario because Group Policy settings override a configuration set using netsh.
You should not execute the following command on each Windows 7 client:
netsh branchcache set cachesize = 0
This command is used to set the size of the cache. While setting the cachesize to 0 on the clients will prevent the client from caching data, it will not cause data to be cached on BC-Srv because clients are not configured to use Hosted Cache mode.
A user’s computer is running Microsoft Windows 7. System Protection is enabled.
A user reports that she accidentally copied an older version of a file over the current version. The Previous Versions tab for the file is shown in the exhibit.
You need to restore the latest saved previous version of the file.
What should you do?
- Enable shadow copy.
- Modify and save the file.
- Open Recovery in the Control Panel and select Restore your files.
- Open the Previous Versions tab of the Document library
Modify and save the file.
You should modify and save the file. The previous version of a file is only listed if the file has been modified since the last restore point was saved. Therefore, you can force the file to be shown by opening, modifying, and saving the file. After the older version is shown, you can select it and choose Restore. System Restore is only supported on NTFS partitions.
You do not need to enable shadow copy. Shadow copy is the technology used by System Protection to save previous versions of files. When System Protection is enabled, shadow copy is used automatically.
You should not open Recovery in the Control Panel and select Restore your files. You use this option to restore files from backup, not to restore a deleted file that was saved in a restore point.
You should not open the Previous Versions tab of the Document library. You can open Previous Versions for a folder or file, not the Documents library.
Your company has an Active Directory domain. The company’s network is shown in the exhibit.
A number of users have portable computers running Microsoft Windows 7. These users need to be able to connect to a selected set of servers on the corporate intranet from any location that has an Internet connection. Technicians need to be able to remotely manage the portable computers when they are connected to the intranet.
You need to configure the network infrastructure to support the requirements.
What should you do?
- Install a DirectAccess server on the corporate network.
- Install a Virtual Private Network (VPN) server on the perimeter network.
- Install a DirectAccess server on the perimeter network.
- Install a Virtual Private Network (VPN) server on the corporate network
Install a DirectAccess server on the perimeter network.
You should install a DirectAccess server on the perimeter network. DirectAccess allows client computers running Windows 7 or Windows Server 2008 to connect to intranet resources. A DirectAccess server must be a domain member and must be located on the perimeter network. It must have two network adapters: a public network adapter and a private network adapter. Both network adapters must be configured for IPv6. The public network adapter must be assigned two publicly-accessible consecutive IPv4 addresses.
You should not install a DirectAccess server on the corporate network. The DirectAccess server must be installed on the perimeter network.
You should not install a VPN server on the perimeter network or the corporate network. A VPN cannot work from some locations because it is blocked by firewalls. Also, remote management is not supported through a VPN connection.
A computer is running Microsoft Windows Vista. You want to perform a custom installation of Microsoft Windows 7 on the computer and migrate all user settings and documents. You plan to use a store on the network share \fs1\migration.
You need to estimate the amount of disk space required to store the settings.
What command should you use?
- ScanState.exe \fs1\migration /localonly /targetVista
- ScanState.exe \fs1\migration /genConfig:c:\spaceNeeded.xml
- ScanState.exe \fs1\migration /genConfig /targetVista
- ScanState.exe \fs1\migration /p:c:\spaceNeeded.xml
ScanState.exe \fs1\migration /p:c:\spaceNeeded.xml
You should use the following command:
ScanState.exe \fs1\migration /p:c:\spaceNeeded.xml
The ScanState command allows you to migrate settings to a store. When you run it with the /p option, it estimates the amount of disk space necessary to store the files. By specifying a filename after the /p option, you cause the estimation to be performed using User State Migration Tool (USMT) 4.0 algorithms. An Extensible Markup Language (XML) file with a format similar to the following is generated:
The storeSize reports the amount of disk space required at the location where the settings and documents will be stored. The temporarySpace reports the amount of temporary disk space required on the source machine while saving the files and on the target machine when restoring the files. When you use the /p option without a filename, the USMT 3.0 algorithm is used to calculate the space required.
You should not use the following command:
ScanState.exe \fs1\migration /localonly /targetVista
You use the /targetVista option when you are using USMT to migrate settings to a computer running Windows Vista. You use the /localonly option to migrate only settings and files that are located on the internal hard disk volumes, not on external drives or network shares. This command would create a store instead of just estimating the space required. However, the store would be optimized for Windows Vista.
You should not use the following commands:
ScanState.exe \fs1\migration /genConfig:c:\spaceNeeded.xml
Or
ScanState.exe \fs1\migration /genConfig:c:\spaceNeeded.xml /targetVista
The /genConfig option is used to generate a configuration file without creating a store. These commands would not estimate the space required because you did not include the /p option.
You have a computer running Windows 7. The computer can connect to computers on the local network, but not to computers on the Internet.
A portion of the Network and Sharing Center window is shown in the exhibit.
You need to resolve the problem.
What should you do?
- Change the network location of the Wireless Network Connection to Home network.
- Change the network location of the Wireless Network Connection 2 to Public network.
- Set the default gateway for the Wireless Network Connection to the correct value.
- Set the default gateway address for the Wireless Network Connection 2 to the correct value
Set the default gateway for the Wireless Network Connection to the correct value.
You should set the default gateway for the Wireless Network Connection to the correct value. Because you can access local resources, but not Internet resources, you know that the problem is caused by an invalid default gateway or an invalid subnet mask. When the default gateway is not correctly configured, the network is displayed as an unidentified public network.
You cannot change the network location of the Wireless Network Connection to Home network. You cannot change the network location until after you resolve the IP configuration issue.
You should not change the network location of the Wireless Network Connection 2 to Public network. The Wireless Network Connection 2 network is not currently connecting to a network. Also, you configure a network as a Public network to increase security when connecting to public Wi-Fi networks.
You should not set the default gateway address for the Wireless Network Connection 2 to the correct value. The Wireless Network Connection 2 network is not currently connecting to a network. The network settings that need to be reconfigured are those associated with Wireless Network Connection.
