New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Plat-Admn-201 Exam - Topic 2 Question 2 Discussion

Actual exam question for Salesforce's Plat-Admn-201 exam
Question #: 2
Topic #: 2
[All Plat-Admn-201 Questions]

The client services and customer support teams share the same profile but have different permission sets. The custom object Retention related list needs to be restricted to the client services team on the Lightning record page layout. What should a Platform Administrator use to fulfill this request?

Show Suggested Answer Hide Answer
Suggested Answer: B

When users share the same profile but require different user interface experiences, Component Visibility is the most effective tool. In the Lightning App Builder, the administrator can select the 'Related List' component (or a 'Related List - Single' component for Retention) and add a visibility filter. The filter can be set to 'User > Permission > Custom Permission' or 'User > Profile,' but since they share a profile, the best approach is to filter based on a Permission Set or a specific user field. This allows the Retention list to be visible only to the Client Services team members while remaining hidden for the Customer Support team, even though they are looking at the same record. Page Layout Assignment (Option A) and Record Type Assignment (Option C) are profile-based and would not work since the teams share a profile. Sharing Settings (Option D) control access to the data itself, but the request specifically asks to hide the UI element (the related list).


Contribute your Thoughts:

0/2000 characters
Joye
7 days ago
I’m not entirely sure, but I remember something about Page Layout Assignment being used for different profiles. Could that apply here?
upvoted 0 times
...
Hildred
13 days ago
I think we might need to look at Component Visibility for this one since it’s about restricting access on the Lightning page layout.
upvoted 0 times
...
Mollie
18 days ago
Ah, the age-old question of how to restrict access to a custom object. Classic Salesforce problem right there.
upvoted 0 times
...
Shayne
23 days ago
B) Component Visibility sounds like the right choice. Who needs sharing settings when you can just hide the component?
upvoted 0 times
...
Delmy
28 days ago
I'm going with C) Record Type Assignment. That's how you can have different permission sets for different record types.
upvoted 0 times
...
Charolette
1 month ago
Definitely D) Sharing Settings. That's the way to control access to records, not just the layout.
upvoted 0 times
...
Laura
1 month ago
I think the answer is B) Component Visibility. That's the way to restrict access to specific components on a record page.
upvoted 0 times
...
Merilyn
1 month ago
Based on the details provided, I'm leaning towards option B - using component visibility to restrict that Retention related list to the client services team.
upvoted 0 times
...
Paris
2 months ago
I'm a bit confused on the difference between page layout assignment and record type assignment for this scenario. I'll need to review those concepts.
upvoted 0 times
...
Joanne
2 months ago
Okay, let me think this through. I'm pretty sure I need to use component visibility to control who can see that Retention related list.
upvoted 0 times
...
Johnna
2 months ago
Hmm, this one seems tricky. I'm not sure if page layout or sharing settings would be the best approach here.
upvoted 0 times
...
Shawna
2 months ago
I think I'd start by looking at the page layout options to see if I can restrict the Retention related list there.
upvoted 0 times
...
Tamra
2 months ago
I think A) Page Layout Assignment could work too.
upvoted 0 times
...
Carin
2 months ago
B) Component Visibility is the way to go!
upvoted 0 times
...

Save Cancel