You administer a Forefront Identity Manager (FIM) 2010 server. The FIM server has management agents (MAs) connected to the following data sources: Active Directory Domain Services (AD DS) Active…

A connector filter on the AD DS MA would prevent AD DS objects from joining or projecting into the metaverse, which would disrupt the required unchanged attribute flow between SQL Server and AD DS.

A connector filter on the SQL Server MA would prevent the SQL record from connecting to the metaverse entirely, rather than triggering a targeted deletion of only the AD LDS object when the record is inactive.

Configuring deprovisioning for the AD LDS MA defines what happens to the connected AD LDS object when it is disconnected from the metaverse - setting it to 'delete object in the external data source' ensures the AD LDS user object is physically deleted when the SQL record becomes inactive and triggers disconnection.

Configuring deprovisioning in the AD LDS triple (the metaverse-to-connector space relationship) controls how the system handles the connector space object when the metaverse object loses its projection, ensuring the deletion workflow is properly scoped to AD LDS without impacting the AD DS connector or its attribute flows.

Configuring deprovisioning for the SQL Server MA controls what happens to SQL Server objects when disconnected, not what happens to AD LDS objects, so this does not address the requirement to delete the AD LDS user.

An object deletion rule for the Person object type would affect all MAs connected to that metaverse object type globally, potentially disrupting the AD DS attribute flow rather than isolating the deletion action to AD LDS only.