You are designing the identity security strategy for a Microsoft Entra ID tenant. You need to map specific identity requirements to their correct Microsoft Entra ID configurations. Match each Microsoft Entra ID feature to its correct primary function.
- Security defaultsProvides pre-configured security settings, such as requiring multi-factor authentication for all users, without requiring custom policies.
- Named locationsDefines trusted IP address ranges or geographic areas that can be referenced as conditions in access policies.
- Authentication strengthSpecifies the specific combination of authentication methods, such as FIDO2 security keys, required to access a resource.
- Emergency access accountsHighly privileged accounts that are excluded from policies to ensure administrator access during an unexpected lockout.
Answer
Security defaults match with providing pre-configured security settings. Named locations match with defining trusted IP ranges or geographic areas. Authentication strength matches with specifying the specific combination of authentication methods. Emergency access accounts match with highly privileged accounts excluded from policies to prevent lockout.
Matching the features to their correct functions aligns each tool with its primary purpose: Security defaults for a basic out-of-the-box baseline; Named locations for network-based policy boundaries; Authentication strength for enforcing specific multi-factor methods; and Emergency access accounts as a fallback to prevent total tenant lockout.
Step-by-Step Solution
Key Concept
Microsoft Entra ID features for securing authentication and tenant access management, including basic defaults, location-based conditions, authentication methods verification, and emergency recovery options.
Estimated Time:2m 0s