70-158 Question #26: Real Exam Question with Answer & Explanation

Question

You use Forefront Identity Manager (FIM) 2010 in your company network. You integrate a new Microsoft SQL Server database with FIM. You create a Management Agent (MA) and configure run profiles. You delete an attribute in the SQL database. You execute a Full Import run profile on the SQL MA and it fails. You review the Connection Log and discover a failed-connection error. You need to ensure that the new SQL database can synchronize with FIM. What should you do? (Choose all that apply.)

Options

• ARun iisreset.exe.
• BRefresh the SQL MA schema.
• CConfigure a connector filter in the SQL MA.
• DAdd a new step to the Full Import run profile.
• EConfigure the schema in Management Agent Designer.

Explanation

When a SQL database schema changes (e.g., an attribute is deleted), the FIM Management Agent must be updated to reflect the new schema to avoid connection/import failures.

Common mistakes.

• A. Running iisreset.exe restarts IIS web services and has no effect on the FIM Synchronization Service or the SQL MA schema mismatch causing the import failure.
• C. A connector filter controls which objects are included or excluded from synchronization based on attribute values, but does not resolve a schema mismatch caused by a deleted attribute.
• D. Adding a new step to the Full Import run profile only changes how the import is executed (e.g., adding a delta step), but does not address the underlying schema discrepancy between the SQL database and the MA configuration.

Concept tested. FIM Management Agent schema refresh after database change

Reference. https://learn.microsoft.com/en-us/microsoft-identity-manager/reference/microsoft-identity-manager-2016-ma-ws

No community discussion yet for this question.