What is the primary issue preventing Javelin from accessing on-premises domain resources after resetting her password in Azure AD?

• A. Password writeback was not enabled
• B. Azure AD Connect Health is not configured
• C. The password does not meet complexity requirements
• D. Two-factor authentication is not set up

Answer: (A)

The situation with Javelin's inability to access on-premises domain resources after resetting her password in Azure AD relates primarily to password writeback capabilities. Password writeback is a feature that allows users to reset their passwords in Azure AD, and then have those changes synchronized back to on-premises Active Directory. Without this feature enabled, any password changes made in Azure AD won’t reflect in the on-premises Active Directory. Consequently, if Javelin resets her password in Azure AD and password writeback is not configured, her new password would not allow her to access on-premises resources because the on-premises system still holds the old password.

The other factors mentioned, such as Azure AD Connect Health, complexity requirements, and two-factor authentication, do not directly affect the synchronization of password changes between Azure AD and on-premises Active Directory. For instance, Azure AD Connect Health pertains to monitoring the health of Azure AD Connect services but does not facilitate the password writeback process itself. Similarly, complexity requirements influence the creation of new passwords but do not affect the syncing of existing passwords. Two-factor authentication adds a layer of security but does not play a role in the mechanics of password changes and their recognition across platforms. Hence, the crux of the issue