nerdexam

70-158 · Question #27

Your company network includes Forefront Identity Manager (FIM) 2010. You plan to configure a Management Agent (MA). Provisioning rules disconnect connector space objects from the corresponding…

The correct answer is C. Make the deprovisioning rule as an explicit disconnector. To prevent connector space objects disconnected by provisioning rules from being re-evaluated for join and projection on subsequent runs, the deprovisioning rule must be configured to create an explicit disconnector.

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

Question

Your company network includes Forefront Identity Manager (FIM) 2010. You plan to configure a Management Agent (MA). Provisioning rules disconnect connector space objects from the corresponding metaverse objects. You need to ensure that objects disconnected by using provisioning rules are not re-evaluated for join and projection rules on subsequent runs. What should you do?

Options

  • AUse a Rules extension.
  • BMake the deprovisioning rule as a disconnector.
  • CMake the deprovisioning rule as an explicit disconnector.
  • DStage a delete on the object for the next export run.

How the community answered

(41 responses)
  • A
    2% (1)
  • B
    15% (6)
  • C
    76% (31)
  • D
    7% (3)

Why each option

To prevent connector space objects disconnected by provisioning rules from being re-evaluated for join and projection on subsequent runs, the deprovisioning rule must be configured to create an explicit disconnector.

AUse a Rules extension.

Rules extensions provide custom logic but do not directly manage the re-evaluation behavior of disconnected objects in the specific way that an explicit disconnector does.

BMake the deprovisioning rule as a disconnector.

Simply making a deprovisioning rule create a 'disconnector' does not inherently prevent it from being re-evaluated for joining on subsequent runs; an explicit disconnector is required for that specific behavior.

CMake the deprovisioning rule as an explicit disconnector.Correct

An explicit disconnector is a specific state in FIM that prevents a connector space object from being considered for join or projection rules during subsequent synchronization runs, even if a join rule would otherwise match it. This ensures that objects intentionally disconnected by provisioning rules remain disconnected and are not inadvertently re-joined to a metaverse object.

DStage a delete on the object for the next export run.

Staging a delete removes the object from the connected data source on the next export, which is a different action than preventing a disconnected object from being re-evaluated for joining.

Concept tested: FIM Synchronization Rules: Explicit Disconnectors

Source: https://docs.microsoft.com/en-us/microsoft-identity-manager/synchronization-service/synchronization-rules-concepts-flow

Topics

#Management Agent#Explicit Disconnector#Deprovisioning Rules#Connector Space

Community Discussion

No community discussion yet for this question.

Full 70-158 Practice