nerdexam

70-158 · Question #24

Your company network includes Forefront Identity Manager (FIM) 2010. You implement several authoritative Management Agents (MAs) for employee metaverse objects. You need to ensure that whenever a…

The correct answer is B. Create an object deletion rule, and select the Delete metaverse object when connector from any. In FIM 2010, object deletion rules control when metaverse objects are deleted based on connector removal from authoritative Management Agents. The correct rule targets deletion when a connector from any authoritative MA is removed.

Submitted by haru.x· Mar 4, 2026Configuring the FIM Synchronization Service

Question

Your company network includes Forefront Identity Manager (FIM) 2010. You implement several authoritative Management Agents (MAs) for employee metaverse objects. You need to ensure that whenever a connector object is removed from an authoritative MA, the employee metaverse object that is connected is deleted. What should you do?

Options

  • ACreate an object deletion rule, and select the Delete metaverse object when last connector is
  • BCreate an object deletion rule, and select the Delete metaverse object when connector from any
  • CSelect the Make them disconnectors option in the deprovisioning rules.
  • DSelect the Determine with a rules extension option in the deprovisioning rules.

How the community answered

(28 responses)
  • A
    11% (3)
  • B
    82% (23)
  • C
    4% (1)
  • D
    4% (1)

Why each option

In FIM 2010, object deletion rules control when metaverse objects are deleted based on connector removal from authoritative Management Agents. The correct rule targets deletion when a connector from any authoritative MA is removed.

ACreate an object deletion rule, and select the Delete metaverse object when last connector is

The 'Delete metaverse object when last connector is removed' option only deletes the metaverse object when ALL connectors across ALL MAs are gone, not specifically when an authoritative MA's connector is removed, which does not satisfy the authoritative-source-driven deletion requirement.

BCreate an object deletion rule, and select the Delete metaverse object when connector from anyCorrect

Selecting 'Delete metaverse object when connector from any [authoritative MA]' ensures that removal of a connector object from any one of the defined authoritative MAs triggers deletion of the corresponding metaverse object. This is the correct approach because the company has multiple authoritative MAs for employee objects, and the business requirement is that removal from any authoritative source should drive metaverse object deletion, reflecting the authoritative nature of those sources.

CSelect the Make them disconnectors option in the deprovisioning rules.

The 'Make them disconnectors' deprovisioning option simply disconnects the connector space object from the metaverse without deleting the metaverse object itself, which does not fulfill the requirement to delete the employee metaverse object.

DSelect the Determine with a rules extension option in the deprovisioning rules.

The 'Determine with a rules extension' deprovisioning option delegates logic to custom code and does not represent a built-in declarative deletion rule targeting authoritative MAs, making it an indirect and unnecessarily complex approach for this requirement.

Concept tested: FIM 2010 metaverse object deletion rules for authoritative MAs

Source: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/forefront-2010/ms696137(v=vs.100)

Topics

#Management Agents#Object Deletion Rules#Metaverse Objects#Deprovisioning

Community Discussion

No community discussion yet for this question.

Full 70-158 Practice