70-680 Exam
How to pass 70 680 exam in Jan 2021
Proper study guides for Renew Microsoft TS:Windows 7,Configuring certified begins with Microsoft microsoft 70 680 preparation products which designed to deliver the Highest Quality 70 680 pdf questions by making you pass the 70 680 exam test at your first time. Try the free 70 680 practice test demo right now.
Q261. - (Topic 5)
You use a desktop computer that has Windows 7 Ultimate SP1. The relevant portions of the computer configuration are shown in the following exhibits:
The Disk Management console (Click the Exhibit button.)
The System Properties window (Click the Exhibit button.)
The System protection for Local Disk C window (Click the Exhibit button.)
You need to create a backup copy of a 40-GB Virtual Hard Disk (VHD) file in a local folder on drive C.
What should you do?
A. Delete restore points.
B. Create a restore point.
C. Perform a system restore.
D. Search for the file in the Recycle Bin.
E. Increase disk space used for system protection.
F. Copy the file from a previous version of a folder.
G. Set restore settings to Only restore previous versions of files.
H. Run the cipher /x command from the elevated command prompt.
I. Run the vssadmin list volumes command from the elevated command prompt.
J. Run the vssadmin list shadows command from the elevated command prompt.
K. Run the compact /U <file_name> command from the elevated command prompt.
Answer: A
Q262. - (Topic 3)
You have a computer that runs Windows 7.
You install Windows XP in a new partition on the computer and discover that you can no longer start Windows 7.
You need to start Windows 7 in the minimum amount of time.
What should you do?
A. From Windows XP, modify the default path in the boot.ini file.
B. From Windows XP Recovery Console, run the Fixboot command.
C. Start the computer from the Windows 7 installation media and select Install now.
D. Start the computer from the Windows 7 installation media and run Startup Repair.
Answer: D
Explanation: When configuring a new computer to boot between multiple operating systems, it is also necessary to install operating systems in the order that they were released. For example, if you want to boot between Windows XP and Windows 7 on a new computer, you need to install Windows XP before you install Windows 7. If you install Windows XP after Windows 7, the Windows XP installation routine cannot recognize the Windows 7 operating system installation and the computer only boots into Windows XP. It is possible to repair the computer from this point using Windows 7 startup repair so that it dual-boots, but the simplest course of action is just to install the operating systems in the order in which they were released
Q263. - (Topic 3)
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 Window 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 (64-bit)
B. Windows 7 Enterprise (x86)
C. Windows 7 Professional (64-bit)
D. Windows 7 Ultimate (x86)
Answer: A
Explanation:
The only applicable solution is Windows 7 Enterprise (64-bit) as for the following reasons:All versions are support Hardware wise.Requirements:Windows 7 Home Premium, Professional, Ultimate, and Enterprise editions have the following minimum hardware requirements:
-1 GHz 32-bit (x86) or 64-bit (x64) processor- 1 GB of system memory- A 40-GB hard disk drive (traditional or SSD) with at least 15 GB of available space- A graphics adapter that supports DirectX 9 graphics, has a Windows Display Driver Model (WDDM) driver,- Pixel Shader 2.0 hardware, and 32 bits per pixel and a minimum of 128 MB graphics memory
XP Mode Windows XP Mode is a downloadable compatibility option that is available for the Professional, Enterprise, and Ultimate editions of Windows 7. Windows XP Mode uses the latest version of Microsoft Virtual PC to allow you to run an installation of Windows XP virtually under Windows 7.
Use all of the installed memory The x86 version supports a maximum of 4 GB of RAM, whereas the x64 version supports a maximum of 8 GB of RAM.
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 Editions The 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.
Q264. - (Topic 4)
You have a computer that runs Windows 7. You have a system image of the computer. You need to restore a single file from the system image. You must achieve this goal in the
minimum amount of time. What should you do first?
A. Restart the computer and run System Restore.
B. Restart the computer and run System Image Recovery.
C. From Backup and Restore, select Restore my files.
D. From Disk Management, select Attach VHD.
Answer: D
Q265. - (Topic 1)
You work in an international company which is named Wiikigo. Before entering this company, you have two years of experience in the IT field, as well as experience implementing and administering any Windows client operating system in a networked environment. You are professional in installing, upgrading and migrating to Windows 7, deploying Windows 7, and configuring Hardware and Applications and son on. You are in charge of a computer that runs Windows Vista. You have Windows 7 installed on a new partition on the computer. You have to make sure that the computer always starts Windows Vista by default. So what action should you perform to make sure of this?
A. In order to make sure that the computer always starts Windows Vista by default, a boot.ini file should be created in the root of the Windows 7 partition.
B. In order to make sure that the computer always starts Windows Vista by default, a boot.ini file should be created in the root of the Windows Vista partition.
C. In order to make sure that the computer always starts Windows Vista by default, Bcdedit.exe should be run and the /default parameter should be specified.
D. In order to make sure that the computer always starts Windows Vista by default, Bcdedit.exe should be run and the /bootems parameter should be specified.
Answer: C
Q266. HOTSPOT - (Topic 4)
You are running windows 7 on a portable computer. A custom power plan named "On The Move" is optimized for battery life.
The computer enters sleep mode when the portable computer is closed.
You need to change a setting so that when you close the portable computer, nothing happens.
Which setting should you change? (To answer, select the appropriate setting in the work area.)
Answer:
Q267. - (Topic 5)
All client computers in your company network have Windows 7 Professional installed. The computers are configured with automatic scheduled Microsoft updates installation.
You receive a support call indicating that after the recently installed update, one of the business applications is unable to start on the computers.
You need to remove the most recent Microsoft update from the computers.
What should you do first?
A. From the Programs and Features, open the Installed Updates window.
B. From the Services console, open the Windows Update service.
C. From the Event Viewer, open the System log.
D. From the Task Scheduler, view the WindowsBackup node.
Answer: C
Q268. - (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 \\computer1\store /nocompress
D. On Computer2 run Scanstate \\computer1\store /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 \\fileserver\migration\mystore /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.
Q269. DRAG DROP - (Topic 4)
You support desktop computers that have Windows 7 Enterprise installed. All computers are configured with system protection on drive C and with a backup task that runs daily at midnight.
One of the users reports that in the morning she has installed a new version of a browser. After the installation, a follower that has favorite shortcuts was replaced with new content.
You need to restore the most recent version of the folder that contains the user data.
What should you do? (To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order).
Answer:
Q270. - (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.