nerdexam

70-158 · Question #3

Your company network includes Forefront Identity Manager (FIM) 2010. You configure the FIM Portal to use detailed error pages. A backup of FIM is performed daily. After a restore of the FIM Service…

The correct answer is A. Include the web.config file in the daily backup of FIM. The FIM Portal's detailed error page configuration is stored in its web.config file, which is separate from the FIM Service's database and core configuration backup. To ensure these settings persist after a restore, the web.config file must be included in the daily backup…

Submitted by fernanda_arg· Mar 4, 2026Configuring the FIM Service and Portal

Question

Your company network includes Forefront Identity Manager (FIM) 2010. You configure the FIM Portal to use detailed error pages. A backup of FIM is performed daily. After a restore of the FIM Service, you discover that the detailed error pages are not displayed for the FIM Portal. You need to ensure that when you perform a restore of the FIM Service, the detailed error pages are displayed. What should you do?

Options

  • AInclude the web.config file in the daily backup of FIM.
  • BFrom an elevated command prompt, run iisreset.exe.
  • CFrom the FIM Portal, edit the Portal Configuration Extended Attributes page.
  • DEdit the web.config file and include <customErrors mode="On"/> in the file.

How the community answered

(16 responses)
  • A
    56% (9)
  • B
    25% (4)
  • C
    13% (2)
  • D
    6% (1)

Why each option

The FIM Portal's detailed error page configuration is stored in its web.config file, which is separate from the FIM Service's database and core configuration backup. To ensure these settings persist after a restore, the web.config file must be included in the daily backup routine.

AInclude the web.config file in the daily backup of FIM.Correct

The configuration for detailed error pages in a FIM Portal (an ASP.NET web application) is stored within its `web.config` file. If this file is not included in the daily backup, its settings will be lost when the FIM Service is restored, as the FIM Service backup primarily covers the database and internal service configurations, not the web application's specific settings.

BFrom an elevated command prompt, run iisreset.exe.

Running `iisreset.exe` restarts IIS services but does not restore configuration files or settings that were lost during a prior restore operation.

CFrom the FIM Portal, edit the Portal Configuration Extended Attributes page.

Editing configuration within the FIM Portal is a manual re-configuration step, not a method to ensure settings are automatically restored as part of a backup process.

DEdit the web.config file and include <customErrors mode="On"/> in the file.

Manually editing the `web.config` file would re-enable the feature, but the goal is to ensure the setting is automatically displayed *after a restore* through proper backup procedures, not requiring manual intervention post-restore.

Concept tested: FIM Portal web.config backup for configuration persistence

Source: https://docs.microsoft.com/en-us/troubleshoot/aspnet/configure-custom-error-pages

Topics

#FIM Portal#Backup and Restore#web.config

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice