The different scenarios may be expected or due to a configuration issue.
1. An ADSAccount resource is assigned, but there is no associated ADSAccount.
In this instance there may a configuration issue with the ADSAccount resource or the VI_ADS_ADSAccount_Insert may have failed for one or more reasons. Check the job service log for any errors and the job queue for any 'FROZEN' process steps during the INSERT.
For additional troubleshooting steps please refer to Knowledge Article 123332
, Identity Manager troubleshooting steps and required information
2. An ADSAccount exists for an Employee, but there is no ADSAccount resource assigned.
In this instance the ADSAccount may be the result of a synchronization with Active directory. It could also have been assigned manually in Manager.
3. An ADSAccount resource is assigned and there is an associated ADSAccount.
In this instance, if the ADSAccount was assigned to the Employee object automatically or via inheritance, then the normal expected result is that an ADSAccount will be created for the Employee object.