PrepAway - Latest Free Exam Questions & Answers

Author: seenagape

You need to find out why the UndoneImports count does not return zero

Your company network includes Forefront Identity Manager (FIM) 2010. You are performing the migration of
FIM from the test environment to the production environment. After you run the CommitChanges.ps1
PowerShell script, the count of UndoneImports is a non-zero value. You need to find out why the
UndoneImports count does not return zero. What should you do?

which phase does synchronization fail?

You administer a Forefront Identity Management (FIM) 2010 server in your company network. You discoverthat
several objects do not synchronize between the FIM Service database and Active Directory Domain Services
(AD DS). The required identity data has the following features: It appears in the connector space of the FIM
management process. It appears in the metaverse. Itdoes not appear in the connector space of the AD DS
Management Agent.
In which phase does synchronization fail?

You need to find out the cause of the issue

You use Forefront Identity Manager (FIM) 2010 in your company network. The fullName attribute is used to
generate a unique logon name for each user by usinga FIM Workflow activity. Before users objects are created
in the metaverse, the FIM environment performs a collision check to confirm whether a unique fullName
attribute exists. You discover that users having duplicate fullName attributes are not being created. You need to
find out the cause of the issue.
What should you do?

Which Management Policy Rule settings should you validate?

You use Forefront Identity Manager (FIM) 2010 in your company network. You configure the Self- Service
Password Reset feature for the FIM Portal. You discover that existing users are able to submit password reset
requests but new users are unable to register for Self-Service Password Reset. You need to identify the cause
of the issue.
Which Management Policy Rule settings should you validate? (Choose all that apply.)

You need to be able to ascertain the cause of the issue

You use Forefront Identity Manager (2010) in your company network. You configure Password Change
Notification Service (PCNS) between Active Directory Domain Services (AD DS) and AD LDS. You discover
that passwords are not being reset on the target systems. You need to be able to ascertain the cause of the
issue.
What should you do?

You need to identify the cause of the error

You use Forefront Identity Manager (FIM) 2010 in your company network. You configure Password Change
Notification Service (PCNS) between an Active Directory Domain Services (AD DS) domain named contoso.
com and an Active Directory Lightweight Directory Services (AD LDS) instance. The FIM Service is hosted on a
server named FIM-Srv-1.
After you change the password for an AD account, you receive the following RPC exception error:
ProcessID is 3252
System Time is: 7/22/2009 9:8:43:109
Generating component is 3
Status is -2146893022 – The target principal name is incorrect.
Detection location is 150
Flags is 0
NumberOfParameters is 3
Long val: 16
Long val: 6
Long val: 0
You verify the following requirements: The DNS is resolving names correctly. The SPN for the target has been
assigned to an AD account used to host the target process. Time clocks are synchronized to an authoritative
time source. You need to identify the cause of the error.
What should you do?

Which describes the cause of the synchronization issue?

You administer a Forefront Identity Manager (FIM) 2010 server in your company network. FIM synchronizes
data between several data sources and the FIM Portal.
All data sources have an attribute named First Namemapped to the person:
firstName metaverse attribute. Attribute flow precedence for the person: firstName attribute is set toequal
precedence.
Synchronization rules are configured to import and export the attribute. The FIM Portal is the last contributor.
You change the value of the First Name attribute inthe FIM Portal and run full synchronization. You discover
that the value of First Name in the FIM Portal has been staged to the connector space but is not updated in the
metaverse.
Which describes the cause of the synchronization issue?

What is the cause of the issue?

You deploy Forefront Identity Manager (FIM) 2010 inyour company network. You configure group
synchronization between the Active Directory DomainServices (AD DS) domain and the FIM Portal. You
discover that when you add a new user to a group through the FIM Portal, the group membership successfully
flows to the domain. However, if you delete all users from the group, the domain group membership is not
updated.
What is the cause of the issue?