nerdexam

70-158 · Question #47

You deploy Forefront Identity Manager (FIM) 2010 in your company network. You create and configure management agents (MAs) named FIM MA, HR MA, and AD MA . You import user accounts from the HR MA…

The correct answer is D. The Management Policy Rule is not connected to a set that has imported user accounts. The expectedRuleList attribute is empty because the FIM Management Policy Rule (MPR) responsible for provisioning is not targeting the set containing the imported user accounts, preventing the necessary outbound synchronization rules from being applied.

Submitted by ashley.k· Mar 4, 2026Configure FIM Policy and Provisioning

Question

You deploy Forefront Identity Manager (FIM) 2010 in your company network. You create and configure management agents (MAs) named FIM MA, HR MA, and AD MA . You import user accounts from the HR MA data source as metaverse person objects and provision them into the FIM Portal. However, you are unable to provision the user accounts into the AD MA data source. The expectedRuleList attribute is empty for all imported person objects. What is the cause of the issue?

Options

  • AMissing run profiles for the AD MA.
  • BIncorrect join rules configuration of the HR MA.
  • CIncorrect outbound attribute flow in the outbound synchronization rule.
  • DThe Management Policy Rule is not connected to a set that has imported user accounts.

How the community answered

(15 responses)
  • A
    13% (2)
  • B
    7% (1)
  • C
    20% (3)
  • D
    60% (9)

Why each option

The `expectedRuleList` attribute is empty because the FIM Management Policy Rule (MPR) responsible for provisioning is not targeting the set containing the imported user accounts, preventing the necessary outbound synchronization rules from being applied.

AMissing run profiles for the AD MA.

Missing run profiles would prevent the AD MA from executing, but the `expectedRuleList` being empty indicates an issue with rules *applying* to objects, not the MA's ability to run.

BIncorrect join rules configuration of the HR MA.

The question states users are successfully imported as metaverse objects, indicating the HR MA's join rules worked correctly to bring data into the metaverse, which is not the source of the provisioning issue.

CIncorrect outbound attribute flow in the outbound synchronization rule.

Incorrect outbound attribute flow would result in provisioning failures or incorrect data if the rule applied, but an empty `expectedRuleList` means the provisioning rule itself isn't being identified or applied to the object.

DThe Management Policy Rule is not connected to a set that has imported user accounts.Correct

In FIM, outbound provisioning to external systems like AD is driven by Management Policy Rules (MPRs) that apply to specific sets of objects. If the imported user accounts are not members of the set targeted by the MPR responsible for AD provisioning, the corresponding outbound synchronization rules will not be triggered, resulting in an empty `expectedRuleList` for those objects.

Concept tested: FIM Management Policy Rules and Set-Based Provisioning

Topics

#Declarative Provisioning#Management Policy Rules#Synchronization Rules#FIM Metaverse

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice