nerdexam

70-158 · Question #74

You install a Forefront Identity Management (FIM) 2010 server in your company network. The network has a Human Resources (HR) application that contains the following two employee attributes: First…

The correct answer is A. Create a synchronization rule. Add an Inbound attribute flow. To calculate and populate the emailAddress attribute in the metaverse by concatenating First Name and Last Name from an HR application, you must define an inbound attribute flow within a synchronization rule.

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

Question

You install a Forefront Identity Management (FIM) 2010 server in your company network. The network has a Human Resources (HR) application that contains the following two employee attributes: First Name Last Name You create a Management Agent (MA) by using the HR application as a data source. You need to calculate the emailAddress attribute of the metaverse Person object. You also need to ensure that the attribute concatenates the values of the First Name and the Last Name attributes. What should you do?

Options

  • ACreate a synchronization rule. Add an Inbound attribute flow.
  • BCreate a synchronization rule. Add an Outbound attribute flow.
  • CEdit the Management Agent properties. Configure an Import attribute flow based on the Direct
  • DEdit the Management Agent properties. Configure an Export attribute flow based on the Advanced

How the community answered

(41 responses)
  • A
    83% (34)
  • B
    5% (2)
  • C
    2% (1)
  • D
    10% (4)

Why each option

To calculate and populate the `emailAddress` attribute in the metaverse by concatenating `First Name` and `Last Name` from an HR application, you must define an inbound attribute flow within a synchronization rule.

ACreate a synchronization rule. Add an Inbound attribute flow.Correct

The requirement is to calculate a metaverse attribute (`emailAddress`) using data from a connected HR application. An inbound attribute flow specifies how data moves from a connected data source into the metaverse, and synchronization rules are the primary mechanism for defining these flows and complex transformations, such as concatenating multiple source attributes.

BCreate a synchronization rule. Add an Outbound attribute flow.

An outbound attribute flow is used to push data from the metaverse to a connected data source, which is the opposite direction needed to populate a metaverse attribute.

CEdit the Management Agent properties. Configure an Import attribute flow based on the Direct

While Management Agents handle imports, a 'Direct' import attribute flow typically implies a simple one-to-one mapping without complex transformations like concatenating multiple source attributes, which is handled by synchronization rules.

DEdit the Management Agent properties. Configure an Export attribute flow based on the Advanced

An export attribute flow, synonymous with outbound flow, pushes data from the metaverse to a connected system, not into the metaverse.

Concept tested: FIM 2010 Inbound Synchronization Rule Configuration

Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/reference/attributes-flow-reference

Topics

#Synchronization Rules#Inbound Attribute Flow#Management Agents#Metaverse

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice