nerdexam

70-158 · Question #44

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…

The correct answer is C. The FIM Portal MA has a missing entry for the ExpectedRulesList attribute. The synchronization issue occurs because a missing entry in the FIM Portal MA's ExpectedRulesList attribute prevents the FIM Service MA from applying the correct inbound synchronization rule to flow the updated value from its connector space to the metaverse.

Submitted by satoshi_tk· Mar 4, 2026Configure synchronization

Question

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 Name mapped to the person: firstName metaverse attribute. Attribute flow precedence for the person: - firstName attribute is set to equal 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 in the 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?

Options

  • AThe FIM Portal MA has missed run profiles.
  • BThe FIM Portal MA requires a refresh of the schema.
  • CThe FIM Portal MA has a missing entry for the ExpectedRulesList attribute.
  • DThe FIM Portal MA is listed as the last row in the Configure Attribute Flow Precedence window for the

How the community answered

(39 responses)
  • A
    28% (11)
  • B
    15% (6)
  • C
    49% (19)
  • D
    8% (3)

Why each option

The synchronization issue occurs because a missing entry in the FIM Portal MA's ExpectedRulesList attribute prevents the FIM Service MA from applying the correct inbound synchronization rule to flow the updated value from its connector space to the metaverse.

AThe FIM Portal MA has missed run profiles.

If run profiles were missed, the change would likely not even be staged to the connector space, which contradicts the problem description.

BThe FIM Portal MA requires a refresh of the schema.

A schema refresh is typically required for new attributes or changes to attribute types, not for an existing attribute failing to flow values due to an internal configuration issue.

CThe FIM Portal MA has a missing entry for the ExpectedRulesList attribute.Correct

The ExpectedRulesList attribute on the FIM Service Management Agent (which represents the FIM Portal) is crucial for directing inbound attribute flow from the FIM Portal's connector space to the metaverse. If an entry for the 'First Name' attribute is missing from this list, the FIM Service MA will correctly stage the changed value in its connector space but will not know which synchronization rule to apply to push that change into the metaverse, resulting in the value not being updated there.

DThe FIM Portal MA is listed as the last row in the Configure Attribute Flow Precedence window for the

The question states 'equal precedence' and the FIM Portal is the 'last contributor,' meaning its changes should win in a conflict; the issue is not about precedence but the MA's inability to perform the import flow itself.

Concept tested: FIM Service MA ExpectedRulesList attribute function

Topics

#Synchronization Rules#Attribute Flow Precedence#Connector Space#ExpectedRulesList

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice