Which describes the cause of the synchronization issue?

You administer a Forefront Identity Manager (FIM) 2010 server in your company network. FIM synchronizes
data between several data sources and the FIM Portal.
All data sources have an attribute named First Namemapped to the person:
firstName metaverse attribute. Attribute flow precedence for the person: firstName attribute is set toequal
precedence.
Synchronization rules are configured to import and export the attribute. The FIM Portal is the last contributor.
You change the value of the First Name attribute inthe FIM Portal and run full synchronization. You discover
that the value of First Name in the FIM Portal has been staged to the connector space but is not updated in the
metaverse.
Which describes the cause of the synchronization issue?

You administer a Forefront Identity Manager (FIM) 2010 server in your company network. FIM synchronizes
data between several data sources and the FIM Portal.
All data sources have an attribute named First Namemapped to the person:
firstName metaverse attribute. Attribute flow precedence for the person: firstName attribute is set toequal
precedence.
Synchronization rules are configured to import and export the attribute. The FIM Portal is the last contributor.
You change the value of the First Name attribute inthe FIM Portal and run full synchronization. You discover
that the value of First Name in the FIM Portal has been staged to the connector space but is not updated in the
metaverse.
Which describes the cause of the synchronization issue?

A.
The FIM Portal MA has missed run profiles.

B.
The FIM Portal MA requires a refresh of the schema.

C.
The FIM Portal MA has a missing entry for the ExpectedRulesList attribute.

D.
The FIM Portal MA is listed as the last row in the Configure Attribute Flow Precedence window for the
person:firstName attribute.



Leave a Reply 0

Your email address will not be published. Required fields are marked *