nerdexam

70-158 · Question #97

You use Forefront Identity Manager (FIM) 2010 in your company network to provide an identity management solution between Active Directory Domain Services (AD DS) and enterprise HR applications. You…

The correct answer is C. Enable indexing for indexable object attributes. To improve the efficiency of searching for object attributes used in join rules within FIM 2010, enabling indexing for indexable object attributes is the correct solution. Indexing significantly speeds up database queries, which are fundamental to attribute searches.

Submitted by yuriko_h· Mar 4, 2026Configure the Metaverse

Question

You use Forefront Identity Manager (FIM) 2010 in your company network to provide an identity management solution between Active Directory Domain Services (AD DS) and enterprise HR applications. You create the required Management Agents (MAs). You need to make searching for object attributes of join rules more efficient. What should you do?

Options

  • AConfigure the attribute flow precedence to use equal precedence.
  • BConfigure the attribute flow precedence to use manual precedence.
  • CEnable indexing for indexable object attributes.
  • DEnable metaverse rules extension and select the Unload extension if the duration of a single operation

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    10% (3)
  • C
    83% (25)
  • D
    3% (1)

Why each option

To improve the efficiency of searching for object attributes used in join rules within FIM 2010, enabling indexing for indexable object attributes is the correct solution. Indexing significantly speeds up database queries, which are fundamental to attribute searches.

AConfigure the attribute flow precedence to use equal precedence.

Configuring attribute flow precedence, whether equal or manual, determines how attribute value conflicts are resolved during synchronization, not the efficiency of searching for attributes.

BConfigure the attribute flow precedence to use manual precedence.

Configuring attribute flow precedence, whether manual or equal, is related to resolving conflicts in attribute values during data flow, not to enhancing search performance for attributes.

CEnable indexing for indexable object attributes.Correct

Enabling indexing for object attributes within FIM's metaverse (which is backed by a SQL database) creates database indexes that drastically reduce the time required to search for specific attribute values. This optimization directly addresses the need to make searching for object attributes more efficient, especially when configuring or evaluating join rules.

DEnable metaverse rules extension and select the Unload extension if the duration of a single operation

Enabling metaverse rules extensions and managing their unload behavior is for optimizing the execution of custom business logic, not for improving the efficiency of searching for existing attributes.

Concept tested: FIM attribute search optimization via indexing

Topics

#Management Agents#Join Rules#Attribute Indexing#Metaverse Configuration

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice