Examkin

Question

Difficulty: MediumProfiles and Object/Field-Level Security

Match each Salesforce security requirement regarding profile settings and object or field-level security to its appropriate administration mechanism.

  • Granting Read and Edit access for a sensitive custom field to only a select group of users without altering their base profile assignmentsField-Level Security (FLS) managed via Permission Set
  • Completely disabling Read, Create, Edit, and Delete access to a custom object for all users assigned to a specific job roleObject-Level Permissions (CRUD) configured on the Profile
  • Restricting the specific times of day when call center representatives are permitted to access the Salesforce orgLogin Hours specified on the Profile
  • Enforcing strict network access control by denying login entirely to users on a profile when originating outside designated IP addressesLogin IP Ranges specified on the Profile

Answer

Granting selective field access maps to Field-Level Security managed via Permission Set. Completely removing access to a custom object maps to Object-Level Permissions configured on the Profile. Restricting login time windows maps to Login Hours specified on the Profile. Enforcing IP-based login blocking maps to Login IP Ranges specified on the Profile.
Each requirement directly aligns with standard Salesforce security administration principles: Permission Sets grant field access incrementally to select users; Profile Object Permissions set baseline object access (CRUD); Profile Login Hours dictate valid access windows; and Profile Login IP Ranges dictate absolute network entry limits.

Step-by-Step Solution

1
Analyze field-level access requirements for a subset of users
Determine that Permission Sets with FLS are used to extend field visibility to specific users without altering the shared profile.
Profiles set baseline access, and permission sets incrementally grant additional permissions such as FLS.
2
Evaluate object-level visibility settings for a whole role
Identify Object-Level Permissions (CRUD) on the Profile as the control point for enabling or disabling entire object access.
Profile object permissions govern whether users can Read, Create, Edit, or Delete records of that object type.
3
Determine time-based login control settings
Match time-window restrictions to Profile Login Hours.
Profile-level Login Hours define the exact operating hours during which assigned users can authenticate into the org.
4
Determine network-based login restrictions
Match network IP restrictions that block access to Profile Login IP Ranges.
When Login IP Ranges are set on a Profile, logins originating outside these ranges are strictly prohibited rather than challenged with identity verification.

Key Concept

Salesforce Security Architecture: Profiles vs. Permission Sets, Object Permissions, FLS, and Login Restrictions
Rate this question

Topics

Profiles and Object/Field-Level Security

More questions from this topic