nerdexam

70-158 · Question #96

You use Forefront Identity Manager (FIM) 2010 in your company network. The network has an HR system that contains a record of all employees. You create the FIM Management Agent (MA) by using default…

The correct answer is A. On the FIM Service MA, map the connector space Person object to the metaverse Person object. B. Add an export attribute flow on the FIM Service MA for the DetectedRulesList attribute. D. Add an import attribute flow on the FIM Service MA for the ExpectedRulesList attribute. In FIM 2010, provisioning and projection require proper object type mapping and correct attribute flows for synchronization rules. The ExpectedRulesList and DetectedRulesList attributes are critical for rules-based provisioning to function correctly.

Submitted by the_admin· Mar 4, 2026Configure Synchronization

Question

You use Forefront Identity Manager (FIM) 2010 in your company network. The network has an HR system that contains a record of all employees. You create the FIM Management Agent (MA) by using default settings. The sAMAccountName has been marked as "Use for Existence test." You confirm that the user accounts in the portal are correctly marked for provisioning. You run a Delta Import (Stage Only) profile on the FIM MA and confirm that the employee accounts arrive in the connector space. However, when you run a synchronization profile, provisioning and projection do not occur. You need to ensure that employee user objects are provisioned to Active Directory. What should you do? (Choose all that apply.)

Options

  • AOn the FIM Service MA, map the connector space Person object to the metaverse Person object.
  • BAdd an export attribute flow on the FIM Service MA for the DetectedRulesList attribute.
  • CAdd an import attribute flow on the FIM Service MA for the DetectedRulesList attribute.
  • DAdd an import attribute flow on the FIM Service MA for the ExpectedRulesList attribute.
  • EAdd an export attribute flow on the FIM Service MA for the ExpectedRulesList attribute.

How the community answered

(36 responses)
  • A
    69% (25)
  • C
    19% (7)
  • E
    11% (4)

Why each option

In FIM 2010, provisioning and projection require proper object type mapping and correct attribute flows for synchronization rules. The ExpectedRulesList and DetectedRulesList attributes are critical for rules-based provisioning to function correctly.

AOn the FIM Service MA, map the connector space Person object to the metaverse Person object.Correct

The FIM Service MA must have an object type mapping that joins or projects the connector space Person object to the metaverse Person object; without this mapping, synchronization cannot project the object into the metaverse, which is a prerequisite for provisioning to occur in any connected directory.

BAdd an export attribute flow on the FIM Service MA for the DetectedRulesList attribute.Correct

The DetectedRulesList attribute must be exported from the metaverse back to the FIM Service connector space so that FIM can write back which synchronization rules have been applied, completing the rules-based provisioning feedback loop and allowing the portal to track rule application state.

CAdd an import attribute flow on the FIM Service MA for the DetectedRulesList attribute.

An import attribute flow for DetectedRulesList is incorrect because DetectedRulesList is a metaverse-generated attribute that flows outward (export) to the FIM Service connector space, not inward from it; importing it would reverse the intended data flow direction.

DAdd an import attribute flow on the FIM Service MA for the ExpectedRulesList attribute.Correct

The ExpectedRulesList attribute must be imported from the FIM Service connector space into the metaverse so that FIM Synchronization Engine can read which synchronization rules are expected to apply to the object, triggering the correct provisioning and attribute flow rules toward Active Directory.

EAdd an export attribute flow on the FIM Service MA for the ExpectedRulesList attribute.

An export attribute flow for ExpectedRulesList is incorrect because ExpectedRulesList originates in the FIM portal/service and must be imported into the metaverse, not exported from the metaverse back to the connector space, as it represents the portal's declared intent rather than a metaverse-derived value.

Concept tested: FIM MA provisioning with synchronization rule attribute flows

Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/understand-fim-synchronization-service-rules-based-management

Topics

#FIM Service MA#Provisioning#Attribute Flow#Metaverse Mapping

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice