An organization has configured strict security settings for users assigned to the Field Specialist profile. The administrator set the Profile Login IP Ranges to – and Profile Login Hours to Monday through Friday from 08:00 AM to 06:00 PM EST. Additionally, the Organization-Wide Network Access Trusted IP Ranges include – . A user assigned to the Field Specialist profile attempts to log in under two different scenarios:
1. On Wednesday at 09:00 PM EST from IP address .
2. On Thursday at 02:00 PM EST from IP address .
Which two login outcomes will occur based on these configurations?
- The login attempt on Wednesday at 09:00 PM EST is denied because it occurs outside the profile's allowed Login Hours.Answer
- The login attempt on Thursday at 02:00 PM EST is denied because Profile Login IP Ranges restrict login access outside the defined profile range.Answer
- CThe login attempt on Thursday at 02:00 PM EST is allowed after completing multi-factor identity verification because the IP is in the Organization Network Access trusted range.
- DThe login attempt on Wednesday at 09:00 PM EST is granted read-only access until the next designated login window opens.
Answer
The login attempt on Wednesday at 09:00 PM EST is denied due to Profile Login Hours restrictions, and the login attempt on Thursday at 02:00 PM EST is denied because Profile Login IP Ranges enforce a hard restriction regardless of Organization Network Access settings.
The correct outcomes recognize that profile security settings enforce strict access controls. Violating Profile Login Hours causes an immediate block of authentication. Furthermore, Profile Login IP Ranges establish an explicit whitelist; any login from an IP address not included in the profile's range is blocked outright, regardless of organization-level Network Access configurations.
Step-by-Step Solution
Key Concept
Profile-level Login Security boundaries (Login Hours and IP Ranges) strictly deny access when violated and supersede Organization-Wide Network Access settings.