Q: 7
A banking company wants their customers Date of Birth Field searchable by Banking Reps, but only
editable by Customer Support Reps.
Which approach is recommended to meet this requirement?
Options
Discussion
Option B worked for me in a similar use case during a mock. Field Level Security lets you make the Date of Birth field visible and editable for Customer Support, but only visible (read-only) for Banking Reps, so they can search it but not update it. I think that's what Salesforce recommends here. Agree?
Nah, not A-validation rules won't grant search access. B makes more sense for FLS control.
Makes sense, I'd pick B.
B
Option B, but I'm kinda torn since C mentions search layout and the question says "searchable." Not 100 percent sure here.
B here, C trips people up but doesn't enforce edit restriction. FLS covers both the readonly and editable needs, yeah?
B , setting FLS for read-only vs edit is classic for this use case. Official guides and hands-on org setups mention this approach often.
B tbh, Field Level Security lets you give Banking Reps read-only and Customer Support Reps edit access to that field. C doesn't truly restrict editing for Banking Reps. Pretty sure that's what a real scenario would use, but open to counterpoints.
C or B, depends if Search layout config is treated as required for the searchability part.
That search aspect is a bit tricky. Even if Banking Reps have read-only FLS via B, the field must also be included in the Search Layout for them to actually find it by searching. But C doesn't restrict edit access, so overall B is still right, just keep in mind there's a minor search config dependency. Pretty sure that's what Salesforce expects.
Be respectful. No spam.
