Examkin

Question

Difficulty: Very hardDynamic Forms and Dynamic Actions

A Salesforce Administrator is configuring a Lightning Record Page for a custom object named Contract_Review__c. The compliance team outlines two strict requirements:
1. The sensitive field Risk_Audit_Notes__c must only appear on the record page layout when the Contract_Value__c is greater than $1,000,000 and the viewing user possesses the specific permission set Risk_Auditor_Access.
2. Users who do not meet these criteria must be entirely prevented from accessing Risk_Audit_Notes__c data across all interfaces, including Reports, Dashboards, Global Search, and API integrations.

Which combination of administrative configurations must be implemented to fulfill both requirements?

  1. Restrict Field-Level Security (FLS) on Risk_Audit_Notes__c so that read and edit access are granted exclusively through the Risk_Auditor_Access permission set, and configure a Dynamic Forms component visibility rule on the Lightning Record Page using the Contract_Value__c field filter.Answer
  2. B
    Upgrade the page layout to Dynamic Forms and configure a component visibility filter on the Risk_Audit_Notes__c field using criteria based on Contract_Value__c and $Permission.CustomPermission without modifying Field-Level Security settings.
  3. C
    Create a custom Profile specifically for risk auditors, grant access to Risk_Audit_Notes__c on that profile, and assign a distinct Page Layout containing the field to that profile via Record Type assignment.
  4. D
    Place Risk_Audit_Notes__c into a separate Dynamic Forms field section, set section visibility using $User.Profile, and hide the field on the underlying standard Page Layout.

Answer

Restrict Field-Level Security (FLS) on the target field to the permission set for underlying data protection, and use Dynamic Forms component visibility rules on the Lightning Record Page for contextual UI display.
The correct solution enforces a multi-layered security and UI strategy. Restricting Field-Level Security (FLS) via the Risk_Auditor_Access permission set ensures that unauthorized users cannot view data in Risk_Audit_Notes__c through reports, dashboards, global search, or API integrations. Concurrently, using Dynamic Forms component visibility rules on the Lightning Record Page ensures the field dynamically appears only when the Contract_Value__c meets the $1,000,000 threshold for qualified users.

Step-by-Step Solution

1
Evaluate data security requirements across APIs, Reports, and Search.
Dynamic Forms component visibility only controls presentation on Lightning record pages; it does not secure data across APIs or Reports.
Field-Level Security (FLS) is necessary to restrict read/edit access system-wide.
2
Configure Field-Level Security (FLS) using Permission Sets.
Remove profile-level read access and grant read/edit access to Risk_Audit_Notes__c solely via the Risk_Auditor_Access permission set.
Follows the principle of least privilege and additive permission management.
3
Configure Dynamic Forms for conditional UI presentation.
Add a component visibility rule on the field or field section in Lightning App Builder filtering by Contract_Value__c > 1000000.
Dynamically shows or hides the field on the Lightning page based on real-time record state.

Key Concept

Field-Level Security (FLS) vs. Dynamic Forms Component Visibility
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic