The Examcollection.org is a credible site to supply anyone with the most accurate as well as original Microsoft Microsoft demos. Our own experts constantly update the Microsoft practice questions as well as answers according to the particular latest Microsoft 70-680 syllabus. There exists a little adjust in the true Microsoft Microsoft exam every occasion. Our staff members will revise the Microsoft 70-680 exam dumps in good occasion.
2021 Mar 70-680 practice test
Q201. - (Topic 1)
You have a computer that runs Windows 7.
The IPv6 address of the computer is configured automatically.
You need to identify the IPV6 address of the computer.
What should you do?
A. At the command prompt, run Netstat.
B. At the command prompt run Net config.
C. From the network connection status, click Details.
D. From network connection properties, select Internet Protocol Version 6 (TCP/IPv6) and click Properties.
Answer: C
Explanation: You can view a list of all the connection interfaces (wired and wireless) on a computer by opening Network And Sharing Center and clicking Change Adapter Settings. You can right-click any network connection and select Status. If you click Details on the Local Area Connection Status dialog box, you access the Network Connection Details information box. You can configure wireless connection behavior by clicking Change Adapter Settings in Network And Sharing Center, right-clicking your wireless adapter, and clicking Status. Clicking Details on the Status dialog box displays the adapter configuration.
Q202. - (Topic 5)
You use a desktop computer that has Windows 7 SP1 Ultimate installed. As part of a disaster recovery plan, you perform regular data backups and system image backups of the desktop computer.
The hard disk drive in the computer fails after a power outage. You replace the hard disk drive and restart the desktop computer by using the Windows 7 SP1 installation media.
You need to recover the computer to its previous state.
What should you do?
A. Use Startup Repair.
B. Use the command prompt.
C. Use System Image Recovery.
D. Perform a system restore.
Answer: C
Explanation:
System Image Recovery
Enables you to implement a System Image restore. You would choose this option if your hard disk failed or needed to be wiped. If system changes are causing problems, you would choose the System Restore option.
NOT Startup Repair
Automatically fixes problems that prevent Windows from starting. If Windows 7 had boot problems during a previous restart, a normal boot (without accessing the Advanced Boot dialog box) gives you the option of selecting Startup Repair.
NOT System Restore
Gives you another method of starting a system restore to a previous restore point. Because you can access this menu when you boot from a DVD-ROM, this lets you repair your system when recent changes to system settings prevent your computer from booting normally.
NOT Command Prompt
Gives access to the file system, volumes, and files through a command-line interface.
Q203. - (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.
Q204. - (Topic 2)
You have a computer that runs windows 7.
You log on to the computer by using a user account that is a member of Administrator Group.
From Windows Explorer you open C:\windows\system32\drivers\etc\hosts in notepad.
You attempt to save the file and receive the save as dialog box.
You need to ensure that you can save changes to c:\windows\system32\drivers\
What should you do?
A. Stop the windows search service
B. Remove the inherited permissions from the file.
C. Start Windows Notepad by using elevated privileges.
D. Change the user account control (UAS) settings to Notify Me Only when programs try to make changes to my computer.
Answer: C
Explanation:
Windows 7 does not allow applications to write data to these secure locations.
User Account Control (UAC)UAC is a security feature of Windows 7 that informs you when
the action that you want to undertake requires an elevation of privileges. If you logged on with a user account that was a member of the local administrators group in previous versions of Microsoft Windows, such as Windows XP, you automatically had administrator-level access at all times. This, by itself, was not a problem because recommended good practice was that people logged on with accounts that were members of the local administrator group only when they needed to do something related to administration. The problem with this is that people tended to use their administrator account as their normal user account. It was convenient for them because they did not have to log off and log on again each time they wanted to do something related to systems administration. Unfortunately, this behavior presented a security problem because any program run by a user logged on with an administrative account runs with the rights and privileges of that user. UAC resolves this problem by allowing a user that is a member of the local Administrators group to run as a standard user most of the time and to briefly elevate their privileges so that they are running as administrators when they attempt to carry out specific administration-related tasks.Privilege elevationAll users of clients running Windows 7 run with the rights of a standard user. When a user attempts an act that requires administrative privileges, such as creating a new user account, her rights need to be raised from those of a standard user to those of an administrative user. This increase in rights is termed privilege elevation. UAC is a gateway to privilege elevation. It allows users who are members of the local Administrators group to access administrative rights, but ensures that the person accessing the Administrative rights is aware that they are doing so. This privilege elevation occurs only for a specific task. Another task executed at the same time that also requires privilege elevation generates its own UAC
Q205. - (Topic 2)
You have a computer that runs Windows Vista.
You install Windows 7 on a new partition on the computer.
You need to ensure that the computer always starts Windows Vista by default.
What should you do?
A. Run Bcdedit.exe and specify the /default parameter.
B. Run Bcdedit.exe and specify the /bootems parameter.
C. Create a boot.ini file in the root of the Windows 7 partition.
D. Create a boot.ini file in the root of the Windows Vista partition.
Answer: A
Explanation:
The Bcdedit.exe utility allows you to manage boot configuration./default - Sets the default entry that the boot manager willl use./bootems - Enable or disables Emergency Management Services for a boot application.NOT boot.ini:Windows (specifically Ntldr) uses
Most up-to-date 70-680 real exam:
Q206. - (Topic 3)
You have a computer named Computer1 that runs Windows 7.
Computer1 has a shared printer.
You need to configure Computer1 so that only Administrators are authorized to shut down the computer.
What should you do?
A. From User Accounts, modify the user profiles settings.
B. From User Accounts, modify the User Account Control (UAC) settings.
C. From the local computer policy, modify the Security Options.
D. From the local computer policy, modify the User Rights Assignment.
Answer: D
Explanation:
Shut down the system Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment Description Determines which users logged on locally to the computer can shut down the operating system using the Shut Down command. This user right is defined in the Default Domain Controller Group Policy object (GPO) and in the local security policy of workstations and servers.
Q207. - (Topic 4)
Your company network has a single-domain Active Directory forest. The forest functional level is set to Windows Server 2008 R2. All computers are members of the domain.
You plan to deploy Windows BitLocker Drive Encryption (BitLocker) on portable computers that have Windows 7 Enterprise installed.
You need to be able to automatically back up recovery passwords for BitLocker-protected disk volumes on the portable computers.
What should you do before you start encrypting the disk volumes with BitLocker?
A. Select the Turn on BitLocker backup to Active Directory option in Group Policy linked to the portable computers.
B. Run the cscript Get-TPMOwnerlnfo.vbs script on the client computers.
C. Run the manage-bde -on C: -RecoveryPassword command on the portable computers.
D. Run the Idifde -i -v -f BitLockerTPMSchemaExtension.ldf -c script on a domain controller.
Answer: C
Q208. - (Topic 1)
Which of the following will cause the Online Compatibility Check to fail during a Window 7 installation? Choose two.
A. 512MB of RAM
B. A display adapter with WDDM Support
C. A display adapter without WDDM Support but with SVIDEO
D. An 80 GB Hard Disk
Answer: A,C
Q209. - (Topic 4)
A company has a server running Windows Server 2008 R2, with Windows Deployment Services (WDS), the Microsoft Deployment Toolkit (MDT), and the Windows Automated Installation Kit (WAIK) set up. The company also has client computers running Windows 7 Enterprise.
You are preparing to capture an image of a Windows 7 client computer.
You need to ensure that the captured image is generic and does not contain the device drivers from the client computer.
What should you do?
A. use Sysprep with an answer file and set the PersistAllDeviceInstalls option in the answer file to True.
B. Run the Start /w ocsetup command.
C. Run the PEImg /Prep command.
D. Run the Dism command with the /Mount-Wimoption.
E. Use Sysprep with an answer file and set the UpdateInstalledDrivers option in the answer file to No.
F. Run the Dism command with the /Add-Driver option.
G. Use Sysprep with an answer file and set the UpdateInstalledDrivers option in the answer file to Yes.
H. Run the BCDEdit/delete command.
I. Run the ImageX command with the /Mount parameter.
J. Run the Dism command with the /Add-Package option.
K. Add a boot image and create a capture image in WDS.
L. Use Sysprep with an answer file and set the PersistAllDeviceInstalls option in the answer file to False.
M. Run the DiskPart command and the Attach command option.
Answer: L
Explanation:
Persisting Plug and Play Device Drivers During generalize You can persist device drivers when you run the Sysprep command with the /generalize option by specifying the PersistAllDeviceInstalls setting in the Microsoft-Windows-PnPSysprep component. During the specialize configuration pass, Plug and Play scans the computer for devices and installs device drivers for the detected devices. By default, these device drivers are removed from the system when you generalize the system. If you set PersistAllDeviceInstalls to true in an answer file, Sysprep will not remove the detected device drivers. For more information, see the Unattended WindowsSetup Reference (Unattend.chm). http://technet.microsoft.com/en-us/library/dd744512(WS.10).aspx
Q210. - (Topic 2)
You install an application named app1.exe on a computer
After the installation the computer becomes unresponsive.
You restart the computer and attempt to uninstall App1.exe. The uninstallation of App1.exe fails.
You need to restore the computer to its previous functional state. You must achieve the goal by using the minimum amount of administration.
What should you do?
A. From Recovery, restore a system restore point.
B. From the Previous Versions tab of App1.exe, click Restore button.
C. Start the computer, press F8 and then use the Last Known Good Configuration.
D. Create a system repair disc and then start the computer from the system repair disc.
Answer: A
Explanation:
If you install an application that causes your computer to become unstable, you should first attempt to uninstall the application. If this does not solve the problem, you can restore system files and settings by performing a system restore to restore the computer to its last system restore point. A system restore returns a computer system to a selected restore point. System restores do not alter user files. Note that a system restore is not the same as a System Image restore.
Windows 7 creates system restore points on a regular schedule and prior to events such as the installation of applications and drivers. A restore point contains information about registry settings and other system information. Windows 7 generates restore points automatically before implementing significant system changes. You can manually create restore points and restore a computer system to a selected restore point. If you install an application or driver that causes your computer to become unstable, you should first attempt to uninstall the application or roll back the driver. If this does not solve the problem, you can restore system files and settings by performing a system restore to restore the computer to its last system restore point. A system restore returns a computer system to a selected restore point. System restores do not alter user files. Note that a system restore is not the same as a System Image restore.