Question

Difficulty: HardSession Settings and Password Policies

A Salesforce Administrator is auditing the organization's security baseline and profile-specific security requirements. Match each security requirement on the left to the correct administrative location or configuration setting in Salesforce Setup on the right.

  • Enforce custom password complexity requirements specifically for users assigned to the Customer Support Specialist profile.Profile-level Password Policies
  • Ensure user session tokens become invalid immediately upon reaching a 15-minute inactivity threshold across the entire organization.Organization-Wide Session Settings: Force logout on session timeout
  • Prevent session hijacking org-wide by binding active user sessions strictly to the original client IP address.Organization-Wide Session Settings: Lock sessions to the IP address from which they originated
  • Configure the global baseline duration for user account unlock following five consecutive failed login attempts.Organization-Wide Password Policies: Password Lockout Period

Answer

The correct pairings align each security requirement with its accurate Salesforce administrative control: profile-specific password rules are managed via Profile-level Password Policies; global session token invalidation upon timeout and IP binding are managed under Organization-Wide Session Settings; global account lockout rules are set under Organization-Wide Password Policies.
Each requirement maps to its specific administrative interface in Salesforce Setup: Profile-level Password Policies allow granular overrides for specific user profiles; Organization-Wide Session Settings manage session timeouts, force logout behavior, and origin IP session locking globally; Organization-Wide Password Policies define default lockout periods and login failure thresholds for the organization baseline.

Step-by-Step Solution

1
Analyze profile-specific vs org-wide password controls.
Identify that customized password complexity for a specific profile (Customer Support Specialist) requires Profile-level Password Policies.
Organization-wide password policies set the default baseline, but profile-level password policies allow targeted overrides.
2
Evaluate session management controls.
Identify that session timeout duration, forcing logout upon timeout, and locking sessions to origin IP addresses are configured under Session Settings in Setup.
Session security settings apply organization-wide to govern active web sessions and session token lifecycle.
3
Differentiate default lockout duration setup.
Map global lockout duration to Organization-Wide Password Policies.
Lockout policies (such as lockout duration after failed login attempts) are maintained in Password Policies in Setup.

Key Concept

Distinction between Organization-Wide Session Settings, Org-Wide Password Policies, and Profile-Level Password Policy Overrides.
Rate this question