During a county onboarding day, staff register an authenticator app once so they can complete multifactor authentication and reset forgotten passwords later. What does that registration primarily support?
Select an answer to reveal the explanation.
Short Explanation
One registration day, two wins later. Staff enroll authenticators so MFA challenges work and so self-service password reset has a trusted method ready. It is not about labels, Autopilot hashes, or eDiscovery holds — it is about proving 'you are you' when signing in or unlocking the account.
Full Explanation
Authentication method registration enables both MFA and self-service password reset, which is what staff accomplish during a county onboarding day when they register an authenticator app once for later multifactor challenges and forgotten-password recovery. That single readiness step pays dividends across multiple Entra ID protection and self-service scenarios. MS-900 often tests the idea that registration is shared foundation rather than a narrow one-feature chore.
SharePoint sensitivity label defaults for every new hire site are content classification settings, not authenticator registration. Windows Autopilot hardware hash collection for Cloud PCs is device provisioning data, not MFA/SSPR method enrollment. Microsoft Purview eDiscovery custodian holds for HR cases are compliance actions, not authentication method registration.
An exam caveat is that different methods may be allowed for MFA versus SSPR depending on tenant policy, so onboarding should register methods that satisfy both where possible. Operationally, include authenticator registration in county onboarding checklists, confirm the new hire can complete an MFA challenge and see SSPR methods registered, and track registration completion before the employee’s first unsupervised remote workday.