nerdexam

70-158 · Question #52

You are planning to deploy Forefront Identity Manager (FIM) 2010 in your company network. You want to provide identity management between a Human Resources application and Active Directory Domain…

The correct answer is B. A warm-standby server. For FIM 2010 Synchronization Service high availability, a warm-standby server is the supported approach because the sync service cannot run in an active cluster configuration. A warm-standby allows manual failover to a pre-configured secondary server if the primary fails.

Submitted by zhang_li· Mar 4, 2026Install and upgrade Forefront Identity Manager (FIM) 2010

Question

You are planning to deploy Forefront Identity Manager (FIM) 2010 in your company network. You want to provide identity management between a Human Resources application and Active Directory Domain Services (AD DS). You need to ensure that the synchronization service instance can be returned if the primary server fails. What should you implement?

Options

  • AA cluster server
  • BA warm-standby server
  • CA software load-balance server
  • DA hardware load-balance appliance

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    77% (23)
  • C
    13% (4)
  • D
    7% (2)

Why each option

For FIM 2010 Synchronization Service high availability, a warm-standby server is the supported approach because the sync service cannot run in an active cluster configuration. A warm-standby allows manual failover to a pre-configured secondary server if the primary fails.

AA cluster server

FIM 2010 Synchronization Service is explicitly not supported in a Windows Server Failover Cluster configuration, so a cluster server cannot be used for this role.

BA warm-standby serverCorrect

FIM 2010 Synchronization Service does not support active/passive Windows Server Failover Clustering, making a warm-standby server the Microsoft-recommended disaster recovery solution. A warm-standby server is pre-installed and configured with FIM Sync, and in the event of primary server failure, an administrator manually brings the standby online to restore the synchronization service instance.

CA software load-balance server

Software load balancing is designed to distribute workloads across multiple active nodes, but FIM Synchronization Service must run as a single active instance and does not support load-balanced deployments.

DA hardware load-balance appliance

Hardware load-balance appliances serve the same distributed-traffic purpose as software load balancers and are equally unsupported for FIM Sync, which requires a single active instance rather than distributed processing.

Concept tested: FIM 2010 Synchronization Service high availability strategy

Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/deploy-fim-sync-service

Topics

#FIM Synchronization Service#High Availability#Warm Standby#Disaster Recovery

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice