Windows 7 Chapter 5 Managing Applications

Front 1

Which compatibility option should you enable for a program that needs administrative privileges but that triggers a User Account Control prompt?

Back 1

You should enable the Run This Program As An Administrator option because this allows the application to run using elevated privileges. The user is presented with a User Account Control prompt prior to elevated privileges being granted.

Front 2

Application Compatibility Toolkit (ACT)

Back 2

The Application Compatibility Toolkit (ACT) is a collection of tools that allows you to resolve application compatibility issues.

Front 3

The ACT contains the following components:

Back 3

Application Compatibility Manager
Compatibility Administrator
Internet Explorer Compatibility Test Tool
Setup Analysis Tool
Standard User Analyzer

Front 4

Application Compatibility Manager

Back 4

allows you to configure, collect, and analyze compatibility data so you can resolve issues prior to deploying Windows 7

Front 5

Compatibility Administrator

Back 5

allows you to resolve a large number of application compatibility issues that might occur when you attempt to deploy an existing application on Windows 7.

Front 6

compatibility fix

Back 6

A compatibility fix, also known as a shim, is a piece of software that intercepts application programming interface (API) calls from applications, modifying
them so that Windows 7 provides a similar response as a previous version of Windows did

Front 7

compatibility mode

Back 7

A compatibility mode is a group of compatibility fixes.

Front 8

Internet Explorer Compatibility Test Tool

Back 8

allows you to test existing
Web sites to determine if they have compatibility problems that adversely influence how
they will display on Internet Explorer 8

Front 9

Setup Analysis Tool

Back 9

The Setup Analysis Tool monitors the actions taken by application installers and can detect the following compatibility issues:
Installation of kernel mode drivers
Installation of 16-bit components
Installation of Graphical Identification and Authentication dynamic-link libraries (DLLs)
Modification of files or registry keys that are guarded by Windows Resource Protection
(WRP)

Front 10

Standard User Analyzer

Back 10

allows you to test applications to determine if they might have compatibility issues caused by User Account Control

Front 11

Application Compatibility Diagnostics Policies

Back 11

Notify Blocked Drivers
Detect Application Failures Caused By Deprecated COM Objects
Detect Application Failures Caused By Deprecated Windows DLLs
Detect Application Install Failures
Detect Application Installers That Need To Be Run As Administrator
Detect Applications Unable To Launch Installers Under UAC

Front 12

An application that functions well on a computer that has Windows XP SP3 installed, but
which does not run normally on Windows 7. How do you make it work?

Back 12

might run without a problem if you configure it to use the Windows XP SP3 compatibility mode

Front 13

There are two different technologies that you can use with computers running Windows 7 to restrict the execution of applications

Back 13

AppLocker and Software Restriction Policies

Front 14

Software Restriction Policies are applied in a particular order

Back 14

the more explicit rule
types overriding more general rule types. The order of precedence from most specific (hash) to least specific (default)

1. Hash rules
2. Certificate rules
3. Path rules
4. Zone rules
5. Default rules

If two conflicting rules with different security levels are established for the same program, the most specific rule takes precedence.

Front 15

In environments that use both Software Restriction Policies and AppLocker

Back 15

AppLocker policies take precedence

Front 16

Default Rules

Back 16

Disallowed
Basic User
Unrestricted

Front 17

Enforcement Properties policy

Back 17

You can use the Enforcement Properties policy, to specify whether Software Restriction Policies to all software files except libraries, such as DLLs, or all software files, including DLLs

Front 18

Designated File Types

Back 18

allows you to determine which file extensions should be recognized as executable files and hence fall under the influence of Software Restriction Policies.

Front 19

Path rules

Back 19

15, allow you to specify a file, folder, or registry key as the target of a Software Restriction Policy.

Front 20

Hash Rules

Back 20

work through the generation of a digital fingerprint that
identifies a file based on its binary characteristics.

Front 21

Certificate Rules

Back 21

Certificate rules use a code-signed software publisher’s certificate to identify applications signed by that publisher

Front 22

Network Zone Rule

Back 22

Zone rules function by differentiating installer packages based on the site
from which they were downloaded

Front 23

What is the advantage of using a hash rule over a path rule?

Back 23

Hash rules are like digital fingerprints that identify a unique file. A path rule only
works based on a file name and path, which means that malware can be inserted
into locations covered by path rules and executed.

Front 24

AppLocker policies

Back 24

similar to Software Restriction
Policies, though AppLocker policies have several advantages, such as the ability to be applied to specific user or group accounts and the ability to apply to all future versions of
a product

Front 25

AppLocker policies are sometimes called

Back 25

application control policies.

Front 26

when you enable AppLocker

Back 26

when you enable AppLocker, you cannot execute any application, script, or installer that does not fall under an Allow rule

Front 27

The fallback Block rule

Back 27

just restricts the execution of any application that has not been allowed specifically

Front 28

Executable Rules

Back 28

Executable rules apply to files that have .exe and .com file extensions. AppLocker policies are primarily about executable files, and it is likely that the majority of the AppLocker policies that you work with in your organizational environment will involve executable rules.

Front 29

Windows Installer Rules

Back 29

Windows Installer rules cover files with .msi and .msp file extensions

Front 30

Script Rules

Back 30

Script rules cover files with the .ps1, .bat, .cmd, .vbs, and .js file extensions

Front 31

DLL Rules

Back 31

DLL rules cover files known as libraries, which have the .dll and .ocx file extensions.

Front 32

Publisher Rules

Back 32

Publisher rules in AppLocker work on the basis of the code-signing certificate used by the
file’s publisher. Unlike a Software Restriction Policy certificate rule, it is not necessary to obtain a certificate to use a publisher rule because the details of the digital signature are extracted from a reference application file.

Front 33

Hash Rules

Back 33

Hash rules in AppLocker function in the same basic way that they do in Software Restriction Policies. Hash rules allow you to identify a specific binary file that is not digitally signed by
creating a digital fingerprint of that file

Front 34

Path Rules

Back 34

AppLocker path rules work in a similar way to Software Restriction Policy path rules that you learned about earlier in this lesson. Path rules let you specify a folder, in which case the path rule applies to the entire contents of the folder, including subfolders, and the path to a specific file.

Path rules are only as effective as the file and folder
permissions applied on the computer.