70-158 Question #96: Real Exam Question with Answer & Explanation

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.

Explanation

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.

Common mistakes.

• C. 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.
• E. 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

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

No community discussion yet for this question.