DRAG DROP
Your company has a private cloud that is managed by using a System Center 2012 infrastructure.
The private cloud contains 200 servers that run Windows Server 2008 R2. All of the servers are
managed by Operations Manager.
The private cloud contains an application named App1 that is deployed on-demand to several
servers. The servers that run the application are identified by a registry value set during the
application’s installation.
You create a monitor that targets all of the servers.
You need to modify the monitor to only affect the servers that have the application installed.
Which three actions should you perform in sequence? (To answer, move the appropriate actions
from the list of actions to the answer area and arrange them in the correct order.)
Answer: 
Explanation:
http://technet.microsoft.com/en-us/library/hh212869.aspx
In Operations Manager 2007, you can create attributes to define a commonality within a group of
objects that you want to monitor.
After you create an attribute, you can create a group whose members are only objects that have the
commonality described in your attribute.
For example, if you want to monitor a set of servers that all have a common registry value, you
create an attribute based on that registry value.
To find the servers that have that registry value, you create a group that has a dynamic inclusion rule
for only those servers that have the newly created attribute and target the group only to the server
object type.
Operations Manager then checks the registry of each server to see whether that registry value
exists.
If it does, that server is added as a member of the group.
When you create an attribute, you must select an object type as a target for it.
Operations Manager adds the new attribute to the existing list of attributes for that object type.
If the target you select is from a sealed management pack, the object type also is sealed and the new
attribute cannot be added.
Instead, Operations Manager creates a new object type to which it adds the new attribute.
By default, this new object type is named after the original object type with _Extended appended to
the original name.
This new object type contains all the attributes of the original object type, in addition to the
attribute you are creating.
You can view existing attributes in the Monitoring area of the Operations console.
If the attributes are defined within a sealed management pack, you can view the properties of the
attribute but you cannot change them.
The properties of an attribute include information about where the attribute information is stored,
such as the registry or through WMI.
You can create a new attribute for any monitored object, and you can change most of the properties
of an attribute that you create.
However, the Attribute Type property, which identifies the source of the attribute information such
as the registry, cannot be changed after an attribute is created.http://systemscenter.ru/opsmgr2007.en/html/26d205e5- a26b-416e-93ae-9f33fe156311.htm