Identity Connect is positioned primarily as a user provisioning and deprovisioning bridge between Microsoft Active Directory and Salesforce. In designs where AD is the authoritative source for user status, deactivating a user upstream should be reflected quickly in Salesforce access. That is why architects pay attention to what happens to existing sessions when a user is disabled in the source directory. The feature is not a managed package, and it is not an identity provider that automatically brokers SSO by itself. It also does not “solve” license overages by disabling users in a FIFO pattern. The relevant capability is operational user-state synchronization: when identity status changes in directory services, Salesforce access should be withdrawn in a controlled, security-focused way. This is why option D is the best answer in Salesforce terms.