Examkin

Question

Difficulty: EasyProfiles and Object/Field-Level Security

Pair each Salesforce access control requirement on the left with the appropriate security mechanism on the right.

  • Completely hide a sensitive custom field from users assigned to a profile across all views, reports, and API calls.Field-Level Security (FLS)
  • Grant Create and Read access for the Account object to all users assigned to a standard user profile.Object Permissions on Profile
  • Prevent users assigned to a specific profile from logging into Salesforce outside of standard business working hours.Profile Login Hours
  • Deny login attempts for users on a profile if their connection originates outside designated corporate IP ranges.Profile Login IP Ranges

Answer

Field-Level Security hides fields universally; Object Permissions grant object-level CRUD access; Profile Login Hours control allowable login times; Profile Login IP Ranges restrict login access by network IP address.
Each administrative requirement corresponds directly to a specific profile security setting: Field-Level Security controls field access across all entry points; Object Permissions govern object-level CRUD access; Profile Login Hours define allowed authentication windows; and Profile Login IP Ranges enforce network boundaries.

Step-by-Step Solution

1
Identify the level of security required for each access scenario.
Categorize requirements into field visibility, object access, temporal login restrictions, and network location restrictions.
Salesforce security features enforce controls at different scopes (Field, Object, and System Security Settings).
2
Match field visibility requirements to Field-Level Security (FLS).
Hiding fields across layouts, API, and reports maps directly to FLS settings.
Page layouts only control visibility on UI record pages, whereas FLS enforces security across all access channels.
3
Match object CRUD requirements to Object Permissions on Profile.
Granting Create and Read access for an object maps to Object Permissions.
Object permissions establish the baseline actions a user can perform on records of that object type.
4
Match time and network location restrictions to Profile Login Hours and Profile Login IP Ranges.
Working hours limits map to Profile Login Hours, while IP whitelist restrictions map to Profile Login IP Ranges.
Profile-level login restrictions enforce system access boundaries prior to record-level access evaluation.

Key Concept

Profiles control baseline object permissions, field-level security, and system-level login restrictions (IP ranges and login hours).
Rate this question

Topics

Profiles and Object/Field-Level Security

More questions from this topic