70-158 · Question #80
You administer a Forefront Identity Manager (FIM) 2010 server in your company network. You download a custom workflow that adds a new activity to the Workflow Designer. You need to deploy the…
The correct answer is A. Execute the iisreset.exe command on the FIM server. B. Execute the gacutil.exe tool from the elevated command prompt on the FIM server. D. Restart the Forefront Identity Manager Service on the FIM server. Deploying a custom workflow activity to FIM 2010 requires registering the assembly in the GAC, resetting IIS, and restarting the FIM Service so the new activity is recognized by the Workflow Designer and runtime.
Question
Options
- AExecute the iisreset.exe command on the FIM server.
- BExecute the gacutil.exe tool from the elevated command prompt on the FIM server.
- CExecute the regsvr32.exe tool from the elevated command prompt on the FIM server.
- DRestart the Forefront Identity Manager Service on the FIM server.
- ECopy the assembly to the C:\Windows\Assembly folder on the FIM server.
- FCopy the assembly to the Global Assembly Cache (GAC) folder on the FIM server.
How the community answered
(17 responses)- A82% (14)
- E12% (2)
- F6% (1)
Why each option
Deploying a custom workflow activity to FIM 2010 requires registering the assembly in the GAC, resetting IIS, and restarting the FIM Service so the new activity is recognized by the Workflow Designer and runtime.
Executing iisreset.exe recycles the IIS worker processes that host the FIM Portal, which is necessary for the portal's Workflow Designer to recognize and load the newly registered custom activity assembly.
The gacutil.exe tool is the proper programmatic method to install a strong-named assembly into the Global Assembly Cache (GAC) from an elevated command prompt, making the custom workflow activity available to the .NET runtime on the FIM server.
regsvr32.exe is used to register COM DLLs and ActiveX controls, not managed .NET assemblies; custom FIM workflow activities are .NET assemblies that must be registered in the GAC, not via COM registration.
Restarting the Forefront Identity Manager Service (FIMService) is required so the FIM workflow engine reloads its activity library and can execute the newly deployed custom workflow activity during request processing.
Manually copying files to C:\Windows\Assembly is not the supported or reliable method for GAC installation; the GAC requires proper registration via gacutil.exe or an installer to correctly record metadata and versioning information.
While conceptually correct that the assembly must go into the GAC, this answer is redundant and misleading as a separate step because using gacutil.exe (answer B) is the correct and complete method to add an assembly to the GAC - manually dragging/copying is not a reliable deployment practice and is functionally covered by answer B.
Concept tested: Deploying custom workflow activities to FIM 2010 GAC
Source: https://learn.microsoft.com/en-us/previous-versions/mim/ff400278(v=ws.10)
Topics
Community Discussion
No community discussion yet for this question.