Question

Difficulty: MediumSession Settings and Password Policies

A Salesforce Administrator needs to enforce tailored security controls for different user roles while maintaining organizational baselines. Match each security administration scenario to the correct location in Setup where the policy must be configured.

  • Set a custom 15-minute session inactivity timeout exclusively for users assigned to the Customer Support profile.Profile-Level Session Settings
  • Ensure that any user whose session expires across the organization is immediately logged out without receiving a session renewal prompt.Organization-Wide Session Settings
  • Configure a maximum limit of 3 invalid login attempts before lockout specifically for users assigned to the System Administrator profile.Profile-Level Password Policies
  • Establish a baseline requirement for passwords to expire every 90 days for all users in the organization who do not have a profile override.Organization-Wide Password Policies

Answer

1. Custom 15-minute timeout for a specific profile matches Profile-Level Session Settings. 2. Immediate logout upon session expiration org-wide matches Organization-Wide Session Settings. 3. Custom lockout threshold for a specific profile matches Profile-Level Password Policies. 4. Baseline password expiration for all users matches Organization-Wide Password Policies.
Custom session timeout durations tailored to specific user roles belong in Profile-Level Session Settings. Global session behavior, such as forcing logout upon session timeout, is configured under Organization-Wide Session Settings. Custom password lockout thresholds for dedicated user roles are defined in Profile-Level Password Policies, whereas default password expiration timelines for the entire tenant are established in Organization-Wide Password Policies.

Step-by-Step Solution

1
Categorize each scenario into Session Settings vs Password Policies.
Scenarios concerning inactivity timeout durations and forced logouts fall under Session Settings. Scenarios concerning invalid login lockouts and password expiration periods fall under Password Policies.
Isolating session behavior from authentication rules identifies the proper administration category in Setup.
2
Determine whether each requirement applies to the entire organization or to a specific subset of users defined by a Profile.
Scenarios targeting the Customer Support profile and System Administrator profile require Profile-level overrides. Scenarios specifying default behavior for all users or tenant-wide forced logout require Organization-Wide configurations.
Salesforce allows admins to define org-wide defaults while overriding session timeouts and password policies at the individual profile level.
3
Pair each scenario with its designated administrative interface in Salesforce.
Specific profile timeout -> Profile-Level Session Settings; Org-wide forced logout -> Organization-Wide Session Settings; Specific profile lockout -> Profile-Level Password Policies; Default org password expiration -> Organization-Wide Password Policies.
This satisfies security requirements by applying overrides where specific control is required and global settings where universal enforcement is needed.

Key Concept

Distinction between Organization-Wide and Profile-Level enforcement for Session Settings and Password Policies in Salesforce.
Rate this question