A city enables self-service password reset, but many employees still call the help desk because they never set up recovery methods. What readiness requirement does that highlight?
Select an answer to reveal the explanation.
Short Explanation
SSPR is not magic if nobody registered a backup method. Staff need a phone, email, or authenticator on file first. Registration day is what makes Monday resets disappear later.
Full Explanation
SSPR depends on users registering authentication methods before they can reset passwords themselves, which is why a city can enable self-service password reset and still see help-desk calls when employees never set up recovery methods. Registration of phone, email, or authenticator methods is the readiness gate that turns SSPR from a console toggle into a working municipal self-service capability. Fundamentals questions often test that dependency explicitly.
SSPR does not work automatically for every user with no registration of recovery methods. It does not require every employee to install Azure Virtual Desktop before resetting a password. It does not only function after Microsoft Project desktop is licensed for each user.
An exam caveat is that organizations should combine SSPR enablement with registration campaigns, Conditional Access registration policies where appropriate, and clear help-desk escalation paths for users who lose all methods. Operationally, report the percentage of municipal users with registered SSPR methods, target unregistered departments with intranet reminders, and re-measure password-reset ticket volume only after registration coverage crosses the city’s readiness threshold.