nerdexam

70-158 · Question #69

You administer a Forefront Identity Manager (FIM) 2010 server in your company network. The FIM server synchronizes user resources between an Active Directory Domain Services (AD DS) domain and a…

The correct answer is B. Create an outbound synchronization rule. C. On the Active Directory outbound sync rule, add the outbound attribute flow rule Source: Name; E. Select the Use as Existence Test check box for the displayName attribute. To verify successful AD account creation, configure an outbound synchronization rule to provision accounts from FIM to AD DS, map the HR 'Name' attribute to the AD 'displayName', and designate 'displayName' as an existence test.

Submitted by devops_kid· Mar 4, 2026Configure Identity Data Synchronization

Question

You administer a Forefront Identity Manager (FIM) 2010 server in your company network. The FIM server synchronizes user resources between an Active Directory Domain Services (AD DS) domain and a Human Resources (HR) application. HR data has been projected to the metaverse and accounts are provisioned to the domain immediately after user records are created in the HR application. The displayName attribute of the domain user matches the Name attribute of the HR application_ s user record. You need to find out whether a user account has been successfully created in the domain after you add a new record in the HR application. What should you do? (Each correct answer presents part of the solution. Choose all that apply.)

Options

  • ACreate an inbound synchronization rule.
  • BCreate an outbound synchronization rule.
  • COn the Active Directory outbound sync rule, add the outbound attribute flow rule Source: Name;
  • DOn the Active Directory outbound sync rule, add the outbound attribute flow rule Source: Name;
  • ESelect the Use as Existence Test check box for the displayName attribute.

How the community answered

(64 responses)
  • A
    23% (15)
  • B
    42% (27)
  • D
    34% (22)

Why each option

To verify successful AD account creation, configure an outbound synchronization rule to provision accounts from FIM to AD DS, map the HR 'Name' attribute to the AD 'displayName', and designate 'displayName' as an existence test.

ACreate an inbound synchronization rule.

An inbound synchronization rule defines flow from a connected data source *to* the FIM metaverse, but the problem focuses on provisioning *from* the metaverse *to* AD DS and verifying creation *in* AD.

BCreate an outbound synchronization rule.Correct

An outbound synchronization rule is necessary to define how user objects and their attributes are provisioned and flow from the FIM metaverse to the Active Directory domain.

COn the Active Directory outbound sync rule, add the outbound attribute flow rule Source: Name;Correct

This attribute flow defines that the 'Name' attribute (from HR, projected to the metaverse) will be used as the source to populate an attribute in Active Directory (implicitly, 'displayName', as stated in the question), which is crucial for account creation.

DOn the Active Directory outbound sync rule, add the outbound attribute flow rule Source: Name;

This choice is a duplicate of option C and does not represent an additional, distinct step in the solution.

ESelect the Use as Existence Test check box for the displayName attribute.Correct

Marking 'displayName' as an existence test enables FIM to check if an object with that 'displayName' already exists in Active Directory, allowing it to confirm if the provisioning process successfully created or identified the target account.

Concept tested: FIM 2010 Outbound Provisioning and Existence Tests

Topics

#Synchronization Rules#Attribute Flow#Existence Test#Outbound Sync

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice