70-158 · Question #53
You are planning to deploy Forefront Identity Manager (FIM) 2010 in your company network to provide an identity management solution between an enterprise resource planning (ERP) application and…
The correct answer is B. Deploy a FIM Service instance on an active server and a second FIM service instance on a C. Deploy the FIM Synchronization Service database and FIM Service database in a failover E. Deploy a FIM Synchronization Service instance on an active physical server and a second FIM. This question tests knowledge of FIM 2010 fault tolerance architecture, requiring candidates to identify which deployment models support high availability for each FIM component.
Question
Options
- ADeploy FIM Service in a network load-balanced configuration.
- BDeploy a FIM Service instance on an active server and a second FIM service instance on a
- CDeploy the FIM Synchronization Service database and FIM Service database in a failover
- DDeploy the FIM Synchronization Service database and FIM Service database in a network
- EDeploy a FIM Synchronization Service instance on an active physical server and a second FIM
How the community answered
(35 responses)- A11% (4)
- B69% (24)
- D20% (7)
Why each option
This question tests knowledge of FIM 2010 fault tolerance architecture, requiring candidates to identify which deployment models support high availability for each FIM component.
FIM Service cannot be deployed in a network load-balanced (NLB) configuration because NLB is not supported for the FIM Service role due to session state and service dependencies that require active/passive clustering instead.
FIM Service supports fault tolerance through an active/passive cluster configuration, where a second FIM Service instance on a standby server can take over if the active server fails, providing failover capability for the FIM Service role.
Both the FIM Synchronization Service database and FIM Service database are SQL Server databases that support fault tolerance through SQL Server failover clustering, which provides automatic failover of the database to a passive node if the active node fails.
SQL Server databases for FIM components do not support network load balancing for fault tolerance; SQL Server high availability requires failover clustering (active/passive), not NLB, making this an invalid configuration for database fault tolerance.
FIM Synchronization Service does not support network load balancing and instead requires an active/passive cluster model, so deploying a second FIM Synchronization Service instance on a standby physical server provides the required fault tolerance through failover.
Concept tested: FIM 2010 high availability and fault tolerance deployment
Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/deploy-fim-service
Topics
Community Discussion
No community discussion yet for this question.