nerdexam

70-158 · Question #17

Your company network includes Forefront Identity Manager (FIM) 2010. Your company uses many custom attributes bound to resource types. One custom attribute is an integer type bound to multiple…

The correct answer is B. Set the minimum and maximum integer values on the validation page of the attribute binding configuration. In FIM 2010, integer validation ranges are configured at the attribute binding level, not the attribute definition level, because different resource types may require different valid ranges for the same shared attribute.

Submitted by suresh_in· Mar 4, 2026Configure the FIM portal

Question

Your company network includes Forefront Identity Manager (FIM) 2010. Your company uses many custom attributes bound to resource types. One custom attribute is an integer type bound to multiple resource types requiring validation of different ranges of values. The attribute must ensure that valid data is entered for the new integer type attribute. You need to extend the schema of the FIM Portal to validate integer data entry. What should you do?

Options

  • ASet the minimum and maximum integer values on the validation page of the new attribute.
  • BSet the minimum and maximum integer values on the validation page of the attribute binding configuration.
  • CSet String Pattern to match a regular expression of the Integer data type.
  • DSet String Pattern to match a regular expression of the Indexed String data type.
  • ERun iisreset.exe.

How the community answered

(53 responses)
  • A
    15% (8)
  • B
    70% (37)
  • C
    6% (3)
  • D
    8% (4)
  • E
    2% (1)

Why each option

In FIM 2010, integer validation ranges are configured at the attribute binding level, not the attribute definition level, because different resource types may require different valid ranges for the same shared attribute.

ASet the minimum and maximum integer values on the validation page of the new attribute.

Validation settings on the attribute definition page apply globally and cannot enforce different integer ranges for different resource types that share the same attribute, making it unsuitable for this scenario.

BSet the minimum and maximum integer values on the validation page of the attribute binding configuration.Correct

In FIM 2010, an attribute binding links a specific attribute to a specific resource type, and validation settings (such as minimum and maximum integer values) are configured on the binding's validation page rather than on the attribute itself. This design allows the same integer attribute bound to multiple resource types to enforce different range constraints per resource type, which is exactly the requirement described in the scenario.

CSet String Pattern to match a regular expression of the Integer data type.

String Pattern with a regular expression is used for String-type attributes to validate text patterns, not for Integer-type attributes, which have dedicated minimum/maximum value controls.

DSet String Pattern to match a regular expression of the Indexed String data type.

Indexed String is a different data type used for searchable string values, and applying a String Pattern regex to it would not validate integer ranges for an Integer-type attribute.

ERun iisreset.exe.

Running iisreset.exe simply restarts IIS services and has no effect on FIM Portal schema configuration or attribute validation settings.

Concept tested: FIM 2010 attribute binding integer validation configuration

Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/reference/mim2016-functions-reference

Topics

#Schema Extension#Attribute Binding#Data Validation#Custom Attributes

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice