Assessment 70-680 is one of appreciated together with demanded audit in IT discipline. To this specific apply audit 70-680 seriously isnt so simple though with your guidance you may apparent 70-680 in an earliest probability. The professionals who wants to turn out to be skillful of their industries and still have the desire to reach at the summit with capacity together with accomplishment they prefer several official certifications qualifications thats why. Process qualifications 70-680 are true accreditations in which warranty ones employers you happen to be professional, certified, together with continuous.
Q381. HOTSPOT - (Topic 4)
You have upgraded a Windows XP system to Windows 7. One of the applications is not showing menus when you launch it under Windows 7. How do you fix this issue?
Answer:
Q382. - (Topic 1)
You have a computer that runs Windows 7.
You need to prevent Internet Explorer from saving any data during a browsing session.
What should you do?
A. Disable the BranchCache service.
B. Modify the InPrivate Blocking list.
C. Open an InPrivate Browsing session.
D. Modify the security settings for the Internet zone.
Answer: C
Explanation:
InPrivate Mode consists of two technologies: InPrivate Filtering and InPrivate Browsing.
Both InPrivate Filtering and InPrivate Browsing are privacy technologies that restrict the amount of information available about a user's browsing session. InPrivate Browsing restricts what data is recorded by the browser, and InPrivate Filtering is used to restrict what information about a browsing session can be tracked by external third parties.
Q383. - (Topic 2)
You are preparing a custom Windows 7 image for deployment.
You need to install a third-party network interface card (NIC) driver in the image.
What should you do?
A. Run Pkgmgr.exe and specify the /ip parameter.
B. Run Dism.exe and specify the /add-driver parameter.
C. Create a new answer file by using Windows System Image Manager (Windows SIM). Run Pkgmgr.exe and specify the /n parameter.
D. Create a new answer file by using Windows System Image Manager (Windows SIM). Run Dism.exe and specify the /apply-unattend parameter.
Answer: B
Explanation:
Dism Deployment Image Servicing and Management (DISM) is a command-line tool used to service Windows. images offline before deployment. You can use it to install, uninstall, configure, and update Windows features, packages, drivers, and international settings. Subsets of the DISM servicing commands are also available for servicing a running operating system. Windows 7 introduces the DISM command-line tool. You can use DISM to service a Windows image or to prepare a Windows PE image. DISM replaces Package Manager (Pkgmgr.exe), PEimg, and Intlcfg in Windows Vista, and includes new features to improve the experience for offline servicing. You can use DISM to perform the following actions:
-Prepare a Windows PE image.- Enable or disable Windows features within an image.-Upgrade a Windows image to a different edition.- Add, remove, and enumerate packages.-Add, remove, and enumerate drivers.- Apply changes based on the offline servicing section of an unattended answer file.- Configure international settings.- Implement powerful logging features.- Service operating systems such as Windows Vista with SP1 and Windows Server 2008.- Service a 32-bit image from a 64-bit host and service a 64-bit image from a 32-bit host.- Service all platforms (32-bit, 64-bit, and Itanium).- Use existing Package Manager scripts.
Q384. - (Topic 2)
You have a Windows 7 Windows image (WIM) that is mounted.
You need to view the list of third-party drivers installed in the image.
What should you do?
A. Run Dism.exe and specify /get-drivers parameter.
B. Run Driverquery.exe and specify the /si parameter.
C. From Device Manager, view all hidden devices.
D. From Windows Explorer, open the \Windows\System32\Drivers folder from the mount folder.
Answer: A
Explanation:
DismDeployment Image Servicing and Management (DISM) is a command-line tool used to service Windows. images offline before deployment. You can use it to install, uninstall, configure, and update Windows features, packages, drivers, and international settings. Subsets of the DISM servicing commands are also available for servicing a running operating system. Windows 7 introduces the DISM command-line tool. You can use DISM to service a Windows image or to prepare a Windows PE image. DISM replaces Package Manager (Pkgmgr.exe), PEimg, and Intlcfg in Windows Vista, and includes new features to improve the experience for offline servicing. You can use DISM to perform the following actions: -Prepare a Windows PE image.
-Enable or disable Windows features within an image.
-Upgrade a Windows image to a different edition.
-Add, remove, and enumerate packages.
-Add, remove, and enumerate drivers.
-Apply changes based on the offline servicing section of an unattended answer file.
-Configure international settings.
-Implement powerful logging features.
-Service operating systems such as Windows Vista with SP1 and Windows Server 2008.
-Service a 32-bit image from a 64-bit host and service a 64-bit image from a 32-bit host.
-Service all platforms (32-bit, 64-bit, and Itanium).
-Use existing Package Manager scripts.
NOT DriverqueryEnables an administrator to display a list of installed device drivers and their properties. If used without parameters, driverquery runs on the local computer. (Could not see documention of images, only computers, therefore assumed this command does not support images) /si : Displays digital signature information for both signed and unsigned device drivers.
Q385. - (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.
Q386. HOTSPOT - (Topic 4)
A company's security policy prohibits employees from running any software from Fabrikam on computers running Windows 7 Enterprise. The applications are digitally signed by the publisher.
You need to configure a single deny rule in AppLocker by applying a condition to restrict all of the applications from running, without affecting other programs.
You have selected one of Fabrikam's applications as a reference.
Which property should you choose? (To answer, select the appropriate setting or settings in the work area.)
Answer:
Q387. - (Topic 5)
You use a portable computer that has Windows 7 Enterprise SP1 installed. A conference room at your company has a network projector installed on a server within the company network.
You need to connect to the projector from your computer. What should you do?
A. From Device Manager, click Add legacy hardware.
B. From Accessories, click Connect to a Network Projector.
C. Run the Displayswitch.exe command and select Projector only.
D. From Display, click Connect to a projector.
Answer: C
Q388. - (Topic 2)
A remote user has a computer that runs Windows 7. The user reports that he receives several error messages while using an application. You do not have remote access to the user's computer.
You need to tell the user how to create screenshots of the actions he performs on the computer.
The solution must track the mouse actions that the user performs. What should you instruct the user to do?
A. Press ALT+PrintScreen
B. Run Psr.exe and then click Start Record
C. From Mouse Properties, select Display pointer trails
D. Run Snippingtool.exe, click New, and then click Window Snip
Answer: B
Explanation:
How do I use Problem Steps Recorder?You can use Problem Steps Recorder to automatically capture the steps you take on a computer, including a text description of where you clicked and a picture of the screen during each click (called a screen shot). Once you capture these steps, you can save them to a file that can be used by a support professional or someone else helping you with a computer problem.NotesWhen you record steps on your computer, anything you type will not be recorded. If what you type is an important part of recreating the problem you're trying to solve, use the comment feature described below to highlight where the problem is occurring.
Q389. - (Topic 4)
Your company office network includes a file server that has Windows Server 2008 R2 installed and client computers that have Windows 7 Enterprise installed. The computers are members of an Active Directory domain. The file server has the BrachCache features installed.
All sales user in the office must download a daily updated 5-GB file that is stored on a file server located in a remote office.
You configure the client computers to run BranchCache in Distributed Host mode. You discover that all users still access the file directly from the file server.
You need to reduce the utilization of a WAN link between the offices because of downloading the file to the client computers.
What should you do?
A. Run the Netsh branchcache set service mode=HOSTEDSERVER client authentication=NONE command
B. Configure firewall exception rules for multicast traffic, inbound and outbound traffic for local UDP port 3702, and inbound and outbound traffic for local TCP port 80.
C. Create a Group Policy that sets Hash Publication for BranchCache as disabled.
D. Run the netsh branchcache set service mode=DISTRIBUTED command.
E. Create a Group Policy object and configure the Set percentage of disk space used for client computer cache option.
F. Check permisions.
G. Run the netsh branchcache set service mode=HOSTEDCLIENT command.
H. Create a Group Policy object and enable the Set BranchCache Hosted Cache mode policy.
I. Configure firewall exception rules for inbound and outbound traffic for local TCP port 80 and for inbound and outbound traffic for local TCP port 8443.
Answer: E
Explanation:
Original wording: You configure the client computers to run BranchCache in 'Distributed Host Mode'. Changed to 'Distributed Cache mode".
Q390. - (Topic 5)
Your company has an Active Directory domain and several branch locations. A Group Policy Object (GPO) exists for each branch office and for the main office. Computer accounts for computers used by sales employees are located in the Sales-Computers organizational unit (OU).
The sales employees use portable computers that have Windows 7 Enterprise installed.
Employees report that the documents that must be printed are sent to printers in their home office when they travel to the different branch offices.
You need to ensure that documents are printed automatically to the correct printer when the sales employees travel to a branch office.
What should you do first?
A. From Devices and Printers, select Change my default printer when I change networks.
B. Publish all printers to Active Directory.
C. Link the GPO of the branch offices to the Sales-Computers OU.
D. From Print Management, select the branch office printer, and select set as default from the Printer menu.
E. From the Network and Sharing Center, select Advanced sharing settings, and then select Turn on file and printer sharing.
Answer: A