Your company has three Active Directory domains in a single forest. You install a new Active
Directory enabled application. The application ads new user attributes to the Active Directory
schema.
You discover that the Active Directory replication traffic to the Global Catalogs has
increased.
You need to prevent the new attributes from being replicated to the Global Catalog.
You must achieve this goal without affecting application functionality.
What should you do?
A.
Change the replication interval for the DEFAULTIPSITELINK object to 9990.
B.
Change the cost for the DEFAULTIPSITELINK object to 9990.
C.
Make the new attributes in the Active Directory as defunct.
D.
Modify the properties in the Active Directory schema for the new attributes.
Explanation:
http://support.microsoft.com/kb/248717
How to Modify Attributes That Replicate to the Global Catalog
The Global Catalog (GC) contains a partial replica of every object in the enterprise. This
article discusses how to manipulate the attributes which make up the set values replicated to
the GC. Deciding which attributes will replicate (in addition to the default attributes) requires
careful planning with consideration for network traffic and necessary disk space.
Before describing how to set an attribute to replicate in the GC, it is important to note the
effects this has on network replication traffic.
After an attributeSchema object is created, marking an additional attribute to replicate to the
GC causes a full replication (also known as a “full sync”) of all objects to the GC as
described below. This behavior occurs on the versions of Windows 2000 listed in this article.
Every server has a full and write-able copy of its own domain. If that server is also a GC, the
remaining domains in the forest are held as read-only, partial copies. “Partial” means that
only a subset of the attributes is kept.
When an attribute is added to the GC, it is added to the partial copy subset (partial attribute
set). This causes the GC to perform a “full sync” of all the read-only copies again to
repopulate itself with only the partial attributes that it needs to hold. This full sync occurs
even if the attribute property isMemberOfPartialAttributeSet is set to “True.” Thus, it only
does a full sync on the read-only partial copy domains and not its own write-able domain, the
configuration directory partition or schema directory partition.
In order to modify the attributes that replicate to the Active Directory GC, you must modify
the schema. To modify the schema, an administrator must be made a member of the
“Schema Admins” group. In addition to being a member of this group, a registry key must be
set on the Schema master.