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 Certified Platform Sharing and Visibility Architect (Plat-Arch-205) Exam - Topic 2 Question 53 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) exam
Question #: 53
Topic #: 2
[All Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205) Questions]

A banking company uses a VIP Flag in the Contact Object that they want only Private Banking Reps to see.

Which approach is recommended to meet this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Royal
3 months ago
B could work too, but C seems simpler.
upvoted 0 times
...
Cherry
3 months ago
Isn't changing the field type overkill for this?
upvoted 0 times
...
Felicidad
3 months ago
Wait, can you really restrict visibility like that?
upvoted 0 times
...
Shaquana
4 months ago
Definitely agree with C, super straightforward!
upvoted 0 times
...
Kindra
4 months ago
I think option C is the best choice.
upvoted 0 times
...
Hailey
4 months ago
I think I read somewhere that Field Level Security is the best practice for controlling access, so I might lean towards option C, but I could be wrong.
upvoted 0 times
...
Tamar
4 months ago
I feel like changing the field type in option A could complicate things unnecessarily. I wonder if it would even solve the visibility issue for Private Banking Reps.
upvoted 0 times
...
Ellsworth
4 months ago
I remember practicing a question about page layouts, so option B sounds familiar, but I'm not convinced it's the best way to restrict access to just one group.
upvoted 0 times
...
Hayley
5 months ago
I think option C makes the most sense because it directly controls visibility based on user profiles, but I'm not entirely sure if that's the only thing we need to consider.
upvoted 0 times
...
Marylin
5 months ago
Ah, this is a good one. I'm leaning towards option C as well. Changing the field type or the layout doesn't seem like the right solution here. Controlling the field-level security is probably the most targeted way to meet the requirement.
upvoted 0 times
...
Alica
5 months ago
I think I've got this one. Option C seems like the best choice - setting the field-level security to make the VIP Flag visible only to the Private Banking Rep profile. That way, we can control who sees that sensitive information.
upvoted 0 times
...
Cecil
5 months ago
Okay, let me think this through. Since we want to restrict visibility of the VIP Flag, I'm guessing option C, setting the field-level security, is the recommended approach. That way we can make the field visible only to the Private Banking Rep profile.
upvoted 0 times
...
Marica
5 months ago
Hmm, I'm a bit unsure about this one. I know we need to control field visibility, but I'm not sure if changing the field type or the layout is the right approach here. Maybe the field security setting is the way to go?
upvoted 0 times
...
Melda
5 months ago
This seems like a straightforward question about field visibility. I think the key is to focus on the specific requirement of making the VIP Flag visible only to Private Banking Reps.
upvoted 0 times
...
Marti
10 months ago
The bank's IT team must be really paranoid about that VIP Flag. It's like they're guarding the nuclear launch codes or something.
upvoted 0 times
Ryan
9 months ago
A: I agree, it's important to limit access to sensitive information like that.
upvoted 0 times
...
Cathern
9 months ago
B: Yeah, setting Field Level Security for the VIP Flag field makes sense to control who can see it.
upvoted 0 times
...
Rolande
10 months ago
A: Option C seems like the best approach to restrict access to the VIP Flag.
upvoted 0 times
...
...
Freida
10 months ago
Option A looks a bit overkill. Why go through the trouble of creating a new record type when you can just use Field Level Security?
upvoted 0 times
...
Galen
10 months ago
Haha, I can just imagine the Private Banking Reps trying to sneak a peek at the VIP Flag like it's some kind of secret spy code.
upvoted 0 times
...
Maryanne
10 months ago
I'm not sure if Option B is the best approach. Hiding the field from other layouts could cause confusion or unintended behavior.
upvoted 0 times
Karl
8 months ago
A: Yeah, Option C provides a clear and controlled access to the VIP Flag field. It's important to consider security when dealing with sensitive information.
upvoted 0 times
...
Theodora
8 months ago
C: Option C is definitely the most secure choice. Limiting visibility based on profile ensures only the right people can see the VIP Flag field.
upvoted 0 times
...
Thaddeus
9 months ago
B: I agree, Option B might lead to confusion. Setting Field Level Security for the VIP Flag field is a safer option.
upvoted 0 times
...
Tamie
9 months ago
A: I think Option A is the way to go. Changing the field type and creating a new record type seems like a more secure approach.
upvoted 0 times
...
...
Mabelle
10 months ago
Option C seems like the most straightforward way to achieve the requirement. Field Level Security is designed for exactly this kind of use case.
upvoted 0 times
Maryln
10 months ago
I agree, Field Level Security is the best option for controlling visibility.
upvoted 0 times
...
Aleisha
10 months ago
Option C seems like the most straightforward way to achieve the requirement.
upvoted 0 times
...
...
Alton
11 months ago
I prefer option C, setting Field Level Security for the VIP Flag field seems more straightforward to me.
upvoted 0 times
...
Mel
11 months ago
I agree with Torie, changing the field type to a picklist and defining a new record type makes sense.
upvoted 0 times
...
Torie
11 months ago
I think option A is the best approach.
upvoted 0 times
...

Save Cancel