Examkin

Question

Difficulty: MediumProfiles and Object/Field-Level Security

Match each Salesforce security or visibility requirement to the appropriate security feature or administrative tool.

  • Restrict access to a sensitive salary field for most profile users while granting access to a specific subset of managers.Field-Level Security (FLS) combined with Permission Sets
  • Prevent an entire user profile from creating or deleting records of a custom object, regardless of record ownership.Object-Level Permissions (CRUD) on Profile
  • Hide specific fields on a Lightning Record Page based on record field values without restricting underlying API access.Dynamic Forms Component Visibility Rules
  • Completely block user login attempts outside designated corporate IP ranges specifically enforced at the profile level.Profile Login IP Ranges

Answer

1. Restricting access to a sensitive field for most profile users while granting it to specific managers matches Field-Level Security (FLS) combined with Permission Sets.
2. Preventing an entire user profile from creating or deleting custom object records matches Object-Level Permissions (CRUD) on Profile.
3. Hiding fields conditionally on a record page without restricting API access matches Dynamic Forms Component Visibility Rules.
4. Blocking logins outside designated corporate IP ranges enforced at the profile tier matches Profile Login IP Ranges.
Each requirement directly aligns with standard Salesforce security architecture: Field-Level Security with Permission Sets extends specific field access cleanly; Object CRUD on profiles governs baseline record capabilities; Dynamic Forms handles UI presentation rules; and Profile Login IP Ranges strictly enforce IP location restrictions.

Step-by-Step Solution

1
Analyze field-level access control requirements for user subsets.
Field-Level Security combined with Permission Sets allows removing field access at the profile level and adding access selectively.
Profiles establish baseline access, while Permission Sets provide flexible access expansion.
2
Evaluate object creation and deletion restrictions for profiles.
Object-Level Permissions (CRUD) on Profiles control record creation, viewing, editing, and deletion boundaries.
Object permissions override sharing rules and govern general action permissions.
3
Distinguish between UI display rules and data security settings.
Dynamic Forms Component Visibility Rules control page layout display dynamically without impacting API/report data access.
Component visibility affects visual layout rendering rather than database field permissions.
4
Examine IP login restriction mechanisms.
Profile Login IP Ranges enforce strict access denial outside specified ranges.
Profile-level IP restrictions deny login completely, unlike org-wide trusted IP ranges.

Key Concept

Profiles, Object Permissions, Field-Level Security, and User Interface Visibility Controls
Rate this question

Topics

Profiles and Object/Field-Level Security

More questions from this topic