nerdexam

70-158 · Question #29

Your company network includes Forefront Identity Manager (FIM) 2010. You are configuring the FIM Management Agent (MA) attribute flows for first-time synchronization between the FIM Service and FIM…

The correct answer is C. Add the expectedRuleEntry metaverse object type. D. Add the detectedRuleEntry metaverse object type. When configuring FIM MA attribute flows for person objects, you must add the expectedRuleEntry and detectedRuleEntry metaverse object types to ensure proper synchronization rule processing between the FIM Service and FIM Synchronization Service.

Submitted by fernanda_arg· Mar 4, 2026Configuring the FIM Synchronization Service

Question

Your company network includes Forefront Identity Manager (FIM) 2010. You are configuring the FIM Management Agent (MA) attribute flows for first-time synchronization between the FIM Service and FIM Synchronization Service. You map configure object mapping for the person object type. You need to ensure that proper attribute flows are created for the Person object on the FIM MA . What should you do? (Choose all that apply.)

Options

  • AAdd the FIM object IDs.
  • BAdd the metaverse object IDs.
  • CAdd the expectedRuleEntry metaverse object type.
  • DAdd the detectedRuleEntry metaverse object type.

How the community answered

(40 responses)
  • A
    15% (6)
  • B
    8% (3)
  • C
    78% (31)

Why each option

When configuring FIM MA attribute flows for person objects, you must add the expectedRuleEntry and detectedRuleEntry metaverse object types to ensure proper synchronization rule processing between the FIM Service and FIM Synchronization Service.

AAdd the FIM object IDs.

FIM object IDs are internal identifiers for objects within the FIM Service database and are not configurable attribute flow mappings required for proper MA synchronization rule processing on the person object type.

BAdd the metaverse object IDs.

Metaverse object IDs are system-generated internal identifiers assigned by the FIM Synchronization Service and cannot be manually added as attribute flow configurations to establish proper synchronization between services.

CAdd the expectedRuleEntry metaverse object type.Correct

The expectedRuleEntry metaverse object type is required because it represents synchronization rules that are expected to be applied to an object, enabling the FIM MA to correctly project and flow attributes according to defined sync rules during initial synchronization.

DAdd the detectedRuleEntry metaverse object type.Correct

The detectedRuleEntry metaverse object type is required because it captures the synchronization rules that have actually been detected and applied to a connector space object, allowing the FIM Service and Synchronization Service to reconcile rule application state during attribute flow configuration.

Concept tested: FIM MA attribute flow configuration for person objects

Source: https://learn.microsoft.com/en-us/previous-versions/mim/ff400261(v=ws.10)

Topics

#FIM Management Agent#Attribute Flows#Object Mapping#Synchronization Rules

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice