Examkin

Question

Difficulty: Very hardSession Settings and Password Policies

An organization's global security baseline enforces a strict 15-minute session timeout and a 30-day password expiration policy configured in Organization-Wide Session Settings and Password Policies. To accommodate call center operations, executive leadership approves a specialized security exception for customer support representatives: a 60-minute session timeout and a 90-day password expiration interval. A Salesforce administrator creates a new Permission Set containing session-based settings and assigns it to the support team, but audits reveal that the support representatives are still being logged out after 15 minutes and prompted for password resets every 30 days. Which administrative action must be taken to successfully enforce these customized session and password requirements for the support representatives?

  1. Configure the custom session timeout and password expiration values directly within the custom Profile assigned to the customer support representatives.Answer
  2. B
    Add the call center IP address range to Organization-Wide Network Access settings to automatically elevate session timeout limits and bypass password expiration cycles.
  3. C
    Update the Organization-Wide Session Settings and Password Policies to 60 minutes and 90 days, then assign a restrictive Permission Set to all non-support users to decrease their thresholds back to 15 minutes and 30 days.
  4. D
    Create a Session-Based Permission Set Group linked to a custom Auth. Session object flow that dynamically updates user session parameters upon login.

Answer

Configure the custom session timeout and password expiration values directly within the custom Profile assigned to the customer support representatives.
In Salesforce, Password Policies (such as password expiration intervals) and Session Settings (such as session inactivity timeouts) set at the organization level act as global defaults. When individual departments require tailored security parameters, these overrides must be configured directly on the specific Profile assigned to those users. Profile-level password policies and session settings completely take precedence over organization-wide defaults.

Step-by-Step Solution

1
Analyze the security governance hierarchy in Salesforce for session settings and password policies.
Identify that global defaults set at the organization level can be overridden specifically per user profile, but not via permission sets.
Salesforce architecture enforces Password Policies and Session Timeout overrides at the Profile level under Profile Security Settings.
2
Evaluate why the administrator's initial approach using a Permission Set failed.
Confirm that Permission Sets manage functional access rights (e.g., object permissions, system permissions) and cannot override session timeouts or password policy expirations.
Permission Sets lack configuration interfaces for baseline password expiration schedules and session inactivity timeouts.
3
Determine the proper administrative procedure to satisfy the compliance requirement.
Navigate to Setup > Profiles, select the custom profile assigned to customer support representatives, and edit the 'Password Policies' and 'Session Settings' sections directly on the profile.
Profile-level settings explicitly supersede Organization-Wide defaults for all users assigned to that profile.

Key Concept

Profile-Level Overrides for Session Settings and Password Policies
Estimated Time:2m 0s
Rate this question

Topics

Session Settings and Password Policies

More questions from this topic