★ 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:
https://www.certleader.com/70-680-dumps.html
Q211. - (Topic 2)
Your computer running Windows 7 Enterprise has two internal hard disks.
System protection is configured by default on the C: drive, which holds the operating system and installed applications.
The D: drive is a 500-GB hard disk formatted with the NTFS filing system, and you use it to store your personal files.
You want to store previous versions going back several months and therefore intend to reserve 200 GB of this disk for system protection.
You are not using either of your internal disks for backup; instead, you store your backups on a 1-TB external USB hard disk.
How do you configure system protection on your D: drive? (Choose all that apply; each answer forms part of the complete solution.)
A. Select Restore System Settings And Previous Versions Of Files
B. Select Only Restore Previous Versions Of Files
C. Set the Max Usage slider control to 40 percent
D. Set the Max Usage slider control to 4 percent
Answer: B,C
Q212. - (Topic 2)
You have a computer that runs Windows 7.
You view the properties of a file on the computer as show in the exhibit. (Click the Exhibit button.)
You need to ensure that you can configure permissions on the file.
What should you do?
A. From Folder Options, modify the View settings.
B. Move the file to a disk that has the NTFS file system.
C. Open Windows Explorer by using elevated privileges.
D. Hold the SHIFT key, right-click the file, and click Properties.
Answer: B
Explanation:
Missing options hints not on NTFS. On NTFS volumes, you can set security permissions on files and folders. These permissions grant or deny access to the files and folders. You can view security permissions for files and folders by completing the following steps: 1. In Windows Explorer, right-click the file or folder you want to work with. 2. From the pop-up menu, select Properties, and then in the Properties dialog box click the Security tab.3. In the Name list box, select the user, contact, computer, or group whose permissions you want to view. If the permissions are dimmed, it means the permissions are inherited from a parent object.
Q213. - (Topic 3)
You have a computer that runs Windows 7.
You install a third-party Web browser.
You discover that HTML files are no longer associated with Windows Internet Explorer.
You need to ensure that Internet Explorer starts whenever a HTML file is opened.
What should you do from Internet Options?
A. Open the Connections tab and click Setup.
B. Open the General tab and click Use default.
C. Open the Programs tab and click Make default.
D. Open the Programs tab and click Manage add-ons.
Answer: C
Explanation:
Change your default web browser
This information applies to Internet Explorer 8 or Internet Explorer 7 running on Windows 7,
Windows Vista, Windows Server 2008, Windows XP Service Pack 2 and Service Pack 3, and Windows Server 2003.
To make Internet Explorer your default web browser
1. Click to open Internet Options.
2. Click the Programs tab, and then click Make default.
Q214. - (Topic 4)
You create a new virtual hard disk (VHD) on a Windows 7 Enterprise computer. Then you install Windows 7 on the VHD.
After you reboot the computer, the Windows 7 boot menu shows two different Windows 7 installations titled "Windows 7".
You need to ensure that the Windows 7 boot menu differentiates between the two Windows 7 installations.
What should you do?
A. Add a boot image in WDS.
B. Run the ImageX command with the /Mount parameter.
C. Run thePEImg/Prep command.
D. Use Sysprep with ar\ answer file and set the UpdatelnstalledDrivers option in the answer file to No.
E. Run the DiskPart command and the Attach command option.
F. Create a capture image in WDS.
G. Run the Dism command with the /Mount-Wimoption.
H. Run the BCDEdit command.
I. Run the Dism command with the /Add-Package option.
J. Run the Dism command with the /Add-Driver option.
K. Use Sysprep with an answer file and set the PersistAllDevicelnstalls option in the answer file to False.
L. Use Sysprep with an answer file and set the UpdatelnstalledDrivers option in the answer file to Yes.
M. Use Sysprep with an answer file and set the PersistAllDevicelnstalls option in the answer file to True.
N. Run the Start /w ocsetup command.
Answer: H
Q215. - (Topic 3)
You need to back up your Encrypting File System (EFS) certificate. You must achieve this goal in the minimum amount of time.
What should you do?
A. Run Cipher.exe /x.
B. Run Ntbackup.exe /p.
C. From Backup and Restore, click Back up now.
D. From Backup and Restore, click Create a system image.
Answer: A
Explanation:
Cipher is used to manage certificates.
NOT Backup and Restore:Only the EFS certificate needs to be backed up and time is a factor.
Q216. - (Topic 5)
You use a portable computer that has Windows 7 SP1 Ultimate installed.
You update the driver for the computer's video card and the computer becomes unresponsive.
You need to be able to roll back the video card driver.
What should you do?
A. Restart the computer in safe mode.
B. Start the computer, press F8, and then select Repair Your Computer.
C. Boot the computer from a Windows Recovery Environment (Windows RE) disk, and then restore the system image.
D. Start the computer, press F8, and then select Debugging Mode.
Answer: A
Q217. - (Topic 6)
You are preparing to migrate from Windows Vista to Windows 7.
You need to use the User System Migration Tool (USMT) XML files.
Which two of these are migrated by using only the default USMT XML files? (Each correct answer presents part of the solution. Choose two. )
A. Application settings for Office 2010 and Windows Mail
B. ACLs for folders outside the user profile
C. Data from the %PROGRAMDATA% folder
D. Installed network printers
Answer: A,D
Explanation: A:
* The original version of the USMT 4. 0 doesn't support Office 2010. There was an update released in February 2011 that adds support for Office 2010.
* Windows Mail (Microsoft Outlook Express Mail, or . dbx, files are migrated from Windows XP)
D: Network printer mapping (not migrated when using offline backup)
Note: In the USMT, XML templates control the data being migrated from the machine. The default templates migrate the following: Accessibility settings Address book Command-prompt settings Desktop wallpaper (not migrated when using offline backup) Encrypting File System (EFS) files Favorites Folder options Fonts Group membership Internet Explorer settings (not migrated when using offline backup) Microsoft ODBC settings Mouse and keyboard settings Network drive mapping
(D) Network printer mapping (not migrated when using offline backup)
Offline files (not migrated when using offline backup)
Phone and modem options (not migrated when using offline backup)
Remote Access Service (RAS) connection and phone book (. pbk) files
Regional settings (not migrated when using offline backup)
Remote Access
Taskbar settings (not migrated when using offline backup)
(A) Windows Mail (Microsoft Outlook Express Mail, or . dbx, files are migrated from Windows XP)
Windows Media Player (not migrated when using offline backup)
Windows Rights Management
Q218. - (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:\windows\system32
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.
Q219. HOTSPOT - (Topic 4)
A user is attempting to connect to a secure remote Microsoft SQL database on a computer running Windows 7 Professional. The computer communicates on port 1433.
A rule in Windows Firewall with Advanced Security allows communication. The user cannot connect to the database on the currently defined protocol due to an error in protocol type.
You need to ensure that users can connect to the database.
Which setting should you choose? (To answer, select the appropriate setting in the work area.)
Answer:
Q220. - (Topic 5)
You have a computer that has the following hardware configuration:
1.6-gigahertz (GHz) processor (64-bit)
8-GB RAM
500-GB hard disk
Graphics card that has 128-MB RAM
You need to select an edition of Windows 7 to meet the following requirements:
Support DirectAccess
Support Windows XP Mode
Use all of the installed memory
Support joining an Active Directory domain
Which edition should you choose?
A. Windows 7 Enterprise (x86)
B. Windows 7 Professional (64-bit)
C. Windows 7 Enterprise (64-bit)
D. Windows 7 Ultimate (x86)
Answer: C