nerdexam

70-158 · Question #73

You install a Forefront Identity Management (FIM) 2010 server in your company network. The network includes Active Directory Domain Services (AD DS) and a Human Resources (HR) application. User…

The correct answer is A. From Synchronization Service Manager, use Metaverse Designer to configure the Department. To ensure the Department attribute from the HR application takes precedence over Active Directory Domain Services when imported into FIM, administrators must configure import attribute flow precedence within the FIM Synchronization Service Manager.

Submitted by asante_acc· Mar 4, 2026Configure the FIM Synchronization Service

Question

You install a Forefront Identity Management (FIM) 2010 server in your company network. The network includes Active Directory Domain Services (AD DS) and a Human Resources (HR) application. User account attributes are located in AD DS and in the HR application. You configure FIM to import a Department attribute from both the HR application data source and AD DS. You need to ensure that the value for the Department attribute from HR is always used where a value exists. What should you do?

Options

  • AFrom Synchronization Service Manager, use Metaverse Designer to configure the Department
  • BFrom Synchronization Service Manager, use Management Agents to modify join rules precedence
  • CFrom the FIM Portal, create a new outbound synchronization rule for the HR application data source.
  • DFrom the FIM Portal, create a new outbound synchronization rule for the AD DS data source.

How the community answered

(27 responses)
  • A
    78% (21)
  • B
    4% (1)
  • C
    4% (1)
  • D
    15% (4)

Why each option

To ensure the Department attribute from the HR application takes precedence over Active Directory Domain Services when imported into FIM, administrators must configure import attribute flow precedence within the FIM Synchronization Service Manager.

AFrom Synchronization Service Manager, use Metaverse Designer to configure the DepartmentCorrect

The FIM Synchronization Service Manager's Metaverse Designer is the tool used to define the metaverse schema and configure attribute flow rules, including setting precedence for attributes like 'Department' that are sourced from multiple connected data sources, ensuring the desired value (e.g., from HR) is prioritized during import.

BFrom Synchronization Service Manager, use Management Agents to modify join rules precedence

Modifying join rule precedence in Management Agents determines how objects are linked to the metaverse, not which attribute value takes precedence during an import from multiple sources once objects are joined.

CFrom the FIM Portal, create a new outbound synchronization rule for the HR application data source.

Outbound synchronization rules control data flow from the metaverse to a connected data source, not the precedence of incoming attribute values during the import process into the metaverse.

DFrom the FIM Portal, create a new outbound synchronization rule for the AD DS data source.

Similar to option C, outbound synchronization rules manage data export from the metaverse, not the prioritization of attribute values during the import process from connected data sources.

Concept tested: FIM/MIM Import Attribute Precedence in Metaverse Designer

Topics

#Attribute Precedence#Metaverse Designer#Synchronization Service Manager#FIM 2010

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice