nerdexam

70-158 · Question #91

You administer a Forefront Identity Management (FIM) 2010 server in your company network. You discover that several objects do not synchronize between the FIM Service database and Active Directory…

The correct answer is B. Outbound synchronization. The data is successfully in the FIM Service Management Agent's connector space and the metaverse, but it fails to appear in the AD DS Management Agent's connector space, indicating a failure during outbound synchronization from the metaverse to AD DS.

Submitted by packet_pusher· Mar 4, 2026Configure Data Synchronization

Question

You administer a Forefront Identity Management (FIM) 2010 server in your company network. You discover that several objects do not synchronize between the FIM Service database and Active Directory Domain Services (AD DS). The required identity data has the following features: - It appears in the connector space of the FIM management process. - It appears in the metaverse. It does not appear in the connector space of the AD DS Management Agent. In which phase does synchronization fail?

Options

  • AInbound synchronization
  • BOutbound synchronization
  • CImport
  • DExport

How the community answered

(20 responses)
  • A
    5% (1)
  • B
    70% (14)
  • C
    10% (2)
  • D
    15% (3)

Why each option

The data is successfully in the FIM Service Management Agent's connector space and the metaverse, but it fails to appear in the AD DS Management Agent's connector space, indicating a failure during outbound synchronization from the metaverse to AD DS.

AInbound synchronization

Inbound synchronization is the process of bringing data into the metaverse from a connected data source; however, the data is already in the metaverse, so this is not the failure point for data destined for AD DS.

BOutbound synchronizationCorrect

Outbound synchronization involves provisioning data from the metaverse to a connector space for a target connected system. Since the data is in the metaverse but does not appear in the AD DS Management Agent's connector space, the failure occurs in the outbound synchronization process from the metaverse to the AD DS connector space, preventing the data from reaching AD DS.

CImport

Import is the process of bringing data from a connected system into its respective connector space; the problem describes data failing to reach the AD DS Management Agent's connector space from the metaverse, not a failure to import from AD DS.

DExport

Export is the process of writing data from a management agent's connector space to the connected data source; the data fails to reach the AD DS Management Agent's connector space, meaning the export phase cannot even begin.

Concept tested: FIM synchronization flow and phases

Topics

#Outbound Synchronization#Metaverse#Connector Space#Troubleshooting Synchronization

Community Discussion

No community discussion yet for this question.

Full 70-158 Practice