we provide Approved Microsoft 70 680 pdf exam guide which are the best for clearing 70 680 practice test test, and to get certified by Microsoft TS:Windows 7,Configuring. The microsoft 70 680 Questions & Answers covers all the knowledge points of the real 70 680 exam exam. Crack your Microsoft exam 70 680 Exam with latest dumps, guaranteed!
♥♥ 2021 NEW RECOMMEND ♥♥
Free VCE & PDF File for Microsoft 70-680 Real Exam (Full Version!)
★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions
Free Instant Download NEW 70-680 Exam Dumps (PDF & VCE):
Available on:
http://www.surepassexam.com/70-680-exam-dumps.html
Q111. - (Topic 2)
Which of the following steps will keep a Microsoft Word shortcut icon on the Taskbar after the next reboot?
A. Copy and paste a Microsoft Word icon to the Taskbar.
B. Right click on the Microsoft Word icon and choose, "Staple to Superbar".
C. Right click on the Microsoft Word icon and choose, "Pin this programm to taskbar".
D. Open Microsoft Word. While the Icon is on the Taskbar, right click the icon and choose, "Pin this program to taskbar".
Answer: D
Q112. - (Topic 1)
You have a computer named Computer1 that runs Windows Vista and a computer named Computer2 that runs Windows 7. You plan to migrate all profiles and user files from Computer1 to Computer2.
You need to identify how much space is required to complete the migration.
What should you do?
A. On Computer1 run Loadstate c:store /nocompress
B. On Computer1 run Scanstate c:store /nocompress /p
C. On Computer2 run Loadstate \computer1store /nocompress
D. On Computer2 run Scanstate \computer1store /nocompress /p
Answer: B
Explanation:
ScanState You run ScanState on the source computer during the migration. You must run ScanState.exe on computers running Windows Vista and Windows 7 from an administrative command prompt. When running ScanState on a source computer that has Windows XP installed, you need to run it as a user that is a member of the local administrators group. The following command creates an encrypted store named Mystore on the file share named Migration on the file server named Fileserver that uses the encryption key Mykey: scanstate \fileservermigrationmystore /i:migapp.xml /i:miguser.xml /o /config:config.xml /encrypt /key:"mykey" Space Estimations for the Migration StoreWhen the ScanState command runs, it will create an .xml file in the path specified. This .xml file includes improved space estimations for the migration store. The following example shows how to create this .xml file: Scanstate.exe C:MigrationLocation [additional parameters] /p:"C:MigrationStoreSize.xml" To preserve the functionality of existing applications or scripts that require the previous behavior of USMT, you can use the /p option, without specifying "pathtoafile", in USMT 4.0. If you specify only the /p option, the storage space estimations are created in the same manner as with USMT 3.x releases. User State Migration ToolUSMT 4.0 is a command-line utility that allows you to automate the process of user profile migration. The USMT is part of the Windows Automated Installation Kit (WAIK) and is a better tool for performing a large number of profile migrations than Windows Easy Transfer. The USMT can write data to a removable USB storage device or a network share but cannot perform a direct side-by-side migration over the network from the source to the destination computer. The USMT does not support user profile migration using the Windows Easy Transfer cable. USMT migration occurs in two phases, exporting profile data from the source computer using ScanState and importing profile data on the destination computer using LoadState.
Q113. - (Topic 3)
You have a computer that runs Windows 7 Home Premium.
You need to upgrade the computer to Windows 7 Ultimate. You must achieve this goal in the minimum amount of time.
What should you do?
A. Perform a Windows Anytime Upgrade.
B. Download and run the Windows 7 Upgrade Advisor.
C. Insert the Windows 7 installation media. From the Install Windows dialog box, select the Upgrade option.
D. Start the computer from the Windows 7 installation media. From the Install Windows dialog box, select the Upgrade option.
Answer: A
Explanation:
Windows Anytime Upgrade With Windows Anytime Upgrade, shown in Figure,you can purchase an upgrade to an application over the Internet and have the features unlocked automatically. This upgrade method is more suitable for home users and users in small businesses where a small number of intra-edition upgrades is required.
Windows Anytime Upgrade
Q114. - (Topic 5)
You are performing a native VHD boot from Windows Vista to Windows 7 Professional. Windows 7 Professional is installed on F: Windows7Pro.vhd.
You run the bcdedit /copy {current} /d "Windows 7 VHD" command. The boot configuration data is enumerated as shown in the exhibit. (Click the Exhibit button.)
You need to ensure that the following requirements are met:
. Both operating systems are bootable after the Power On Self-Test (POST).
. Windows 7 VHD is selected as the default boot entry.
Which three commands should you run? (Each correct answer presents part of the solution. Choose three.)
A. Bcdedit /default {ded5a252-7077-11e0-8ac8-a2d217dce703}
B. Bcdedit /set {ded5a24e-7077-11e0-8ac8-a2d217dce703} osdevice vhd=[f:]Windows7Pro.vhd
C. Bcdboot C:windows /s E:
D. Bcdedit /set {ded5a24e-7077-11e0-8ac8-a2d217dce703} device vhd=[f:]Windows7Pro.vhd
E. Bcdedit /set {ded5a252-7077-11e0-8ac8-a2d217dce703} device vhd=[f:]Windows7Pro.vhd
F. Bcdedit /default {current}
G. Bcdedit /set {ded5a252-7077-11e0-8ac8-a2d217dce703} osdevice vhd=[f:]Windows7Pro.vhd
Answer: A,E,G
Q115. - (Topic 5)
You administer client computers that have Windows 7 Enterprise installed.
A server named Server1 has an IP address of 10.10.4.56. The server accepts Remote Desktop connections at a custom port 10876.
You need to connect to the server from a client computer by using Remote Desktop.
What should you do?
A. From an elevated command prompt, run mstsc.exe 10.10.4.56 port: 10876.
B. From the Advanced tab of your Remote Desktop connection, configure the port of Server1 in the Connect from anywhere option.
C. From the General tab of your Remote Desktop connection, type 10.10.4.56:10876 in the Computer field.
D. From the Advanced tab of your Remote Desktop connection, configure the IP address and port of Server1 as the RD Gateway Server.
Answer: C
Explanation:
Note:
* mstsc.exe allows you to initiate terminal services commands via the command line, and forms an important part of this additional Windows service.
Incorrect:
Not A: Incorrect syntax.
Q116. - (Topic 2)
You have a portable computer named Computer1 and a desktop computer named Computer2. Both computers run windows 7.
On computer2, you create a share named Share1 by using Advanced Sharing feature.
You need to ensure that when you connect to Share1 from Computer1, the files that you open are automatically cached.
What should you do?
A. On Computer1, modify the Offline Files settings.
B. On Computer1, modify the User Profile settings.
C. On Computer2, modify the properties of Share1.
D. On Computer2, modify the file sharing connection settings for the HomeGroup
Answer: C
Explanation:
The caching feature of Shared Folders ensures that users have access to shared files even when they are working offline without access to the network. You can also use Shared Folders or Share and Storage Management to enable BranchCache on shared resources. The BranchCache feature in Windows. 7 or Windows Server 2008 R2 enables computers in a branch office to cache files downloaded from this shared folder, and then securely serve the files to other computers in the branch. To set caching options for a shared folder by using the Windows interface 1. Open Computer Management.2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.3. In the console tree, click System Tools, click Shared Folders, and then click Shares.4. In the results pane, right-click the shared folder, and then click Properties.5. On the General tab, click Offline Settings, configure the offline availability options as appropriate and then click OK. Offline availability optionsSelect the following offline availability option for each shared folder: All files and programs that users open from the share are automatically available offlineWhenever a user accesses the shared folder or volume and opens a file or program in it, that file or program will be automatically made available offline to that user. Files and programs that are automatically made available offline will remain in the Offline Files cache and synchronize with the version on the server until the cache is full or the user deletes the files. Files and programs that are not opened are not available offline.
Q117. - (Topic 2)
You have a computer that runs Windows 7.
You create an application shim for a third-party application by using the Microsoft Application Compatibility Toolkit (ACT).
You need to ensure that the application shim is applied the next time you run the application.
What should you do first?
A. Run Sdbinst.exe.
B. Run Msiexec.exe.
C. Right-click the application executable file and modify the compatibility settings.
D. Right-click the application executable file and modify the advanced security settings.
Answer: A
Explanation:
Deploying a custom shim database to users requires the following two actions: Placing the custom shim database (*.sdb file) in a location to which the user's computer has access (either- locally or on the network)- Calling the sdbinst.exe command-line utility to install the custom shim database locally
Demystifying Shims - or - Using the Application Compatibility Toolkit to make your old stuff work with your new stuff
What is a Shim? A shim is one of the very few four-letter words in use by Microsoft that isn't an acronym of some sort. It's a metaphor based on the English language word shim, which is an engineering term used to describe a piece of wood or metal that is inserted between two objects to make them fit together better. In computer programming, a shim is a small library which transparently intercepts an API, changes the parameters passed, handles the operation itself, or redirects the operation elsewhere. Shims can also be used for running programs on different software platforms than they were developed for.
How Shims work The Shim Infrastructure implements a form of Application Programming Interface (API) hooking. The Windows API is implemented using a collection of DLLs. Each application built for Windows imports these DLLs, and maintains a table of the address of each of these functions in memory. Because the address of the Windows functionality is sitting in a table, it is straightforward for the shim engine to replace this address with the address of the shim DLL instead. The application is generally unaware that the request is going to a shim DLL instead of to Windows itself, and Windows is unaware that the request is coming from a source other than the application (because the shim DLL is just another DLL inside the application's process). In this particular case, the two objects are the application program and Windows, and the shim is additional code that causes the two to behave better together, as shown below:
Figure 1 Before the shim is applied, the application interacts directly with Windows.
Figure 2 After the shim is applied, the application interacts with Windows indirectly; the shim code is injected and can modify the request to Windows, the response from Windows, or both.
Specifically, it leverages the nature of linking to redirect API calls from Windows to alternative code—the Shim. Calls to external binary files take place through the Import
Address Table (IAT). Consequently, a call into Windows looks like:
Figure 1
Application calling into Windows through the IAT Specifically, you can modify the address of the Windows function resolved in the import table, and then replace it with a pointer to a function in the alternate shim code, as shown in
Figure 2
This redirection happens for statically linked .dll files when the application is loaded. You can also shim dynamically linked .dll files by hooking the GetProcAddress API. Why Should we be using Shims This is the cost-saving route—help the application by modifying calls to the operating system before they get there. You can fix applications without access to the source code, or without changing them at all. You incur a minimal amount of additional management overhead (for the shim database), and you can fix a reasonable number of applications this way. The downside is support as most vendors don't support shimmed applications. You can't fix every application using shims. Most people typically consider shims for applications where the vendor is out of business, the software isn't strategic enough to necessitate support, or they just want to buy some time. For example, a very commonly used shim is a version-lie shim. To implement this shim, we intercept several APIs that are used to determine which version of Windows the application is running on. Normally, this information is passed on to Windows itself, and it answers truthfully. With the shim applied, however, these APIs are intercepted. Instead of passing on the request to Windows, a different version of Windows is returned (for example, Windows XP instead of Windows 7). If the application is programmed to run only on Windows XP, this is a way to trick the application into believing it's running on the correct OS. (Frequently this is all that is necessary to resolve an application compatibility problem!) There are a huge number of tricks you can play with shims. For example: The ForceAdminAccess shim tries to trick the application into believing that the current user is a member of the local Administrator group, even if he is not. (Many applications outright fail if you are not a local administrator, though you may be able to use other tricks, such as UAC File and Registry Virtualization, to resolve the issues that caused the check in the first place.) How it implements this check can be fairly straightforward. For example, this shim intercepts the API IsUserAnAdmin from shell32.dll. The complete source code of the shimmed function (which has wonderful performance characteristics compared to the actual API) is simply return TRUE. The WrpMitigation shim tricks application installers into believing they can write to files that are protected by Windows Resource Protection (WRP). If you try to write to a file that's protected, the shim first creates a new temporary file, marks it to be deleted once the handle is closed, and then returns the handle to the temporary file as if it were the actual protected file. The application installs the crusty old version of kernel32.dll or shell32.dll (or whichever other file it picked up while it was being packaged) into a temp file, but then that temp file goes away and the matching, patched, up-to-date version of the protected file remains on the file system. So, WRP can still ensure that you don't end up with an ancient copy of shell32.dll from Windows 95 on your computer, but the installer won't fail with ACCESS_DENIED when you use this shim. The CorrectFilePaths shim can redirect files from one location to another. So, if you have an application that is trying to write to c:myprogramdir (which isn't automatically fixed using UAC File and Registry Virtualization), you can redirect the files that are modified at runtime to a per-user location. This allows you to run as a standard user without having to loosen access control lists (ACLs), because you know your security folks hate it when you loosen ACLs. NOTE: As shims run as user-mode code inside a user-mode application process, you cannot use a shim to fix kernel-mode code. For example, you cannot use shims to resolve compatibility issues with device drivers or with other kernel-mode code. (For example, some antivirus, firewall, and antispyware code runs in kernel mode.)
When can we use a Shim: You acquired the application from a vendor that is no longer in business. Several applications are from vendors that have since gone out of business; so clearly, support is no longer a concern. However, because the source code is not available, shimming is the only option for compatibility mitigation. You developed the application internally. While most customers would prefer to fix all their applications to be natively compatible, there are some scenarios in which the timing does not allow for this. The team may not be able to fix all of them prior to the planned deployment of new version of Windows, so they may choose to shim the applications that can be shimmed and modify the code on the ones where shims are insufficient to resolve the compatibility issue. You acquired the application from a vendor that will eventually be releasing a compatible version, but support is not critical. When an off-the-shelf application is neither business critical nor important, some customers use shims as a stopgap solution. Users could theoretically wait until a compatible version is available, and its absence would not block the deployment, but being able to provide users with a shimmed and functional version can bridge that gap until a compatible version is available.
Creating an Application Compatibility Shim If you are trying to run an application that was created for 2000 or XP and had problems running in Windows 7, you could always turn on compatibility mode for the executable on your machine. However if you are trying to create a shim that could be used on other machines as well, you could use the following instructions to create the shim and send it. It is a very small size and once executed, will always be associated with that executable on that machine.
ACT is the Application Compatibility Toolkit. Download it from here: http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en
Once we launch the Compatibility Administrator Tool, from Start Menu – Microsoft Application Compatibility Toolkit:
Right-click on New Database:
Choose Application Fix here. In this below dialog, give the application details and the executable you would want to fix:
1. Type the name of the program to fix
2. Type the vendor name
3. Browse to location of executable
When you press the next button, you will get to see the list of the compatibility modes listed by default. If you have an issue with just version incompatibility then choose the version in which the application was working earlier. At this point I have already determined that Windows 2000 compatibility mode will work for this program.
In the list box, scroll down and select "Windows 2000".
In the next window (when you have combination of shims to be chosen). As shown below, you have lots of shims to choose from. Select all the shims which would fix your application.
Click on Finish. This will give you the complete summary of the application and the fixes applied.
Now you need to save this shim database file (A small database including the shim information is created), and install it. You can either install it by right-clicking on the shim and pressing the install button, or by using a command-line option, sdbinst.exe <database. sdb>.
NOTE: "sdbinst.exe" is already located by default in c:windowssystem32
Once the Application Compatibility Database is installed, we can run the program from the location specified earlier (in the first window). Now the program should be running in the Compatibility mode that you specified during the process.
Q118. - (Topic 3)
You have a computer named Computer1 that runs Windows 7. You have a server named Server1 that runs Windows Server 2008. Server1 has a file share named Share1.
The network configuration for Computer1 is shown in the exhibit. (Click the Exhibit button.)
You attempt to connect to \Server1Share1 and receive the following error message: Windows cannot access \Server1Share1. From Computer1, you successfully ping Server1.
You need to connect to \Server1Share1.
What should you enable on Computer1?
A. Client for Microsoft Networks
B. File and Printer Sharing for Microsoft Networks
C. Link-Layer Topology Discovery Mapper I/O Driver
D. Link-Layer Topology Discovery Responder
Answer: A
Explanation:
Client for Microsoft Networks Allows the computer to access resources on a Microsoft network.File and Printer Sharing for Microsoft NetworksEnables other computers to access resources on your computer in a Microsoft network (and other networks).Link-layer Topology Discovery Mapper I/O DriverDiscovers and locates other computers, devices, and network infrastructure features on the network, and determines network bandwidth.
Link-layer Topology Discovery ResponderAllows a computer to be discovered and located on the network.
Q119. - (Topic 1)
Your company has an internal Web site that requires HTTPS. The Web site's certificate is self-signed. You have a computer that runs Windows 7 and Windows Internet Explorer 8. You use HTTPS to browse to the Web site and receive the following warning message. "There is a problem with this website's security certificate."
You need to prevent the warning message from appearing when you access the Web site. What should you do?
A. From Internet Explorer, enable InPrivate Browsing.
B. From Internet Explorer, add the Web site to the Trusted sites zone.
C. From Certificate Manager, import the Web sites certificate into your Personal store.
D. From Certificate Manager, import the Web sites certificate into your Trusted Root Certification Authorities store.
Answer: D
Explanation:
Certificate Manager A certificate manager can approve certificate enrollment and revocation requests, issue certificates, and manage certificates. This role can be configured by assigning a user or group the Issue and Manage Certificatespermission. When you assign this permission to a user or group, you can further refine their ability to manage certificates by group and by certificate template. For example, you might want to implement a restriction that they can only approve requests or revoke smart card logon certificates for users in a certain office or organizational unit that is the basis for a security group.Importing CertificatesYou may restore certificates and the corresponding private keys from a file.
6. Right-click the certificate store you want to import, and click Install PFX on the context menu.
7. The Certificate Import Wizard launches. Click Next.
8. In the File name text box, type the name of the certificate file that you want to import. Alternatively, you can find the file by clicking Browse.
9. Click Next. If the file specified is a Personal Information Exchange–PKCS #12 (*.pfx), you will be prompted for the password. Enter the password to import the file. Click Next.
10. On the next page, select where you'd like to store the certificate. Click Next.
11. The next wizard page contains summary information about the file that you are importing. Click Finish to import the file. The certificate(s) are now ready for use by the system.
Q120. - (Topic 2)
You have a computer that runs windows 7 professional.
A removable drive is attached to the computer.
You need to protect data on the removable drive by using Bitlocker To Go.
What should you do first?
A. Upgrade the computer to Windows 7 Enterprise.
B. Install all Windows Updates for Windows 7 Professional.
C. Issue a digital certificate for the Encryption File System (EFS).
D. Select the Encrypt contents to secure data checkbox from the properties on the removable drive.
Answer: A
Explanation:
Windows 7 ProfessionalWindows 7 Professional is available from retailers and on new computers installed by manufacturers. It supports all the features available in Windows Home Premium, but you can join computers with this operating system installed to a domain. It supports EFS and Remote Desktop Host but does not support enterprise features such as AppLocker, DirectAccess, BitLocker, and BranchCache.Windows 7 Enterprise and Ultimate EditionsThe Windows 7 Enterprise and Ultimate editions are identical except for the fact that Windows 7 Enterprise is available only to Microsoft's volume licensing customers, and Windows 7 Ultimate is available from retailers and on new computers installed by manufacturers. The Enterprise and Ultimate editions support all the features available in other Windows 7 editions but also support all the enterprise features such as EFS, Remote Desktop Host, AppLocker, DirectAccess, BitLocker, BranchCache, and Boot from VHD.