CRT-211 · Question #81
Cloud Kicks has o custom object called Membership Details that records information about customers' preferences for their memberships. Depending, on the membership level, different data needs to be…
The correct answer is B. Set up Dynamic forms to conditionally show data. Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users' access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used…
Question
Cloud Kicks has o custom object called Membership Details that records information about customers' preferences for their memberships. Depending, on the membership level, different data needs to be displayed.
- when cue running user has the Market no profile, all data should be
visible.
- When the running user has the Support profile, only the Support
preference fields should be visible.
- Both Marketing and Support users should be able to report on all
data. How should the administrator deliver this solution?
Options
- ACreate two record types und two page layouts.
- BSet up Dynamic forms to conditionally show data.
- CMake a permission set with a Muting permission.
- DUse Field-Level Security to control data access.
How the community answered
(62 responses)- A3% (2)
- B82% (51)
- C10% (6)
- D5% (3)
Explanation
Use Field-Level Security to control data access is how the administrator should deliver this solution. Field-Level Security is a way to restrict users' access to view or edit specific fields on an object based on their profile or permission set. Field-Level Security can be used to make fields visible or hidden, and editable or read-only for different users. By using Field-Level Security, the administrator can ensure that only Marketing users can see all data on the Membership Details object, while Support users can only see the Support preference fields.
Topics
Community Discussion
No community discussion yet for this question.